Re: Re: CPU support for RHEL 7.x

"Dan Horák [email protected] [hercules-390]" <[email protected]>
Newsgroups gmane.comp.emulators.hercules390.general
Message-ID <[email protected]>
On 30 May 2019 22:38:52 +0000
"[email protected] [hercules-390]" <[email protected]> wrote:

> Hi Filipe, Did you manage to get RHEL 7.x installed under Herc?
>  I've successfully installed Gentoo under Herc, and RHEL 6.10, but
> I'm unable to get the installer system running correctly for RHEL
> 7.x. 
> 
>  I'm ipling from my 000C device, which is as follows:
>  
> 
>  000C    3505    E:/linux_RHEL70/images/kernel.img
> E:/linux_RHEL70/images/generic.prm E:/linux_RHEL70/images/initrd.img
> autopad eof
> 
>  
> 
>  All I have in my generic.prm is:
>    ro ramdisk_size=40000 cio_ignore=all,!condev
>  
> 
>  
> 
>  
> 
>  Linux starts up, and after a few minutes of startup messages and
> burning CPU, I get this: 

this happens when the installer can't get its stage2, which is usually
downloaded from network. AFAIK the RHEL docs have documented what
parameters must be set in generic.prm. RHEL7 shouldn't be different
from RHEL6 in this regard, except using enccw0.0.abcd for the network
interface name.


		Dan

>  2019/05/30 23:25:08.314 00000570   32m  OK   0m! Mounted
> Configuration File System. 2019/05/30 23:25:08.314 00000570   32m
> OK   0m! Reached target System Initialization. 2019/05/30
> 23:29:04.994 00000570 Warning: /dev/root does not exist 2019/05/30
> 23:29:04.994 00000570 2019/05/30 23:29:04.994 00000570 Generating
> "/run/initramfs/rdsosreport.txt" 2019/05/30 23:29:05.534 00000570 
>  2019/05/30 23:29:05.534 00000570 
>  2019/05/30 23:29:05.534 00000570 Entering emergency mode. Exit the
> shell to continue. 2019/05/30 23:29:05.534 00000570 Type "journalctl"
> to view system logs. 2019/05/30 23:29:05.534 00000570 You might want
> to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot
> 2019/05/30 23:29:05.534 00000570 after mounting them and attach it to
> a bug report. 2019/05/30 23:29:05.534 00000570 2019/05/30
> 23:29:05.534 00000570 2019/05/30 23:29:05.634 00000570 dracut:/#
>  
> 
>  I don't really see any errors prior to that.  The journalctl and
> rdsosreport.txt files show the following: 
> 
>   86.580293! localhost systemd 1!: Starting Paths.
>   86.590591! localhost systemd 1!: Reached target Paths.
>   86.596205! localhost systemd 1!: Starting Basic System.
>   86.602890! localhost systemd 1!: Reached target Basic System.
>   86.892235! localhost systemd 1!: Reloading.
>  322.313265! localhost dracut-initqueue 580!: Warning: Could not boot.
>  322.339111! localhost dracut-initqueue 580!: Warning: /dev/root does
> not exist 322.424762! localhost systemd 1!: Started Setup Virtual
> Console. 322.430975! localhost systemd 1!: Starting Dracut Emergency
> Shell... 
> 
> 
>  So a few mins after the "Reloading" begins, it suddenly has the
> issue with /dev/root. 
> 
>  Anyone got any ideas what I'm doing wrong?
>  
> 
> 
>  
> 
> 
>  
> 
>  
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.