Description of problem:
Version-Release number of selected component (if applicable):
# uname -r
# rpm -q kvm
Steps to Reproduce:
# /usr/libexec/qemu-kvm -no-hpet -usbdevice tablet -rtc-td-hack -drive
-smp 1 -m 1G -cpu qemu64,+sse2 -vnc :31 -monitor stdio -net
tap,vlan=0,script=/etc/qemu-ifup -boot c -drive
(qemu) eject ide1-cd0
(qemu) change ide1-cd0 gpxe.iso
(qemu) info block
ide1-cd0: type=cdrom removable=1 locked=0 file=gpxe.iso ro=0 drv=raw
ide1-cd0: type=cdrom removable=1 locked=0 file=gpxe.iso ro=1 drv=raw
*** Bug 641854 has been marked as a duplicate of this bug. ***
Note, this is actually preventing the media to be changed at all using libvirt if selinux is in enforcing mode so this would probably deserve higher priority.
Markus, what's your view of it? Is it complex to fix?
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.
This request was erroneously denied for the current release of
Red Hat Enterprise Linux. The error has been fixed and this
request has been re-proposed for the current release.
Probably related to rhel-6 bug 602026.
Move to Tier2 to match tier of 602026
Reassign to Christoph as he did the RHEL6 patch for this one.
Christoph, please take a quick look and apply the same RHEL5.7
triage rules to this one.
It's easily doable for RHEL5.7. I've just posted the patch for review.
Reproduced on kvm-83-224.el5
Verified on kvm-83-232.el5
Steps to Reproduce:
1.run a VM
2.info block and check ide1-cd0 status
4 change ide1-cd0 filename and check ide1-cd0's status
on kvm-83-224.el5 ,ide1-cd0 ro=0
on kvm-83-232.el5 ,ide1-cd0 ro=1
Based on above ,this issue has been fixed.
*** Bug 657252 has been marked as a duplicate of this bug. ***
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.