Fedora Images

[Phil Roberts]

> Phil P wrote:
> So I pulled the latest Source code snapshot - 7747 compiled it - and tried

to boot the install images - 
it just loops never getting past - the Linux message - "Trying to unpack
rootfs image as initramfs..."
> Went back to 7702 and it came up to the network configuration fine.

Compiled 7702 and latest 7747 today and both give similar result of 23 minutes or so and 33 Billion instruction count before unpack is finished.

14:15:10 Ö 15.455934! Trying to unpack rootfs image as initramfs...
14:38:09 Ö 704.650414! Freeing initrd memory: 77722k freed
> Are you running hercules under Windows or Linux?

Linux.
> It also depends if you are using CTCs - it would be the IP address at the

other end, if you are using LCS devices it should be your router or gateway
to the internet.   LCS Devices are simpler to use on Linux you do not need
to add routes just a change to sysctl.conf to
net.ipv4.conf.default.proxy_arp = 1

Keeping the configuration which worked for FC11 which used CTC.

If I don't run the hercules.init script before hercules startup the 2nd CTC fails to initalize due to tun (?) not available.

My host only has 1Gb RAM and 512Mb swap partition.  I added a 2Gb swap file and with SVN 7747 don't seem to get segmentation faults anymore up IPL of C.  Down in the interactive install it askes for 'partner to partner' and then states it is trying gateway and later DNS IP address.  I haven't gotten the right info yet as it never cannot ping the DNS Server.

A little bit of my log:

14:38:36 Scanning for available network devices...
14:38:38 Autodetection found 0 devices.
14:38:40 Note: There is a device blacklist active× (Clearing might take long)
14:38:40 c) clear blacklist, m) manual config, r) rescan, s) shell:
15:13:19 HHC00160I SCP command: 'c'
15:13:19 c
15:13:19 Clearing device blacklist...
15:13:26 /init: line 491: nettable: bad array subscript
15:13:26 
15:13:27 
15:13:27 Network type (qeth, lcs, ctc, ? for help). Default is qeth:
15:13:29 INFO kernel:Ö 1764.690769! lcs: Loading LCS driver
15:13:31 INFO kernel:Ö 1765.561956! ctcm: CTCM driver initialized
15:13:34 HHC00160I SCP command: 'ctc'
15:13:34 ctc
15:13:34 
15:13:34 Read,write channel (e.g. 0.0.0600,0.0.0601 or ? for help)
15:13:46 HHC00160I SCP command: '0.0.0600,0.0.0601'
15:13:46 0.0.0600,0.0.0601
15:13:48 Detected: channel-to-channel adapter (CTC/A)
15:13:48 
15:13:48 CTC protocol (0, 1, 3, or ? for help). Default is 0:
15:13:54 HHC00160I SCP command: '0'
15:13:54 0
15:13:54 Activating network device...
15:13:55 INFO kernel:Ö 1777.926703! net ctc0: setup OK : r/w = ch-0.0.0600/ch-0.0.0601, p
15:13:55 rotocol : 0
15:13:58 
15:13:58 Hostname of your new Linux guest (FQDN e.g. s390.redhat.com or ? for help):
15:13:58 INFO kernel:Ö 1779.297699! net ctc0: Connected with remote side
15:14:19 HHC00160I SCP command: 's390.halfmeg.org'
15:14:19 s390.halfmeg.org
15:14:20 
15:14:20 IPv4 address (e.g. 10.0.0.2 or ? for help)
15:15:05 HHC00160I SCP command: '192.168.200.3'
15:15:06 192.168.200.3
15:15:06 
15:15:06 IPv4 address of your point-to-point partner or ? for help:
15:15:14 HHC00160I SCP command: '?'
15:15:14 ?
15:15:14 Help text for point-to-point partner:
15:15:14 IPv4 address of your CTC or ESCON point-to-point partner.
15:15:14 
15:15:14 IPv4 address of your point-to-point partner or ? for help:
15:15:46 HHC00160I SCP command: '192.168.200.4'
15:15:46 192.168.200.4
15:15:46 Trying to reach gateway 192.168.200.4...
15:15:53 
15:15:53 IPv4 addresses of DNS servers (separated by colons ':' or ? for help):
15:16:01 HHC00160I SCP command: '?'
15:16:01 ?
15:16:01 Help text for DNS servers:
15:16:01 Enter IPv4 addresses of DNS servers separated by colons ':'
15:16:01 Default are no DNS servers at all.
15:16:01 However, you might encounter problems without a nameserver,
15:16:01 especially with FTP installs.
15:16:01 An example with 2 servers would be: 10.0.0.250:10.1.1.1
15:16:01 
15:16:01 IPv4 addresses of DNS servers (separated by colons ':' or ? for help):
15:18:12 HHC00160I SCP command: '98.66.242.91'
15:18:12 98.66.242.91
15:18:13 Trying to reach DNS servers...
15:19:14 Could not ping DNS server: 98.66.242.91

