On 01/30/2013 05:06 AM, Robert Knight wrote:
> the "reipl" step blocks other steps including setting up the network in
> the installed image, see
>
https://bugzilla.redhat.com/show_bug.cgi?id=858996
> IIRC the workaround is to copy the ifcfg-ctc0 file from /tmp
> to /mnt/sysimage/etc/sysconfig/network-scripts and also setting the
> root's password is needed after "chroot /mnt/sysimage"
Will try it. Do some s390-utils, aside from the obviously VM only
ones, only work on z/VM? I've only read one presentation on them and
didn't note that if it is the case. anaconda knows or at least
something knows if this is virtual -- I see it issue DIAG to check.
Hmmm. Maybe that's checking for IUCV instead.
Report in a couple of hours when I get back to that point.
OK. That was
refreshing. More like a couple of days. At the time that
I wrote the above, I thought I knew how to modify anaconda to chase
this, but had to learn that I did not.
I'm still stuck at the install finishes but produces an un-IPLable disk
image. I see in the bug quoted above (and the repair in that bug's
referenced bug) that this has been trouble.
I can hack out the crash in the iutil.py code that blows up anaconda,
but the chreipl is not working. It looks from the logs like it thinks
it has installed the "boot loader", although the disk still won't boot.