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:
separate this bug from bug 1134693 for ide fail to specify the physical_block_size.

Version-Release number of selected component (if applicable):
host info:
# uname -r && rpm -q qemu-kvm
2.6.32-538.el6.x86_64
qemu-kvm-0.12.1.2-2.454.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1.launch a KVM guest with physical_block_size=1024 specified.
e.g:...-drive file=/home/my-data-disk1.qcow2,if=none,id=drive-data-disk1,format=qcow2,cache=none,aio=native -device ide-drive,drive=drive-data-disk1,id=data-disk1,bus=ide.0,unit=0,physical_block_size=1024

2.(qemu) info qtree
...
          type IDE
          dev: ide-drive, id "data-disk1"
            dev-prop: unit = 0
            dev-prop: drive = drive-data-disk1
            dev-prop: logical_block_size = 512
            dev-prop: physical_block_size = 1024
3.check the physical_block_size from guest.
# cat /sys/block/sda/queue/physical_block_size

Actual results:
after step 3, it fail to emulate the physical_block_size correctly.
# cat /sys/block/sda/queue/physical_block_size
512

Expected results:
the physical_block_size should be 1024 in guest.

Additional info:

Are you sure that you reproduced this with the fix for bug 1134693? For me, it
just works now.

(In reply to Kevin Wolf from comment #1)
> Are you sure that you reproduced this with the fix for bug 1134693? For me,
> it
> just works now.
It also works for me now, did not find any unusual, thanks.

# rpm -q qemu-kvm
qemu-kvm-0.12.1.2-2.454.el6.x86_64
# rpm -q --changelog qemu-kvm-0.12.1.2-2.454.el6.x86_64 | grep 1134693
- kvm-ide-Check-validity-of-logical-block-size.patch [bz#1134693]
- Resolves: bz#1134693

e.g:...-drive file=/home/my-data-disk1.qcow2,if=none,id=drive-data-disk1,format=qcow2,cache=none,aio=native -device ide-drive,drive=drive-data-disk1,id=data-disk1,bus=ide.0,unit=0,physical_block_size=1024

# cat /sys/block/sda/queue/physical_block_size
1024