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:

$ qemu-system-x86_64  -device 
virtio-blk-pci,logical_block_size=4096,physical_block_size=4096,drive=boot
-drive file=/tmp/a.qcow2,if=none,id=boot

gives me: Floating point exception

The crash is in hw/virtio-blk.c:505 blkcfg.blk_size is zero because
s->conf->logical_block_size is zero.

Analyzed by armbru: setting physical_block_size overwrites logical_block_size due to incorrect use of inttypes macros in parse_uint16().

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Reproduced in qemu-kvm-0.12.1.2-2.69.el6

Verified in qemu-kvm-0.12.1.2-2.71.el6

Steps:
1.start VM with following command.
#/usr/libexec/qemu-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -name tt -uuid `uuidgen` -rtc-td-hack -boot c -drive file=/home/RHEL-Server-6.0-64-virtio.raw,if=none,id=drive-virtio0-0-0,boot=on,format=raw -device virtio-blk-pci,drive=drive-virtio0-0-0,id=ide0-0-0,logical_block_size=4096,physical_block_size=4096 -net nic,macaddr=20:40:50:12:23:21,model=virtio,vlan=0 -net tap,script=/etc/qemu-ifup,vlan=0 -vnc :8 -monitor stdio

Actual Results:
qemu-kvm will not crash for Floating point exception,Guest can work successfully.

The bug has already been fixed.

according to #c7. closing