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.
Created attachment 584646[details]
libvirtd log file
Description of problem:
Guest will die if try to mount a disconnected floppy driver.
Version-Release number of selected component (if applicable):
virt-manager-0.9.0-14.el6.x86_64
libvirt-0.9.10-18.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Make sure there is a running guest.
2. Add a floppy device and connect to an img file.
3. Run #modprobe floppy in guest.
4. Run #mount /dev/floppy /mnt in guest.
5. Make sure floppy image has been mounted to /mnt
6. Run #umount /mnt in guest.
7. Create a floppy eject XML.
#cat eject.xml
<disk type='block' device='floppy'>
<target dev='fda' bus='fdc'/>
</disk>
8. Run #virsh update-device $guest eject.xml in host
9. Run #mount /dev/floppy /mnt in guest.
Actual results:
1. After step 9. Guest will die.
Expected results:
1. Guest should keep living.
Additional info:
(In reply to comment #2)
> This looks to me like qemu crashing, so I've changed the component to qemu-kvm.
> If that's not the case, please reassign back to libvirt.
Did the kernel crashed (maybe a kernel issue) or was it qemu?
Looks like kernel crash. I can get a line from guest: "Kernel panic - not syncing: Fatal exception."
Comment 6Markus Armbruster
2012-07-17 11:15:10 UTC
For a guest kernel crash, please provide guest kernel version information. Output of "uname -a" in guest should do. Also provide guest's dmesg. Recommend to capture it on a serial console.
This bug will be fixed by patches for bug 729244. You can try the whole patch-file attached for that bug.
Comment 9Markus Armbruster
2012-07-25 15:33:02 UTC
This bug report is really two bugs:
1. A bug in qemu-kvm floppy device model. Probably a duplicate of bug 729244 mentioned in comment#8.
2. A bug in the guest kernel, which really shouldn't crash just because the floppy controller acts up. Probably a duplicate of bug 815472.
(In reply to comment #8)
> This bug will be fixed by patches for bug 729244. You can try the whole
> patch-file attached for that bug.
(In reply to comment #9)
> This bug report is really two bugs:
>
> 1. A bug in qemu-kvm floppy device model. Probably a duplicate of bug
> 729244 mentioned in comment#8.
>
> 2. A bug in the guest kernel, which really shouldn't crash just because the
> floppy controller acts up. Probably a duplicate of bug 815472.
Closing as duplicate of Bug 729244. This scenario should be included in the testcase of Bug 729244.
*** This bug has been marked as a duplicate of bug 729244 ***
Created attachment 584646 [details] libvirtd log file Description of problem: Guest will die if try to mount a disconnected floppy driver. Version-Release number of selected component (if applicable): virt-manager-0.9.0-14.el6.x86_64 libvirt-0.9.10-18.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. Make sure there is a running guest. 2. Add a floppy device and connect to an img file. 3. Run #modprobe floppy in guest. 4. Run #mount /dev/floppy /mnt in guest. 5. Make sure floppy image has been mounted to /mnt 6. Run #umount /mnt in guest. 7. Create a floppy eject XML. #cat eject.xml <disk type='block' device='floppy'> <target dev='fda' bus='fdc'/> </disk> 8. Run #virsh update-device $guest eject.xml in host 9. Run #mount /dev/floppy /mnt in guest. Actual results: 1. After step 9. Guest will die. Expected results: 1. Guest should keep living. Additional info: