On Fri, Nov 08, 2002 at 11:09:02AM -0600, Nix, Robert P. wrote: > This has gone completely off track, and in no way resembles or answers > my original questions. We're running zVM 4.2, not 4.2. We're on a 9672, > not a z-series, we have a single OSA interface, shared with a zOS image, > and no option for adding hardware interfaces, and we don't have any > money budgeted for the trial, not even the $500 for the true trial from > SuSE. Answers that involve any of the things we don't have don't help.
Then I would suggest you haven't been reading very carefully. Point the First: You do not need any additional hardware or a newer release of VM. You can do guest LANs just fine. Point the Second: If you cannot get anything newer from SuSE, then you will have to build your own kernel. SuSE will not support this kernel, but since SuSE isn't supporting you *anyway*, it doesn't matter. When you get a support contract, then you can get a SuSE-supported kernel that will support HiperSockets. *VIRTUAL* HiperSockets. For which you *DO NOT NEED ANY MORE PHYSICAL HARDWARE THAN WHAT YOU ALREADY HAVE*. Here's how: go get the virgin 2.4.19 kernel sources from kernel.org. Go get the s390-may2002, s390-1-may2002, and timer-1-may2002 patches from IBM Developerworks, and apply them in that order. Also get the qeth driver from there. Build a kernel. Build your modules. Copy the qeth driver somewhere under your modules directory. Run depmod -a. Edit zipl.conf to boot from your new kernel, and run zipl. ReIPL your Linux image--into CMS, if you can. Add a guest LAN to VM. Add a VIRTUAL HiperSocket NIC to your Linux image. Couple B to A. IPL Linux on your guest. Screw around with /etc/chandev.conf until your new virtual OSA works. Clone this image. Change IP address and hostname for each clone. Couple it to the same LAN. You're all done. It didn't cost you a penny. You don't need to fool with a point-to-point routing structure. Adam
