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.

Bug 1209708

Summary: floppy fail to be accessible(Location is not available) after change from none
Product: Red Hat Enterprise Linux 7 Reporter: Sibiao Luo <sluo>
Component: qemu-kvm-rhevAssignee: John Snow <jsnow>
Status: CLOSED ERRATA QA Contact: FuXiangChun <xfu>
Severity: high Docs Contact:
Priority: high    
Version: 7.2CC: chayang, famz, hhuang, juzhang, knoel, kwolf, michen, mkenneth, mrezanin, pbonzini, qzhang, rbalakri, rpacheco, virt-bugs, virt-maint, xfu
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: qemu-2.6.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1209707 Environment:
Last Closed: 2016-11-07 20:22:23 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: 1209362, 1209707    
Bug Blocks:    
Attachments:
Description Flags
screenshot_for_qemu-kvm-rhev-2.2.0-8.el7.x86_64 none

Comment 1 Sibiao Luo 2015-04-08 03:17:09 UTC 
Created attachment 1012009 [details]
screenshot_for_qemu-kvm-rhev-2.2.0-8.el7.x86_64
Comment 2 Sibiao Luo 2015-04-08 03:18:04 UTC 
host info:
# uname -r&& rpm -q qemu-kvm-rhev
3.10.0-232.el7.x86_64
qemu-kvm-rhev-2.2.0-8.el7.x86_64
guest info:
# rpm -q virtio-win
virtio-win-1.7.2-2.el6.noarch
/usr/share/virtio-win/virtio-win-1.7.2_amd64.vfd
Comment 4 John Snow 2015-06-30 20:01:43 UTC 
The problem is caused by QEMU's usage of the 1.44MB FDrive type as a default when no floppy is inserted. Our virtio-win drivers ship on a 2.88MB floppy drive image. There is currently no CLI interface to specify that a 2.88MB drive is desired, except by having an image present at boot.

I am delaying this BZ because it needs to be worked on upstream and will likely involve more research before a proper fix is identified.

I recommend releasing documentation informing users that it would be best to boot their machine with a 2.88MB FD image if they desire that functionality. In this particular case, this image is generally only useful at boot during a new VM installation, so impact is expected to be minimal.
Comment 6 John Snow 2016-05-16 18:14:56 UTC 
Should be fixed by rebase to 2.6.0.
Comment 8 FuXiangChun 2016-09-13 07:51:50 UTC 
according to comment0. reproduced but with qemu-kvm-rhev-2.3.0-31. 

verified this but with 3:qemu-kvm-rhev-2.6.0-23.el7
Comment 10 errata-xmlrpc 2016-11-07 20:22:23 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.

https://rhn.redhat.com/errata/RHBA-2016-2673.html