Bug 2112303
Summary: | virtio-blk: Can't boot fresh installation from used 512 cluster_size image under certain conditions | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | bfu <bfu> |
Component: | qemu-kvm | Assignee: | Thomas Huth <thuth> |
qemu-kvm sub component: | virtio-blk,scsi | QA Contact: | bfu <bfu> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | medium | ||
Priority: | high | CC: | cohuck, coli, dgilbert, hannsj_uhl, jinzhao, juzhang, knoel, lijin, pbonzini, ribarry, smitterl, stefanha, thuth, vgoyal, virt-maint, virt-qe-z, yiwei |
Version: | 9.1 | Keywords: | Regression, Triaged |
Target Milestone: | rc | ||
Target Release: | 9.1 | ||
Hardware: | s390x | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | qemu-kvm-7.0.0-11.el9 | Doc Type: | No Doc Update |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-11-15 09:54:42 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: |
Description
bfu
2022-07-29 09:53:16 UTC
Hi Boqiao, one question: Is this really a regression (since the "Regression" keyword has been set), or did this simply never work? Ah, I think I now understood what is going on here. When fixing BZ 2098076 by removing the "hack" in the firmware that was enforcing 512 byte sectors in some cases (and thus preventing the disk with the 4096 there, see https://gitlab.com/qemu-project/qemu/-/commit/5447de2619050a0a4d ), this uncovered another problem in the s390-ccw bios: It tries to access the sectors with the physical block size numbers, not with the logical ones, which is nonsense. For this specific case here, it used to work in the past since the "hack" enforced 512 byte sectors again, but since the hack has been removed, it is failing now. Anyway, the right thing to do is to simply switch to use the logical block sizes in the s390-ccw bios. I suggested a patch here: https://lore.kernel.org/qemu-devel/20220805094214.285223-1-thuth@redhat.com/ Test result: JOB ID : 2a09f9e7544bcebd320513b1c90d3a83c9ceda7e JOB LOG : /root/avocado/job-results/job-2022-08-11T11.42-2a09f9e/job.log (1/2) Host_RHEL.m9.u1.nographic.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.9.1.0.s390x.io-github-autotest-qemu.unattended_install.cdrom.extra_cdrom_ks.default_install.aio_threads.s390-virtio: STARTED (1/2) Host_RHEL.m9.u1.nographic.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.9.1.0.s390x.io-github-autotest-qemu.unattended_install.cdrom.extra_cdrom_ks.default_install.aio_threads.s390-virtio: PASS (675.59 s) (2/2) Host_RHEL.m9.u1.nographic.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.9.1.0.s390x.io-github-autotest-qemu.check_block_size.4096_512.extra_cdrom_ks.s390-virtio: STARTED (2/2) Host_RHEL.m9.u1.nographic.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.9.1.0.s390x.io-github-autotest-qemu.check_block_size.4096_512.extra_cdrom_ks.s390-virtio: PASS (681.97 s) RESULTS : PASS 2 | ERROR 0 | FAIL 0 | SKIP 0 | WARN 0 | INTERRUPT 0 | CANCEL 0 JOB HTML : /root/avocado/job-results/job-2022-08-11T11.42-2a09f9e/results.html JOB TIME : 1360.84 s As the test result, add verified: tested to this bz JOB ID : 478e6bbf927de9529e0239298bb34053130be8bf JOB LOG : /root/avocado/job-results/job-2022-08-16T23.37-478e6bb/job.log (1/5) Host_RHEL.m9.u1.nographic.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.9.1.0.s390x.io-github-autotest-qemu.unattended_install.cdrom.extra_cdrom_ks.default_install.aio_threads.s390-virtio: STARTED (1/5) Host_RHEL.m9.u1.nographic.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.9.1.0.s390x.io-github-autotest-qemu.unattended_install.cdrom.extra_cdrom_ks.default_install.aio_threads.s390-virtio: PASS (552.67 s) (2/5) Host_RHEL.m9.u1.nographic.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.9.1.0.s390x.io-github-autotest-qemu.check_block_size.4096_4096.base.s390-virtio: STARTED (2/5) Host_RHEL.m9.u1.nographic.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.9.1.0.s390x.io-github-autotest-qemu.check_block_size.4096_4096.base.s390-virtio: PASS (27.75 s) (3/5) Host_RHEL.m9.u1.nographic.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.9.1.0.s390x.io-github-autotest-qemu.check_block_size.4096_512.extra_cdrom_ks.s390-virtio: STARTED (3/5) Host_RHEL.m9.u1.nographic.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.9.1.0.s390x.io-github-autotest-qemu.check_block_size.4096_512.extra_cdrom_ks.s390-virtio: PASS (587.67 s) (4/5) Host_RHEL.m9.u1.nographic.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.9.1.0.s390x.io-github-autotest-qemu.check_block_size.512_512.extra_cdrom_ks.s390-virtio: STARTED (4/5) Host_RHEL.m9.u1.nographic.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.9.1.0.s390x.io-github-autotest-qemu.check_block_size.512_512.extra_cdrom_ks.s390-virtio: PASS (586.49 s) (5/5) Host_RHEL.m9.u1.nographic.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.9.1.0.s390x.io-github-autotest-qemu.check_block_size.4096_4096_cluster_install.extra_cdrom_ks.s390-virtio: STARTED (5/5) Host_RHEL.m9.u1.nographic.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.9.1.0.s390x.io-github-autotest-qemu.check_block_size.4096_4096_cluster_install.extra_cdrom_ks.s390-virtio: PASS (591.47 s) RESULTS : PASS 5 | ERROR 0 | FAIL 0 | SKIP 0 | WARN 0 | INTERRUPT 0 | CANCEL 0 JOB HTML : /root/avocado/job-results/job-2022-08-16T23.37-478e6bb/results.html JOB TIME : 2354.38 s As the test result, set this bz to verified 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 (Moderate: qemu-kvm security, bug fix, and enhancement update), 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/RHSA-2022:7967 |