I tried 192.168.200.1 for point-to-point ( gateway ? ) which it didn't balk at but still couldn't get past the DNS address ( thinik I tried 192.168.1.254 for DNS also ).

You mentioned LCS is simpler so may attempt to switch to that.

Ignoring the above problems with DNS and perhaps the gateway addresses I continued the install and got to this point:

15:28:19 Starting sshd to allow login over the network.
15:28:19 HHC00801I Processor CP00: 'Operation exception' code 0001 ilc 4
15:28:19 HHC02267I PSW=0705F00180000000 000003FFFCF524A0 INST=B93E0002 KIMD 0,2 compute_intermediate_message_digest
15:28:19 HHC02267I V:0000000000000000: Translation exception 003B
15:28:19 HHC02267I V:000002AAD057EA60:K:06=67452301 EFCDAB89 98BADCFE 10325476 . Á.ï.¨iqª.ú...ä
15:28:19 /init: line 178: 364 Illegal instruction /usr/sbin/sshd -f /etc/ssh/sshd_c
15:28:19 onfig.anaconda
15:28:19 
15:28:19 Connect now to 192.168.200.3 and log in as user 'install' to start the installat
15:28:19 ion.
15:28:19 E.g. using: ssh -x install@192.168.200.3
15:28:19 For VNC or text mode, disable X11 forwarding (recommended) with 'ssh -x'.
15:28:19 For X11, enable X11 forwarding with 'ssh -X'.
15:28:19 
15:28:19 You may log in as the root user to start an interactive shell.
15:29:14 HHC00160I SCP command: 'login root'
15:29:14 login root
15:29:14 sh: cannot set terminal process group (-1): Inappropriate ioctl for device
15:29:14 sh: no job control in this shell
15:29:15 sh-4.2# 
15:29:26 HHC00160I SCP command: 'ls'
15:29:26 ls
15:29:26 bin etc init lib64 proc run selinux tmp var
15:29:26 dev firmware lib modules root sbin sys usr
15:29:27 sh-4.2# 
15:29:40 HHC00160I SCP command: 'shutdown -h now'b

A ssh from another terminal window on the same host pc timed out connecting.  Logging in via the hercules console it does get to where one can do a 'ls' and get response back.

In a couple of places I noticed hercules get an 'operation exception' and the above snippet of the log shows one.  Is this type error expected ?

Phil R

[Philip Pinto]

Phil R Wrote,
> Compiled 7702 and latest 7747 today and both give similar result of 23

minutes or so and 33 Billion instruction count before unpack is finished.

I know on here 7747 I did get around 29 Billion before I killed it but not
much higher – the thing that threw me was the Registers and PSW were not
changing on 7747 though the instruction count was going up like crazy – I
might give it and try waiting a little longer but 7702 where I did observe
Regs and PSW changing during the long wait period -  it was about 15-20 min
here too.
> > snip
> Keeping the configuration which worked for FC11 which used CTC.

That's ok I have installed with CTCs too - I have some FC15 that use CTCs as
well

Couple things to keep in Mind - be cautions of firewall on Linux Intel box -
if it is on you may want to turn it off for testing

Looks like the  CTC is working and it can ping the other side - so your
setup is good for the CTC

15:15:46 HHC00160I SCP command: '192.168.200.4'
15:15:46 192.168.200.4
15:15:46 Trying to reach gateway 192.168.200.4...
15:15:53 IPv4 addresses of DNS servers (separated by colons ':' or ? for
help):

If it could not ping the gateway it would re-prompt to re-enter

Do you have any routes setup?

Here is a sample of ctc that should work 
0600.2 CTCI /dev/net/tun 1500 192.168.200.3 192.168.200.4 255.255.255.0

You will need a hercules.rc on the Intel Linux 
pause 4
sh route add 192.168.200.3 gw 192.168.200.4 tun0

I am assuming the 192.168.200.4 is the IP of the Intel box running hercules
here and 192.168.200.3 is the FC15 guest of hercules

Also check that the /etc/sysctl.conf on the intel box - I am assuming a RHEL
variant here  - I have these set in mine - the forward is the only thing you
need on for CTCs but the others make LCS devices work.  If you can I would
set them all as below.

