Bug 742446

We need to figure out whether this is a virtualization problem or a general problem.  Let's try to reproduce on a physical machine.

We need to observe the state of the drive's tray lock.  The obvious way to do that is to press the physical eject button.  If nothing happens, the tray is locked.

Complication: software can react to the button press, and unlock the tray.  I don't know whether RHEL-6 does that.

Suggested test:

1. Boot physical machine similar to the virtual one, i.e. with a CD containing an ISO filesystem in the drive.

2. Verify that filesystem got mounted automatically.

3. Press the eject button.  Does the tray open?

4. Unmount the filesystem if it's mounted.  Close the tray if it's open.

5. Mount the filesystem manually.

6. Press the eject button.  Does the tray open?

If the tray opens in step 3 and doesn't open in step 6, we can be pretty sure the automatic mount during boot didn't lock the drive, but the manual mount in step 5 did.

If the tray opens neither in step 3 nor in step 6, we can be pretty sure both mounts locked the drive.

If the tray opens in both steps, we need to dig deeper.

If the tray doesn't open in step 3 and does open in step 6, I'm confused, and we need to dig deeper.

I tried twice,please have a look the following infos.
#uname -r
2.6.32-191.el6.x86_64
> 1. Boot physical machine similar to the virtual one, i.e. with a CD containing
> an ISO filesystem in the drive.
> 
> 2. Verify that filesystem got mounted automatically.
Yes,mounted automatically
#mount
/dev/sr0 on /media/CDROM type iso9660 (ro,nosuid,nodev,uhelper=udisks,uid=0,gid=0,iocharset=utf8,mode=0400,dmode=0500)

> 
> 3. Press the eject button.  Does the tray open?
> 
After press the eject button,the tray doesn't open.
> 4. Unmount the filesystem if it's mounted.  Close the tray if it's open.
#umount /media/CDROM
Unmount the filesystem,then press the the eject button,the tray open,then close the tray.

> 
> 5. Mount the filesystem manually.
mount the filesystem manually.
#mount /dev/sr0 /mnt/
mount: block device /dev/sr0 is write-protected, mounting read-only
#mount
/dev/sr0 on /media/CDROM type iso9660 (ro,nosuid,nodev,uhelper=udisks,uid=0,gid=0,iocharset=utf8,mode=0400,dmode=0500)
/dev/sr0 on /mnt type iso9660 (ro)

#
> 
> 6. Press the eject button.  Does the tray open?
> 
After press the eject button,the tray doesn't open.
> If the tray opens in step 3 and doesn't open in step 6, we can be pretty sure
> the automatic mount during boot didn't lock the drive, but the manual mount in
> step 5 did.
Neither open in step 3 and step6.
> 
> If the tray opens neither in step 3 nor in step 6, we can be pretty sure both
> mounts locked the drive.
> 
Neither open in step 3 and step6.

> > 4. Unmount the filesystem if it's mounted.  Close the tray if it's open.
> #umount /media/CDROM
> Unmount the filesystem,then press the the eject button,the tray open,then close
> the tray.
> 
Re-parse these sentence in order to don't bring misunderstandings .
1.#umount /media/CDROM
2.then I press the the eject button,the tray open.
3.I press the the eject button again,the tray close

I tried to reproduce this with a freshly installed 6.2 guest (standard server install), no luck.  I suspect your guest runs something that I don't run.  To help me over this hump, please do a fresh install, reproduce the bug, and send me the anaconda-ks.cfg and install.log.

(In reply to comment #5)
> I tried to reproduce this with a freshly installed 6.2 guest (standard server
> install), no luck.  I suspect your guest runs something that I don't run.  To
> help me over this hump, please do a fresh install, reproduce the bug, and send
> me the anaconda-ks.cfg and install.log.


I tested this bug and got the same result with comment 2. Neither open in step 3 and step 6.  "info block" got locked=0 in step 3, and  "info block" got locked=1 in step 6.

Created attachment 567486 [details]
anaconda-ks.cfg log

Created attachment 567487 [details]
install log

My two cents:

Tested f17 host with a f16 guest.

 - locked=0 at grub in the first boot
 - locked=1 during boot time (changes while loading the kernel)
 - locked=1 all the time after a reboot (even at grub)

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.

I've been investigating this issue and the bug is not in qemu-kvm but in Nautilus or Gnome. If the media is automounted by nautilus the optical drive stay unlocked. If you turn off automount in Gnome using gconf-editor and after that try to mount media using Nautilus the optical drive stay unlocked too.

I tried this also using KDE an there is not this bug. KDE did not automatically mount the inserted media and if I opened them by Dolphin the optical drive changed status from unlocked to locked.

I've done some deeper investigation and I find out that the media is not locked is a feature of udisks to enable the HW eject button.

And another interesting think is that for some physical drives udisks using detection by polling and for others it is not using detection by polling. And there is the difference. If detection by polling is used, then the optical drive is not locked, otherwise it is locked.

This is probably not a bug at all.

I'll test the issue mentioned by Ademar in Comment #11