On 4/25/19 10:31 AM, Colin Walters wrote:
>
>
> On Wed, Apr 24, 2019, at 9:20 AM, Dan Horák wrote:
>>
>> you should be able to use the image-base kickstart outside coreos to
>> install a regular VM and look what's going on, capture logs, etc.
>
> That shouldn't be necessary, see
>
https://github.com/coreos/coreos-assembler/pull/491
>
> (You don't need that PR, the log extraction functionality works today, it just
tells you where to find it)
>
> Also on this topic, what bootloader is s390x using nowadays? So far the
Fedora+ostree integration is mostly tested with grub2; see also
https://github.com/ostreedev/ostree/issues/1801 though.
>
> It looks like whatever is going wrong is in the s390x bootloader code in Anaconda.
s390x uses zipl as usual.
Yes Anaconda is not recognizing GPT-ed SCSI disks as allowed booting
media even though zipl supports both MBR and GPT SCSI disks.
https://github.com/rhinstaller/anaconda/blob/master/pyanaconda/platform.p... _______________________________________________
CoreOS mailing list -- coreos(a)lists.fedoraproject.org
To unsubscribe send an email to coreos-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://getfedora.org/code-of-conduct.html
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/coreos@lists.fedoraproject.org