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.

Rationale:
http://thread.gmane.org/gmane.comp.emulators.qemu.block/2054

Upstream commits:
1 fd53c87 i386/pc: pc_basic_device_init(): delegate FDC creation request
2 936a7c1 i386/pc: '-drive if=floppy' should imply a board-default FDC
3 6cd2234 i386/pc_q35: don't insist on board FDC if there's no default floppy
4 ea96bc6 i386: drop FDC in pc-q35-2.4+ if neither it nor floppy drives are
          wanted

This bug only exists due to a bugzilla glitch. When I filed bug 1227282, I got an internal server error instead of the fresh bug, so -- not wanting to lose the data I had entered -- I clicked "submit nonetheless". Turns out the same was filed twice.

*** This bug has been marked as a duplicate of bug 1227282 ***