Bug 1134679
Summary: | [virtio-win][virtio scsi] fail to specify the physical_block_size/logical_block_size value not 512 for virtio-scsi disk | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Sibiao Luo <sluo> | ||||
Component: | virtio-win | Assignee: | Vadim Rozenfeld <vrozenfe> | ||||
virtio-win sub component: | virtio-win-prewhql | QA Contact: | Virtualization Bugs <virt-bugs> | ||||
Status: | CLOSED WONTFIX | Docs Contact: | |||||
Severity: | medium | ||||||
Priority: | medium | CC: | chayang, coli, famz, hhuang, juzhang, lijin, michen, phou, qzhang, virt-bugs, virt-maint, vrozenfe, wyu, xfu, xuwei, yvugenfi | ||||
Version: | 7.0 | ||||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2018-08-07 08:27:24 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 1558351 | ||||||
Attachments: |
|
Description
Sibiao Luo
2014-08-28 05:19:02 UTC
Also tried the rhel guest with the same testing which did not hit it. # cat /sys/block/sdb/queue/logical_block_size 1024 # cat /sys/block/sdb/queue/physical_block_size 1024 Best Regards, sluo Created attachment 931723 [details]
screenshot for the Error.
Also tried the physical_block_size/logical_block_size=4096 with bcao's request for windows guest which also hit the same issue. Sibiao, I would expect 512 and 4096 to work. These are the standard real hardware sizes. Vadim will probably have better answers. Postponed to 7.2, as we are out of capacity for 7.1 can we please check if the problem still exists? Just don't forget to re-format disk after changing physical or logical block size. Thank you, Vadim. For system disk: - with logical_block_size=512,guest can be installed correctly,"fsutil fsinfo ntfsinfo " can show correct info; - with logical_block_size=1024/2048/4096,guest can NOT be installed(please check the attachment) - with physical_block_size=512/1024/2048/4096,guest can be installed correctly,"fsutil fsinfo ntfsinfo " can show correct info; For data disk - physical_block_size and logical_block_size=512/1024/2048/4096,all work well,"fsutil fsinfo ntfsinfo " can show correct info Testing package info: virtio-win-prewhql-132 qemu-kvm-rhev-2.8.0-4.el7.x86_64 kernel-3.10.0-563.el7.x86_64 seabios-1.9.1-5.el7_3.1.x86_64 guest:windows 2016 Vadim, scsi system disk logical_block_size does NOT support 1024/2048/4096,could you help to check is it normal? Thanks (In reply to lijin from comment #9) > For system disk: > - with logical_block_size=512,guest can be installed correctly,"fsutil > fsinfo ntfsinfo " can show correct info; > - with logical_block_size=1024/2048/4096,guest can NOT be installed(please > check the attachment) > - with physical_block_size=512/1024/2048/4096,guest can be installed > correctly,"fsutil fsinfo ntfsinfo " can show correct info; > > > For data disk > - physical_block_size and logical_block_size=512/1024/2048/4096,all work > well,"fsutil fsinfo ntfsinfo " can show correct info > > > Testing package info: > virtio-win-prewhql-132 > qemu-kvm-rhev-2.8.0-4.el7.x86_64 > kernel-3.10.0-563.el7.x86_64 > seabios-1.9.1-5.el7_3.1.x86_64 > guest:windows 2016 > > Vadim, > scsi system disk logical_block_size does NOT support 1024/2048/4096,could > you help to check is it normal? > Thanks a lot Lijin. Will do it soon. Could you please tell me if logical size was always equal or bigger than physical size for this case? Best regards, Vadim. > Thanks (In reply to Vadim Rozenfeld from comment #11) > (In reply to lijin from comment #9) > > For system disk: > > - with logical_block_size=512,guest can be installed correctly,"fsutil > > fsinfo ntfsinfo " can show correct info; > > - with logical_block_size=1024/2048/4096,guest can NOT be installed(please > > check the attachment) > > - with physical_block_size=512/1024/2048/4096,guest can be installed > > correctly,"fsutil fsinfo ntfsinfo " can show correct info; > > > > > > For data disk > > - physical_block_size and logical_block_size=512/1024/2048/4096,all work > > well,"fsutil fsinfo ntfsinfo " can show correct info > > > > > > Testing package info: > > virtio-win-prewhql-132 > > qemu-kvm-rhev-2.8.0-4.el7.x86_64 > > kernel-3.10.0-563.el7.x86_64 > > seabios-1.9.1-5.el7_3.1.x86_64 > > guest:windows 2016 > > > > Vadim, > > scsi system disk logical_block_size does NOT support 1024/2048/4096,could > > you help to check is it normal? > > > > Thanks a lot Lijin. > Will do it soon. Could you please tell me if logical size was always equal > or bigger than physical size for this case? I tried with following matrix,all hit the sam issue: physical_block_size=512,logical_block_size=1024 physical_block_size=1024,logical_block_size=1024 physical_block_size=2048,logical_block_size=1024 BTW,I saw a comment "Windows can be installed/booted only from GPT 4K sector size disk." in https://bugzilla.redhat.com/show_bug.cgi?id=664659#c6. I'm not sure if this also apply to other sector size. Hi Vadim, 1 For virtio-scsi device(data disk): when logical_block_size > physical_block_size , "Bytes Per Sector" and "Bytes Per Physical Sector" show the "logical_block_size" when logical_block_size < physical_block_size , "Bytes Per Sector" shows logical size and "Bytes Per Physical Sector" shows physical size. 2 For virtio-blk device (data disk): No matter > or < , "Bytes Per Sector" and "Bytes Per Physical Sector" both show the "logical_block_size" Is that normal or a bug (vioscsi and viostor)? Thanks Yu Wang (In reply to lijin from comment #12) > (In reply to Vadim Rozenfeld from comment #11) > > (In reply to lijin from comment #9) > > > For system disk: > > > - with logical_block_size=512,guest can be installed correctly,"fsutil > > > fsinfo ntfsinfo " can show correct info; > > > - with logical_block_size=1024/2048/4096,guest can NOT be installed(please > > > check the attachment) > > > - with physical_block_size=512/1024/2048/4096,guest can be installed > > > correctly,"fsutil fsinfo ntfsinfo " can show correct info; > > > > > > > > > For data disk > > > - physical_block_size and logical_block_size=512/1024/2048/4096,all work > > > well,"fsutil fsinfo ntfsinfo " can show correct info > > > > > > > > > Testing package info: > > > virtio-win-prewhql-132 > > > qemu-kvm-rhev-2.8.0-4.el7.x86_64 > > > kernel-3.10.0-563.el7.x86_64 > > > seabios-1.9.1-5.el7_3.1.x86_64 > > > guest:windows 2016 > > > > > > Vadim, > > > scsi system disk logical_block_size does NOT support 1024/2048/4096,could > > > you help to check is it normal? > > > > > > > Thanks a lot Lijin. > > Will do it soon. Could you please tell me if logical size was always equal > > or bigger than physical size for this case? > > I tried with following matrix,all hit the sam issue: > physical_block_size=512,logical_block_size=1024 > physical_block_size=1024,logical_block_size=1024 > physical_block_size=2048,logical_block_size=1024 > > > BTW,I saw a comment "Windows can be installed/booted only from GPT 4K sector > size disk." in https://bugzilla.redhat.com/show_bug.cgi?id=664659#c6. > I'm not sure if this also apply to other sector size. It's still relevant. As far as I remember, for the system disk we supposed to be able to support the following matrix: logical size/physical size 4096/4096 512/512 512/4096 Hi vadim, For virtio scsi, I tested some configuration on rhel7.6 host. I checked this issue https://bugzilla.redhat.com/show_bug.cgi?id=566785, and combined your answer in the comment#14, have a question want to confirm: For system disk, If it's only support follow configurations? logical size/physical size 512/512 512/4096 if yes, for 4096/4096 configuration, could tell the reason why not support? For data disk, if only support follows? logical size/physical size 4096/4096 512/512 512/4096 Test summary: Guest os: win2016 1. Tested with logical_block_size=512,physical_block_size=4096 on system disk, can get the system disk information in the guest: LogicalSectorSize : 512 PhysicalSectorSize : 4096 2. Tested with logical_block_size=512,physical_block_size=512 on system disk, can get the system disk information in the guest: LogicalSectorSize : 512 PhysicalSectorSize : 512 3. Tried with logical_block_size=4096,physical_block_size=4096 on system disk, cannot boot in the guest. 4. Tested with logical_block_size=512,physical_block_size=4096 on data disk, can get the data disk information in the guest: LogicalSectorSize : 512 PhysicalSectorSize : 4096 5. Tested with logical_block_size=512,physical_block_size=512 on data disk, can get the data disk information in the guest: LogicalSectorSize : 512 PhysicalSectorSize : 512 6. Tested with logical_block_size=4096,physical_block_size=4096 on data disk, can get the data disk information in the guest: LogicalSectorSize : 4096 PhysicalSectorSize : 4096 Used virtio-win prewhql-157 build. Thanks a lot~ Peixiu (In reply to Peixiu Hou from comment #19) > Hi vadim, > > For virtio scsi, I tested some configuration on rhel7.6 host. > I checked this issue https://bugzilla.redhat.com/show_bug.cgi?id=566785, and > combined your answer in the comment#14, have a question want to confirm: > For system disk, If it's only support follow configurations? > logical size/physical size > 512/512 > 512/4096 > if yes, for 4096/4096 configuration, could tell the reason why not support? I guess it might be a BIOS (SeaBios) problem, but we need to check it. What about UEFI? Can you give it a try to see if it works or not? Thanks, Vadim. > > For data disk, if only support follows? > logical size/physical size > 4096/4096 > 512/512 > 512/4096 > > Test summary: > Guest os: win2016 > > 1. Tested with logical_block_size=512,physical_block_size=4096 on system > disk, can get the system disk information in the guest: > LogicalSectorSize : 512 > PhysicalSectorSize : 4096 > > 2. Tested with logical_block_size=512,physical_block_size=512 on system > disk, can get the system disk information in the guest: > LogicalSectorSize : 512 > PhysicalSectorSize : 512 > > 3. Tried with logical_block_size=4096,physical_block_size=4096 on system > disk, cannot boot in the guest. > > 4. Tested with logical_block_size=512,physical_block_size=4096 on data disk, > can get the data disk information in the guest: > LogicalSectorSize : 512 > PhysicalSectorSize : 4096 > > 5. Tested with logical_block_size=512,physical_block_size=512 on data disk, > can get the data disk information in the guest: > LogicalSectorSize : 512 > PhysicalSectorSize : 512 > > 6. Tested with logical_block_size=4096,physical_block_size=4096 on data > disk, can get the data disk information in the guest: > LogicalSectorSize : 4096 > PhysicalSectorSize : 4096 > > Used virtio-win prewhql-157 build. > > Thanks a lot~ > Peixiu (In reply to Vadim Rozenfeld from comment #20) > (In reply to Peixiu Hou from comment #19) > > Hi vadim, > > > > For virtio scsi, I tested some configuration on rhel7.6 host. > > I checked this issue https://bugzilla.redhat.com/show_bug.cgi?id=566785, and > > combined your answer in the comment#14, have a question want to confirm: > > For system disk, If it's only support follow configurations? > > logical size/physical size > > 512/512 > > 512/4096 > > if yes, for 4096/4096 configuration, could tell the reason why not support? > > I guess it might be a BIOS (SeaBios) problem, but we need to check it. What > about UEFI? Can you give it a try to see if it works or not? > Hi Vadim I tried test with UEFI(under q35+ovmf), guest can be installed successfully with logical_block_size=4096,physical_block_size=4096 for system disk. and check in guest the logical block size and physical block size, both report correct. related commands as follows: -drive if=pflash,format=raw,readonly=on,file=/usr/share/OVMF/OVMF_CODE.secboot.fd \ -drive if=pflash,format=raw,file=/home/kvm_autotest_root/images/win2016-64-virtio-scsi.qcow2.fd \ -device virtio-scsi-pci,num_queues=4,id=virtio_scsi_pci0,bus=pcie.0-root-port-6,addr=0x0 \ -drive id=drive_stg,if=none,snapshot=off,aio=threads,cache=none,format=qcow2,file=/home/kvm_autotest_root/images/check_block_size_image.qcow2 \ device scsi-hd,id=stg,drive=drive_stg,logical_block_size=4096,physical_block_size=4096,serial=TARGET_DISK0 \ Also tried with q35+seabios again, guest cannot be installed successfully with logical_block_size=4096,physical_block_size=4096 for system disk, the detected disk report error message "Windows cannot be installed to this disk. This computer's hardware may not support booting to this disk. Ensure that the disk's comtroller is enabled in the computer's BIOS menu" Could it mean the seabios doesn't support this configure? Best Regards~ Peixiu (In reply to Peixiu Hou from comment #21) > (In reply to Vadim Rozenfeld from comment #20) > > (In reply to Peixiu Hou from comment #19) > > > Hi vadim, > > > > > > For virtio scsi, I tested some configuration on rhel7.6 host. > > > I checked this issue https://bugzilla.redhat.com/show_bug.cgi?id=566785, and > > > combined your answer in the comment#14, have a question want to confirm: > > > For system disk, If it's only support follow configurations? > > > logical size/physical size > > > 512/512 > > > 512/4096 > > > if yes, for 4096/4096 configuration, could tell the reason why not support? > > > > I guess it might be a BIOS (SeaBios) problem, but we need to check it. What > > about UEFI? Can you give it a try to see if it works or not? > > > Hi Vadim > > I tried test with UEFI(under q35+ovmf), guest can be installed successfully > with logical_block_size=4096,physical_block_size=4096 for system disk. and > check in guest the logical block size and physical block size, both report > correct. related commands as follows: > > -drive > if=pflash,format=raw,readonly=on,file=/usr/share/OVMF/OVMF_CODE.secboot.fd \ > -drive > if=pflash,format=raw,file=/home/kvm_autotest_root/images/win2016-64-virtio- > scsi.qcow2.fd \ > -device > virtio-scsi-pci,num_queues=4,id=virtio_scsi_pci0,bus=pcie.0-root-port-6, > addr=0x0 \ > -drive > id=drive_stg,if=none,snapshot=off,aio=threads,cache=none,format=qcow2,file=/ > home/kvm_autotest_root/images/check_block_size_image.qcow2 \ > device > scsi-hd,id=stg,drive=drive_stg,logical_block_size=4096, > physical_block_size=4096,serial=TARGET_DISK0 \ > > Also tried with q35+seabios again, guest cannot be installed successfully > with logical_block_size=4096,physical_block_size=4096 for system disk, the > detected disk report error message "Windows cannot be installed to this > disk. This computer's hardware may not support booting to this disk. Ensure > that the disk's comtroller is enabled in the computer's BIOS menu" > > Could it mean the seabios doesn't support this configure? Looks like SeBIOS doen't support 4Kn native configuration. (But at least viostor is working fine with UEFI). We can expect the same problems with virtio-blk device as well. I would go forward and close this bug as WONTFIX and keep in mind that for system disk 4Kn configuration we need to use UEFI. Best regards, Vadim. > > Best Regards~ > Peixiu (In reply to Vadim Rozenfeld from comment #22) > (In reply to Peixiu Hou from comment #21) > > (In reply to Vadim Rozenfeld from comment #20) > > > (In reply to Peixiu Hou from comment #19) > > > > Hi vadim, > > > > > > > > For virtio scsi, I tested some configuration on rhel7.6 host. > > > > I checked this issue https://bugzilla.redhat.com/show_bug.cgi?id=566785, and > > > > combined your answer in the comment#14, have a question want to confirm: > > > > For system disk, If it's only support follow configurations? > > > > logical size/physical size > > > > 512/512 > > > > 512/4096 > > > > if yes, for 4096/4096 configuration, could tell the reason why not support? > > > > > > I guess it might be a BIOS (SeaBios) problem, but we need to check it. What > > > about UEFI? Can you give it a try to see if it works or not? > > > > > Hi Vadim > > > > I tried test with UEFI(under q35+ovmf), guest can be installed successfully > > with logical_block_size=4096,physical_block_size=4096 for system disk. and > > check in guest the logical block size and physical block size, both report > > correct. related commands as follows: > > > > -drive > > if=pflash,format=raw,readonly=on,file=/usr/share/OVMF/OVMF_CODE.secboot.fd \ > > -drive > > if=pflash,format=raw,file=/home/kvm_autotest_root/images/win2016-64-virtio- > > scsi.qcow2.fd \ > > -device > > virtio-scsi-pci,num_queues=4,id=virtio_scsi_pci0,bus=pcie.0-root-port-6, > > addr=0x0 \ > > -drive > > id=drive_stg,if=none,snapshot=off,aio=threads,cache=none,format=qcow2,file=/ > > home/kvm_autotest_root/images/check_block_size_image.qcow2 \ > > device > > scsi-hd,id=stg,drive=drive_stg,logical_block_size=4096, > > physical_block_size=4096,serial=TARGET_DISK0 \ > > > > Also tried with q35+seabios again, guest cannot be installed successfully > > with logical_block_size=4096,physical_block_size=4096 for system disk, the > > detected disk report error message "Windows cannot be installed to this > > disk. This computer's hardware may not support booting to this disk. Ensure > > that the disk's comtroller is enabled in the computer's BIOS menu" > > > > Could it mean the seabios doesn't support this configure? > > Looks like SeBIOS doen't support 4Kn native configuration. (But at least > viostor > is working fine with UEFI). We can expect the same problems with virtio-blk > device as well. I would go forward and close this bug as WONTFIX and keep in > mind that for system disk 4Kn configuration we need to use UEFI. > Agree with you, thanks for your confirm~ Best Regards~ Peixiu 4Kn installation works with UEFI but doesn't work with SeaBIOS due to its limitations. |