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.
If only one floppy drive is present on a Microsoft Windows guest and the isa-fdc.driveB property is set, the following error message can appear when attempting to access the drive:
A:\ is not accessible.
The floppy disk controller returned inconsistent results in its registers.
This problem only occurs when using the QEMU command line directly, which is not supported. To work around this problem, specify the isa-fdc.driveA property when using a single floppy drive.
Description of problem:
Boot win8_64 guest with only one floppy with isa-fdc.driveB, guest can not use this floppy. when access this floppy, it will show error message :"A:\ is not accessible. The floppy disk controller returned inconsistent results in its registers.".
Version-Release number of selected component (if applicable):
3.10.0-11.el7.x86_64
qemu-kvm-1.5.2-4.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1.Boot win8_64 guest with only one floppy with isa-fdc.driveB.
#<qemu-kvm cli> ... -drive file=/home/floppy2.vfd,if=none,id=drive-fdc0-0-0,format=raw -global isa-fdc.driveB=drive-fdc0-0-0 ...
2.open floppy inside guest.
3.Check the error message.
Actual results:
When access the floppy, it will get a error message as attachment picture.
Expected results:
Can access floppy as normal with no error.
Additional info:
I also test linux guest, it could access this floppy correctly.
For win7_64 guest, it hits the same error.
When boot win8_64 guest with only one floppy with isa-fdc.driveA, guest could access this floppy correctly as normal.
Jun Li,
I assume that this is not a regression, and if indeed it is not a regression, then I prefer not to fix it.
Practically speaking, this is a rare situation that as you said can be easily
be worked around by using disk-A, or better using an ISO (floppy is really needed only for XP boot-time driver's installation).
Can you check if the problem existed also for RHEL6.4 with Win7 guests.
Thanks.
(In reply to Ronen Hod from comment #3)
> Jun Li,
>
> I assume that this is not a regression, and if indeed it is not a
> regression, then I prefer not to fix it.
> Practically speaking, this is a rare situation that as you said can be easily
> be worked around by using disk-A, or better using an ISO (floppy is really
> needed only for XP boot-time driver's installation).
> Can you check if the problem existed also for RHEL6.4 with Win7 guests.
>
> Thanks.
On RHEL7 with qemu-kvm-1.4.0-4.el7.x86_64 with Win7 guests
Hit the same issue.
kernel version:3.10.0-18.el7.x86_64
On RHEL6.5 with Win7 guests
Hit this issue, too.
kernel and qemu-kvm version:
2.6.32-416.el6.x86_64
qemu-kvm-0.12.1.2-2.394.el6.x86_64
On released RHEL-6.4 with Win7 guests
Hit the same issue.
kernel and qemu-kvm version:
2.6.32-358.el6.x86_64
qemu-kvm-0.12.1.2-2.355.el6.x86_64
In my original thoughts, I thought I have hit this issue, so filed this bug. Now, I know this is not a regression. So I think whether fix this issue or not is ok. Thank you for your detailed explanations.