Bug 963773

Summary: scsi-cd: tray statuses (locked and open) are not reset on boot/reboot of guest
Product: Red Hat Enterprise Linux 6 Reporter: Pavel Hrdina <phrdina>
Component: qemu-kvmAssignee: Pavel Hrdina <phrdina>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.4CC: acathrow, bsarathy, chayang, flang, juzhang, lnovich, michen, mkenneth, qzhang, sluo, virt-maint
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: qemu-kvm-0.12.1.2-2.376.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 963775 (view as bug list) Environment:
Last Closed: 2013-11-21 06:58:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 963775    

Description Pavel Hrdina 2013-05-16 14:16:55 UTC 
Description of problem:

If you reboot a guest which locks the tray of optical drive the optical drive stay locked.

How reproducible: 100%

Steps to Reproduce:
1. Boot a guest with media inserted in optical drive (for example fedora 17)
2. The media is auto-mounted and the optical drive is locked
3. Reboot the guest.
4. Before kernel is loaded (in GRUB time) the optical drive is locked
  
Actual results:
Before kernel is loaded the optical drive is locked.

Expected results:
Optical drive should not be locked.
Comment 7 langfang 2013-06-28 07:11:00 UTC 
This bug can be verified on latest version,please see  Bug 886878 atapi: tray statuses (locked and open) are not reset on boot/reboot of guest(comment8)

...
Verify this bug as follow version:
HOst:
# uname -r
2.6.32-392.el6.x86_64
# rpm -q qemu-kvm
qemu-kvm-0.12.1.2-2.376.el6.x86_64

Guest:
2.6.32-358.el6.x86_64

.....
Addtional info:
...
3)Also tried use local cdrom with scsi-cd,work well



So this bug fixed.
Comment 10 errata-xmlrpc 2013-11-21 06:58:08 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-1553.html