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.
Bug 2112296 - virtio-blk: Can't boot fresh installation from used 512 cluster_size image under certain conditions
Summary: virtio-blk: Can't boot fresh installation from used 512 cluster_size image un...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: qemu-kvm
Version: 8.7
Hardware: s390x
OS: Linux
high
medium
Target Milestone: rc
: 8.7
Assignee: Thomas Huth
QA Contact: bfu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-29 09:24 UTC by bfu
Modified: 2022-11-08 09:47 UTC (History)
18 users (show)

Fixed In Version: qemu-kvm-6.2.0-19.module+el8.7.0+16358+eef3c6a2
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-08 09:20:55 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gitlab redhat/rhel/src/qemu-kvm qemu-kvm merge_requests 207 0 None None None 2022-08-09 07:46:35 UTC
Red Hat Bugzilla 2112303 0 high CLOSED virtio-blk: Can't boot fresh installation from used 512 cluster_size image under certain conditions 2023-07-18 11:23:31 UTC
Red Hat Issue Tracker RHELPLAN-129638 0 None None None 2022-07-29 09:45:07 UTC
Red Hat Product Errata RHSA-2022:7472 0 None None None 2022-11-08 09:21:47 UTC

Internal Links: 2112303

Description bfu 2022-07-29 09:24:01 UTC 
Description of problem:
When using an image with 512k cluster_size, and installing guest with physical size=4096&logical size=512, guest could not reboot after installation

Version-Release number of selected component (if applicable):
kernel version: 4.18.0-409.el8.s390x
qemu version: qemu-img-6.2.0-17.module+el8.7.0+15924+b11d8c3f.s390x
libvirt version: libvirt-8.0.0-9.module+el8.7.0+15830+85788ab7.s390x

How reproducible:
100%

Steps to Reproduce:
1. create an image file that has a cluster size of 512k
qemu-img create -f qcow2 test.qcow2 20G

2. install guest into the created image file with
physical_block_size = 4096, logical_block_size = 512

3. reboot guest after installation finished

Actual results:
guest cannot reboot
2022-07-28 07:30:29: Powering off.
2022-07-28 07:32:40: (Process terminated with status 0)
2022-07-28 07:32:44: LOADPARM=[        ]
2022-07-28 07:32:44: Using virtio-blk.
2022-07-28 07:32:44: Using SCSI scheme.
2022-07-28 07:32:44: 
2022-07-28 07:32:44: ! No zIPL magic in PT !
2022-07-28 07:45:24: (Process terminated with status 0)

Expected results:
guest could reboot successfully

Additional info:
Comment 3 bfu 2022-08-11 17:13:38 UTC 
Test result:
JOB ID     : 72a1c81e13e7b75d3bcf1ee12ec7bd23433aad23
JOB LOG    : /root/avocado/job-results/job-2022-08-11T11.22-72a1c81/job.log
 (1/2) Host_RHEL.m8.u7.nographic.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.8.7.0.s390x.io-github-autotest-qemu.unattended_install.cdrom.extra_cdrom_ks.default_install.aio_threads.s390-virtio: STARTED
 (1/2) Host_RHEL.m8.u7.nographic.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.8.7.0.s390x.io-github-autotest-qemu.unattended_install.cdrom.extra_cdrom_ks.default_install.aio_threads.s390-virtio: PASS (775.23 s)
 (2/2) Host_RHEL.m8.u7.nographic.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.8.7.0.s390x.io-github-autotest-qemu.check_block_size.4096_512.extra_cdrom_ks.s390-virtio: STARTED
 (2/2) Host_RHEL.m8.u7.nographic.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.8.7.0.s390x.io-github-autotest-qemu.check_block_size.4096_512.extra_cdrom_ks.s390-virtio: PASS (809.91 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.22-72a1c81/results.html
JOB TIME   : 1589.68 s

As the test result, add verified: tested to this bz
Comment 6 bfu 2022-08-18 10:16:02 UTC 
Test result:
JOB ID     : b46d5622d781594a03201628207d6065954236e3
JOB LOG    : /root/avocado/job-results/job-2022-08-18T05.23-b46d562/job.log
 (1/5) Host_RHEL.m8.u7.product_rhel.nographic.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.8.7.0.s390x.io-github-autotest-qemu.unattended_install.cdrom.extra_cdrom_ks.default_install.aio_threads.s390-virtio: STARTED
 (1/5) Host_RHEL.m8.u7.product_rhel.nographic.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.8.7.0.s390x.io-github-autotest-qemu.unattended_install.cdrom.extra_cdrom_ks.default_install.aio_threads.s390-virtio: PASS (620.88 s)
 (2/5) Host_RHEL.m8.u7.product_rhel.nographic.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.8.7.0.s390x.io-github-autotest-qemu.check_block_size.4096_4096.base.s390-virtio: STARTED
 (2/5) Host_RHEL.m8.u7.product_rhel.nographic.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.8.7.0.s390x.io-github-autotest-qemu.check_block_size.4096_4096.base.s390-virtio: PASS (25.54 s)
 (3/5) Host_RHEL.m8.u7.product_rhel.nographic.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.8.7.0.s390x.io-github-autotest-qemu.check_block_size.4096_512.extra_cdrom_ks.s390-virtio: STARTED
 (3/5) Host_RHEL.m8.u7.product_rhel.nographic.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.8.7.0.s390x.io-github-autotest-qemu.check_block_size.4096_512.extra_cdrom_ks.s390-virtio: PASS (647.89 s)
 (4/5) Host_RHEL.m8.u7.product_rhel.nographic.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.8.7.0.s390x.io-github-autotest-qemu.check_block_size.512_512.extra_cdrom_ks.s390-virtio: STARTED
 (4/5) Host_RHEL.m8.u7.product_rhel.nographic.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.8.7.0.s390x.io-github-autotest-qemu.check_block_size.512_512.extra_cdrom_ks.s390-virtio: PASS (644.79 s)
 (5/5) Host_RHEL.m8.u7.product_rhel.nographic.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.8.7.0.s390x.io-github-autotest-qemu.check_block_size.4096_4096_cluster_install.extra_cdrom_ks.s390-virtio: STARTED
 (5/5) Host_RHEL.m8.u7.product_rhel.nographic.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.8.7.0.s390x.io-github-autotest-qemu.check_block_size.4096_4096_cluster_install.extra_cdrom_ks.s390-virtio: PASS (656.66 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-18T05.23-b46d562/results.html
JOB TIME   : 2603.17 s

qemu version: qemu-kvm-6.2.0-19.module+el8.7.0+16358+eef3c6a2.s390x

As the test result, set this bz to verified
Comment 11 errata-xmlrpc 2022-11-08 09:20:55 UTC 
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 (Low: virt:rhel and virt-devel:rhel 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:7472
Note You need to log in before you can comment on or make changes to this bug.