s390x: put coreos-installer into initramfs #294
Conversation
Signed-off-by: Nikita Dubrovskii <nikita@linux.ibm.com>
|
This PR depends on: coreos/coreos-installer#153 |
|
|
||
| `#cp ipl c` | ||
|
|
||
| During `cosa buildextend-live` ramdisk gets generated, but contains no coreos-installer, |
There was a problem hiding this comment.
Hmm, can you expand on this? The ramdisk contains the root squashfs into which we pivot, right? That rootfs is a regular FCOS system which should have coreos-installer in it.
There was a problem hiding this comment.
After checking (unpacking) fedora-coreos-*.dev.*-live-initramfs.s390x.img i figured out, that it doesn't contain coreos-installer service. Maybe on x86 it's there, haven't checked yet. It means, that on IBM Z we are not able to proceed with CoreOS without installation during 1st boot.
There was a problem hiding this comment.
After checking (unpacking)
fedora-coreos-*.dev.*-live-initramfs.s390x.imgi figured out, that it doesn't contain coreos-installer service.
The initramfs is a concatenation of multiple CPIO archives. One of those contains the root squashfs.
Are you able to boot the live image on s390x? Does it not boot all the way to the real root?
There was a problem hiding this comment.
After unpacking the initramfs you need to look for a file at /root.squashfs. That squashfs has the real root filesystem in it that contains coreos-installer. As @jlebon said, the suggestion here is to boot a live cd all the way up and then you'll find coreos-installer easily.
There was a problem hiding this comment.
One thing to watch for if you're doing cpio -id is that it doesn't understand concatenated CPIO archives. That's why dracut has skipcpio to skip over the first microcode one. But even then, that one just seems to print everything after the first CPIO, regardless if there's just one or multiple ones left.
There was a problem hiding this comment.
Are you able to boot the live image on s390x?
on zVM it's possible with live-initramfs, not live-iso
There was a problem hiding this comment.
with unpatched ramdisk ostree-prepare-root.service fails during boot.
I'll continue investigation
There was a problem hiding this comment.
on zVM it's possible with live-initramfs, not live-iso
Gotcha. How are you booting with the live initramfs directly, via live PXE or some s390x-specific thing?
Either way, if it boot fine all the way to the real root, you should have access to coreos-installer there, right?
There was a problem hiding this comment.
It's s390x specific: on zVM kernel, ramdisk and boot.prm should be directly copied into reader queue, and then ipl'ed (booted).
Here some more details about it:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/installation_guide/sect-installation-overview-s390
I wasn't aware about /root.squashfs exists within ramdisk, so decided to add coreos-installer. Currently CoreOS failes during boot - mount issues. I'll try fixinig it today.
There was a problem hiding this comment.
so, it was my bad. the script i've wrote and used to boot CoreOS on zVM had a bug preventing ostree-prepare-root to parse cmdline. after fixing it root.squashfs mounts without issues
Signed-off-by: Nikita Dubrovskii nikita@linux.ibm.com