Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Ejecting a busy floppy from guest causes I/O error
Version-Release number of selected component (if applicable):
- libvirt-0.8.7-8.el6.x86_64
- kernel-2.6.32-114.0.1.el6.x86_64
- qemu-kvm-0.12.1.2-2.144.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1. Add a floppy to guest xml
</disk>
<disk type='block' device='floppy'>
<driver name='qemu' type='raw'/>
<source dev='/var/lib/libvirt/images/floppy1.img'/>
<target dev='fda' bus='fdc'/>
</disk>
2. Define and start the guest
3. In guest,
# modprobe floppy
# mount /dev/fd0 /mnt
4.Prepare a eject.xml
# cat eject.xml
<disk type='block' device='floppy'>
<target dev='fda' bus='fdc'/>
</disk>
5. # virsh update-device rhel61_i386_11 eject.xml
Device updated successfully
Actual results:
5. Could eject a busy floppy in guest without --force, and seconds later, could see I/O error in guest (please see the attachment)
Expected results:
6. Should cannot eject a busy floppy in guest without --force, surely should not cause I/O error in guest
Additional info:
The actual results are in fact expected. Floppy drives, unlike CD-ROM drives, do not support locking the media in. Thus the drive (qemu) doesn't know whether the floppy is mounted in the guest or not.
Description of problem: Ejecting a busy floppy from guest causes I/O error Version-Release number of selected component (if applicable): - libvirt-0.8.7-8.el6.x86_64 - kernel-2.6.32-114.0.1.el6.x86_64 - qemu-kvm-0.12.1.2-2.144.el6.x86_64 How reproducible: always Steps to Reproduce: 1. Add a floppy to guest xml </disk> <disk type='block' device='floppy'> <driver name='qemu' type='raw'/> <source dev='/var/lib/libvirt/images/floppy1.img'/> <target dev='fda' bus='fdc'/> </disk> 2. Define and start the guest 3. In guest, # modprobe floppy # mount /dev/fd0 /mnt 4.Prepare a eject.xml # cat eject.xml <disk type='block' device='floppy'> <target dev='fda' bus='fdc'/> </disk> 5. # virsh update-device rhel61_i386_11 eject.xml Device updated successfully Actual results: 5. Could eject a busy floppy in guest without --force, and seconds later, could see I/O error in guest (please see the attachment) Expected results: 6. Should cannot eject a busy floppy in guest without --force, surely should not cause I/O error in guest Additional info: