Robert Knight píše v Út 29. 01. 2013 v 22:18 -0500:
On 1/29/2013 6:26 PM, Robert Knight wrote:
> That just a straight-up defect in the anaconda module iutil.py. There
> is no "anaconda" included. There are other places where there is
> "storage.disks" in the code, so I'm guessing (and will check some time
> tonight) that removing the "anaconda." prefix will make that failure
> go away.
strange is that it doesn't affect real iron installation ... although
the can be difference between LPAR (that's what Hercules emulates) and
z/VM guest.
>>
>>> wherein it had tried a "chreipl" and it had failed. I don't
believe
>>> there's more to do at this point. lsreipl shows the expected device
>>> already set up. There are two more processes with /mnt/sysimage, one
>>> being anaconda and the other bash.
>>>
>>> I guess I'll try hacking the iutil.py file before things start...
>>
> The bad news is that when this is fixed, we're going to see "Unable to
> set reIPL device to..." followed by this: "After shutdown, please
> perform a manual IPL from ... to continue installation.", so that's
> not what's keeping it from booting.
Removing "anaconda." did allow the code to run, but
> 02:08:18,285 INFO program: Preparing boot device: dasda.
> 02:08:18,296 INFO program: Done.
> 02:08:18,341 INFO program: Running... chreipl node /dev/dasda
> 02:08:18,780 ERR program: chreipl: Could not open "reipl/ccw/loadparm"
> (Permission denied)
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"
Dan