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 1746399 - [s390x] Composer, qcow2 image: No zIPL section in IPL2 record.
Summary: [s390x] Composer, qcow2 image: No zIPL section in IPL2 record.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: anaconda
Version: 8.1
Hardware: s390x
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.2
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 1673744 1746404
TreeView+ depends on / blocked
 
Reported: 2019-08-28 11:20 UTC by Alexander Todorov
Modified: 2021-01-29 07:44 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-29 07:43:47 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)
program.log (39.01 KB, text/plain)
2019-09-03 12:51 UTC, Alexander Todorov 		no flags Details
anaconda.log (27.77 KB, text/plain)
2019-09-03 12:52 UTC, Alexander Todorov 		no flags Details
lvm.log (231.24 KB, text/plain)
2019-09-03 12:52 UTC, Alexander Todorov 		no flags Details
packaging.log (247.17 KB, text/plain)
2019-09-03 12:52 UTC, Alexander Todorov 		no flags Details
storage.log (150.39 KB, text/plain)
2019-09-03 12:53 UTC, Alexander Todorov 		no flags Details
View All

Description Alexander Todorov 2019-08-28 11:20:07 UTC 
Description of problem:

I was able to build a qcow2 image with composer-cli on s390x but it fails to boot with qemu-kvm. What I see is:


:: [ 07:08:34 ] :: [  BEGIN   ] :: Running '/usr/libexec/qemu-kvm -m 2048 -boot c -hda 9870594b-6e1a-4d09-98f3-00dafc490f6b-disk.qcow2 -nographic                            -net user,id=nic0,hostfwd=tcp::2222-:22 -net nic &'
STDERR: qemu-kvm: warning: 'apqci' requires 'ap'.
STDERR: qemu-kvm: warning: 'apft' requires 'ap'.
STDOUT: LOADPARM=[        ]
STDOUT: Using virtio-blk.
STDOUT: Using guessed DASD geometry.
STDOUT: Using ECKD scheme (block size  4096), CDL
STDOUT: 
STDOUT: ! No zIPL section in IPL2 record. !


Version-Release number of selected component (if applicable):
lorax-composer-28.14.30-1.el8.s390x

How reproducible:
always

Steps to Reproduce:
1. composer-cli compose start example-http-server qcow2 on an s390x system
2.
3.
Comment 4 Brian Lane 2019-08-28 16:14:25 UTC 
Please attach the anaconda logs from the compose, I'm especially interested in program.log to see what the bootloader install looks like.
Comment 6 Cornelia Huck 2019-09-02 07:16:58 UTC 
Looking at

STDOUT: LOADPARM=[        ]
STDOUT: Using virtio-blk.
STDOUT: Using guessed DASD geometry.
STDOUT: Using ECKD scheme (block size  4096), CDL
STDOUT: 
STDOUT: ! No zIPL section in IPL2 record. !

this smells like a missing zipl invocation somewhere.

Is the code building the qcow2 image calling zipl after the kernel has been installed?
Comment 7 Thomas Huth 2019-09-02 10:04:30 UTC 
FWIW, I've reproduce the problem (with "composer-cli compose start example-atlas qcow2" as described in https://bugzilla.redhat.com/show_bug.cgi?id=1746404#c7 ) and had a closer look at the produced image. Indeed, zipl is missing here - there is no /etc/zipl.conf installed in the image. I had to add that file manually, adjust /boot/loader/entries/*.conf, re-create the initrd with dracut and run "zipl" manually. Then the image was finally bootable.
Comment 10 Alexander Todorov 2019-09-03 12:51:46 UTC 
Created attachment 1611128 [details]
program.log
Comment 11 Alexander Todorov 2019-09-03 12:52:09 UTC 
Created attachment 1611129 [details]
anaconda.log
Comment 12 Alexander Todorov 2019-09-03 12:52:48 UTC 
Created attachment 1611130 [details]
lvm.log
Comment 13 Alexander Todorov 2019-09-03 12:52:59 UTC 
Created attachment 1611131 [details]
packaging.log
Comment 14 Alexander Todorov 2019-09-03 12:53:09 UTC 
Created attachment 1611132 [details]
storage.log
Comment 17 Brian Lane 2019-09-03 16:42:01 UTC 
https://bugzilla.redhat.com/show_bug.cgi?id=1746424 is likely the root cause of this, it wasn't copying the config file.
Comment 19 Brian Lane 2019-11-06 20:40:02 UTC 
Looking at this again I realize that it is different from the live-iso case.

Comment 7 indicates that it is possible to get the image bootable with some manual intervention. These steps should be handled by Anaconda.

After some digging around I discovered that installing the bootload was disabled because of rhbz#1019502, ends up there is a check for s390 image installation in pyanaconda/bootloader/execution.py that has been in place since 2013.

If I disable the check in pyanaconda/bootloader/execution.py the qcow2 image is now bootable, but it isn't a working system.
Once it hits dracut it cannot find the root disk, and it looks like there are no disks attached at all.
Bootup is also very slow, even when passing --rng=/dev/urandom to virt-install, and once you get to the dracut shell there are almost no modules loaded.

I've been booting the disk.qcow2 with:
virt-install --debug --name f32 --memory 2048 --disk /var/lib/lorax/composer/results/UUID/disk.qcow2 --import --rng=/dev/urandom

I'm fairly sure these problems are all things that Anaconda needs to solve (at the least, re-enabling bootloader install to s390 disk images) so I'm moving this bug over there.
Comment 21 Alexander Todorov 2020-02-21 22:02:32 UTC 
I've tested with a current snapshot from February and the image gets build and boots. Fails with a dracut timeout but there is no error about zIPL anymore. Moving to VERIFIED.
Comment 24 Thomas Huth 2021-01-29 07:43:47 UTC 
(In reply to Alexander Todorov from comment #21)
> I've tested with a current snapshot from February and the image gets build
> and boots. Fails with a dracut timeout but there is no error about zIPL
> anymore. Moving to VERIFIED.

Looks like this bug is in VERIFIED since 11 months already - I guess it just has not been auto-closed because there was no errata in this case. Let's close it manually now.
Note You need to log in before you can comment on or make changes to this bug.