# Controls IP packet forwarding
net.ipv4.ip_forward = 1
net.ipv4.conf.default.proxy_arp = 1
# Controls source route verification
net.ipv4.conf.default.rp_filter = 1
> My host only has 1Gb RAM and 512Mb swap partition.  I added a 2Gb swap file

and with SVN 7747 don't seem to get segmentation faults anymore up IPL of
C.  Down in the interactive install it asks for >'partner to partner' and
then states it is trying gateway and later DNS IP address.  I haven't gotten
the right info yet as it never cannot ping the DNS Server.

The memory is a little tight - what is the memory size set to in the
hercules.cnf for FC15?  You might need to 2GB of Central to get FC15 to
install might be the problem with sshd illegal instruction in the later part
of the install log
> A little bit of my log:

Everything looks good right up to the DNS but FC15 can't ping it - I assume
that 98.66.262.91 is a router or a DNS Servers you are running somewhere.  I
run my own DNS servers here under Intel Linux so I define DNS names there
for all Hercules Linux Guests - Because as you get further into the install
a real DNS entry for the Linux box is essential VNC and x-windows to work.
Also I believe FC15 will also do an nslookup  on 's390.halfmeg.org' so if
that is not really defined FC15 may reprompt for DNS and or Hostname even if
it can ping it.

15:15:53 IPv4 addresses of DNS servers (separated by colons ':' or ? for
help):
15:16:01 HHC00160I SCP command: '?'
15:16:01 ?
15:16:01 Help text for DNS servers:
15:16:01 Enter IPv4 addresses of DNS servers separated by colons ':'
15:16:01 Default are no DNS servers at all.
15:16:01 However, you might encounter problems without a nameserver,
15:16:01 especially with FTP installs.
15:16:01 An example with 2 servers would be: 10.0.0.250:10.1.1.1
15:16:01 
15:16:01 IPv4 addresses of DNS servers (separated by colons ':' or ? for
help):
15:18:12 HHC00160I SCP command: '98.66.242.91'
15:18:12 98.66.242.91
15:18:13 Trying to reach DNS servers...
15:19:14 Could not ping DNS server: 98.66.242.91
> I tried 192.168.200.1 for point-to-point ( gateway ? ) which it didn't

balk at but still couldn't get past the DNS address ( thinik I tried
192.168.1.254 for DNS also ).
> > You mentioned LCS is simpler so may attempt to switch to that.

You won't need the routes and the setup process is essentially the same from
FC15 under hercules  as the CTC- you will need to check the settings in
sysctl.conf as mentioned earlier

The network config at this point would be like any other PC on your network
- gateway / dns etc would be same IPs as what you use to access the internet
from any pc on the same network.
> > Ignoring the above problems with DNS and perhaps the gateway addresses I

continued the install and got to this point:

Too late ;-)  - besides you really can't install Linux without the network
working properly

15:28:19 Starting sshd to allow login over the network.
15:28:19 HHC00801I Processor CP00: 'Operation exception' code 0001 ilc 4
15:28:19 HHC02267I PSW=0705F00180000000 000003FFFCF524A0 INST=B93E0002 KIMD
0,2 compute_intermediate_message_digest
15:28:19 HHC02267I V:0000000000000000: Translation exception 003B
15:28:19 HHC02267I V:000002AAD057EA60:K:06=67452301 EFCDAB89 98BADCFE
10325476 . Á.ï.¨iqª.ú...ä
15:28:19 /init: line 178: 364 Illegal instruction /usr/sbin/sshd -f
/etc/ssh/sshd_c
15:28:19 onfig.anaconda

This Line looks bad maybe larger central storage from hercules.conf file -
maybe?  If SSHD is really dying here - it's game over for the install.
 /init: line 178: 364 Illegal instruction /usr/sbin/sshd -f /etc/ssh/sshd_c
> > A ssh from another terminal window on the same host pc timed out

connecting.

Did you try pinging from that terminal - ping 192.168.200.3?  If SSHD really
died - you would still be able to ping and that would mean the networking
between the Intel and FC15 systems.
> > Logging in via the hercules console it does get to where one can do a

'ls' and get response back.
Yes but not much you can do from there -  check /dev /etc etc... there are
some cool dasd commands
> > In a couple of places I noticed hercules get an 'operation exception' and

the above snippet of the log shows one.  Is this type error expected ?

I see those too - usually not a real problem  of course everything looks bad
when things don't work

Phil P