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:
Install fail with 4k physical block size and 4k logical_block_size option

Version-Release number of selected component (if applicable):
qemu-kvm-0.12.1.2-2.126.el6.x86_64
virtio-win-1.1.16

How reproducible:
2/2

Steps to Reproduce:
1.launch win7 guest with cli:
-drive file=/home/windows7.img,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,boot=on,werror=stop,rerror=stop 
-device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,physical_block_size=4096,logical_block_size=4096 
-fda /home/virtio-win-1.1.16.vfd

2.error pops up after start installation about 10mins as attached screenshot

  
Actual results:
error happens, installation fail.

Expected results:
install guest finish, and boot ok.

Additional info:

guest can finish installation and boot ok without physical_block_size and logical_block_size option.

Created attachment 469924 [details]
screen shot when error happens

For RHEL guest, when add physical_block_size=4096,logical_block_size=4096 to command line, guest can finish installation, while guest can not boot up as screen shot.

So change Component to qemu-kvm.

Created attachment 470113 [details]
guest stuck on this stage

Does windows support a 4k logical block size at all?  And if yes do our virtio-blk drivers for windows support it?  I'd be very surprised if Windows does so, as there are no 4k logical drives for PC-class hardware.

(In reply to comment #5)
> Does windows support a 4k logical block size at all?  And if yes do our
> virtio-blk drivers for windows support it?  I'd be very surprised if Windows
> does so, as there are no 4k logical drives for PC-class hardware.

Yes for both of your question.
But, Windows can be installed/booted only from GPT 4K sector size disk.
To be able to install from or boot to a GPT disk you need EFI hardware, otherwise GPT is only supported as a data drive.

Okay, given that we don't support EFI yet closing this for now