Re: [Xen-devel] IDE CD-ROM drive problem - Evan Deaubl - com.xensource.lists.xen-devel

5 messages in com.xensource.lists.xen-develRe: [Xen-devel] IDE CD-ROM drive prob...

From	Sent On	Attachments
Evan Deaubl	15 Dec 2003 21:00
Steven Hand	16 Dec 2003 08:00
Keir Fraser	16 Dec 2003 08:11
Evan Deaubl	17 Dec 2003 21:37
Steven Hand	17 Dec 2003 23:43

Subject:	Re: [Xen-devel] IDE CD-ROM drive problem
From:	Evan Deaubl (ev...@inuum.com)
Date:	12/17/2003 09:37:35 PM
List:	com.xensource.lists.xen-devel

The only platform I've been able to test this on so far is a VMWare setup (I don't imagine native hardware being different, as I've had the same results from both thus far), but here are the results. If I boot now with no disk in the drive, it reports "No medium found" in the drive, even when I put a disk in the drive to mount. If I boot with a disk in the drive, then it behaves the same as it did when I removed the block of code in xenolinux_block_open().

I will try and get the boot output to dump to a serial file and post it tomorrow.

I concur, though, looks like bringing in all the CD-ROM code would be icky...

-- Evan Deaubl ev...@inuum.com

Quoting Keir Fraser <Keir...@cl.cam.ac.uk>:

Indeed - as the comments indicate, this is pretty gross stuff trying to work around the fact that we didn't bother porting all the cdrom stuff to do with media (and audio stuff etc).

However I'd expect it to 'work' in the sense that it should produce the error "mount: No medium found" if there's no CD in the drive, or never trigger this if code if there was a CD in the drive at boot time. If you're getting "Not a valid block device" that seems like something else is going on...

Can you post the output from Xen and XenoLinux booting if you have it?

If I remove this code, I can mount the CD-ROM with no difficulty. I've been investigating the problem myself, but I figured I'd forward to the experts in charge who have been into this code a lot more than I have.

Removing it completely is not the right thing to do, although it may well need to be fixed 'properly' (i.e. pull in all the cdrom crap :-(

I think I may have now fixed this problem in the unstable tree. I made a few other cleanups at the same time -- I'd appreciate it if you can pull teh updates and see if the problem has gone away (or got worse! ;-).