8000 GitHub - ashcrow/hercules-f30: some very simple but specific helper scripts and configurations to install F30 for s390x inside the hercules emulator
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

some very simple but specific helper scripts and configurations to install F30 for s390x inside the hercules emulator

Notifications You must be signed in to change notification settings

ashcrow/hercules-f30

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

10 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Intro

These are some very simple but specific helper scripts and configurations to install F30 for s390x inside the hercules emulator.

How simple? The instructions below should give you a running F30 s390x instance with 6 commands.

I am by no means expert in mainframe or hecules. Corrections and improvements welcome.

This was inspired by Daniel Horak's earlier work with F20 which he documented here:

https://sharkcz.livejournal.com/12268.html

More recent Fedora releases make use of newer s390x features that are not properly emulated by the 3.x series of hercules.

As a result, to use these scripts and instructions, you'll need to install the in-progress 4.x rpm-ification from here:

https://copr.fedorainfracloud.org/coprs/imcleod/hercules4/

Instructions

Do several preparation steps:

make all

This downloads the install kernel and ramdisk, appends the kickstart file to the ramdisk, creates the hercules DASD image file and sets up a NAT rule and forwarding to allow the virtual QETH device inside of the hercules guest to route to the outside world. Look in the Makefiles for details.

Now start hercules with our config. Note that for this setup, you must be root, as hercules will create a tap networking device as it runs:

sudo hercules -f ./fedora.cnf

Within the hercules console, start the install. In the mainframe world this is known as an Initial Program Load. The details of the boot environment are described in the "ks.ins" file:

herc =====> ipl ks.ins

Now wait and watch for 2 to 3 hours. You'll see occasional console output from Anaconda, combined with status output from the emulator itself.

If you are bored, press [esc] to toggle back and forth between a more device/CPU centric view of the emulator status, and the actual console/command-line.

If you end up in an emergency shell, you can interact with linux by prepending a "!" to console commands. e.g.:

herc =====> !ps xa

If all goes well, at the completion of install, Anaconda will shutdown the guest and the emulator will halt. For me it looks like this

  7220.162678! anaconda 1624!: .                                                                                                                                                                   
  7220.167409! anaconda 1624!: Generating initramfs                                                                                                                                                
  7279.225390! anaconda 1624!: ..                                                                                                                                                                  
  7279.228380! anaconda 1624!: Running post-installation scripts                                                                                                                                   
  7283.780539! anaconda 1624!: .                                                                                                
5848
                                                                   
  7283.783219! anaconda 1624!: Storing configuration files and kickstarts                                                                                                                          
  7284.148649! anaconda 1624!: ..                                                                                                                                                                  
HHC00006I SCLP console interface inactive                                                                                                                                                          
HHC00814I Processor CP00: SIGP Stop                             (05) CP01, PARM 0000000000000000: CC 0                                                                                             
HHC00814I Processor CP00: SIGP Stop                             (05) CP00, PARM 0000000000000000: CC 0                                                                                             
herc =====>

At this point, you can quit and then restart the emulator. e.g.:

herc =====> quit

and then:

# sudo hercules -f ./fedora.cnf

At this point you can IPL from the disk device we have just installed to, rather than into the install environment defined by ks.ins file. In our configuration, this is device 130 and the command to IPL from it is the following:

herc =====> ipl 130

After a brief boot up, you should be able to "ssh root@192.168.200.3". The root password is "fedora"

About

some very simple but specific helper scripts and configurations to install F30 for s390x inside the hercules emulator

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Makefile 51.6%
  • Python 31.0%
  • TeX 9.3%
  • Shell 8.1%
0