Bug 1428641
Summary: | [virtio-win][viostor]Windows guest's physical block size change to "512" after installation with the size "4096" | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | aihua liang <aliang> | |
Component: | virtio-win | Assignee: | Vadim Rozenfeld <vrozenfe> | |
virtio-win sub component: | virtio-win-prewhql | QA Contact: | Virtualization Bugs <virt-bugs> | |
Status: | CLOSED ERRATA | Docs Contact: | ||
Severity: | unspecified | |||
Priority: | unspecified | CC: | ailan, aliang, chayang, coli, dkutalek, jen, juzhang, kanderso, knoel, lijin, phou, virt-bugs, virt-maint, vrozenfe, xuwei, yfu | |
Version: | 8.0 | |||
Target Milestone: | rc | |||
Target Release: | 8.0 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | If docs needed, set a value | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1645343 1721248 (view as bug list) | Environment: | ||
Last Closed: | 2019-07-30 14:22:06 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: | 1645343, 1721248, 1725380 |
Description
aihua liang
2017-03-03 02:49:11 UTC
same as https://bugzilla.redhat.com/show_bug.cgi?id=1134679#c13 If rhel guest does not hit this issue,I suggest change component to virtio-win The bug also exist in RHEL+qemu-kvm kernel version:3.10.0-568.el7.x86_64 qemu-kvm version:qemu-kvm-1.5.3-132.el7.x86_64 Test Result: ERROR 1-smp_8.1024m.repeat1.run_test.Host_RHEL.m7.u4.qcow2.virtio_blk.up.virtio_net.Win2016.x86_64.io-github-autotest-qemu.check_block_size.4096_512.extra_cdrom_ks -> TestSetupFail: Block size in guest doesn't match with qemu parameter Physical block size in guest: 512, expect: 4096 Logical block size in guest: 512, expect: 512 BTY, the problem not exist on rhel guest. according to lijin's suggestion, change component to virtio-win. Hit this bug on RHEL7.5 host with Win8-32 guest. Used version info: kernel-3.10.0-768.el7.x86_64 qemu-kvm-rhev-2.10.0-4.el7.x86_64 virtio-win-1.9.3-1.el7 *** Bug 1448021 has been marked as a duplicate of this bug. *** fix committed and merged upstream https://github.com/virtio-win/kvm-guest-drivers-windows/pull/312 Hi Vadim, I saw this bug has been in post status for a long time. Could you help to generate a new build for it so QE can verify it? Thanks a lot Hi Li Jin. Please give a try to build 163 https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=812055 Thanks, Vadim (In reply to Vadim Rozenfeld from comment #9) > Hi Li Jin. > > Please give a try to build 163 > https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=812055 > I tested with build 163, cannot reproduce this issue. Used versions: kernel-4.18.0-48.el8.x86_64 qemu-kvm-common-3.1.0-0.module+el8+2266+616cf026.next.candidate.x86_64 seabios-bin-1.11.1-2.module+el8+2179+85112f94.noarch virtio-win-prewhql-163 Changed status to verified. Thanks a lot~ Peixiu (In reply to Peixiu Hou from comment #10) > (In reply to Vadim Rozenfeld from comment #9) > > Hi Li Jin. > > > > Please give a try to build 163 > > https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=812055 > > > > I tested with build 163, cannot reproduce this issue. > > Used versions: > kernel-4.18.0-48.el8.x86_64 > qemu-kvm-common-3.1.0-0.module+el8+2266+616cf026.next.candidate.x86_64 > seabios-bin-1.11.1-2.module+el8+2179+85112f94.noarch > virtio-win-prewhql-163 > > Changed status to verified. > > Thanks a lot~ > Peixiu Thank you. Vadim. *** Bug 1645343 has been marked as a duplicate of this bug. *** change status to verified according to comment#10 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:1997 |