From here everything has to be done by hand: After logging in by SSH, you can start yast. Now yast should get the autoinst.xml from the selected source in parmfile, but yast doesn't. The is no action over the network to get this file, verified by ethereal. There are no Firewall problems because of using private network and already working FTP download. Before starting yast, you can also connect and get
Hello ! We still have some problems with autoinstallation on our s/390(x)-machines on LPAR: We already have: - start up the machine with the first ramdisk and a modified parmfile. The parmfile contains information like this: ramdisk_size=65536 root=/dev/ram1 ro init=/linuxrc TERM=dumb AUTOINSTALL=yes INST_PASSWORD=xxx IP_HOST=(ownHOSTNAME) IP_ADDR=(ownIP) IP_MTU=1492 IP_INTERFACE=qeth IP_NETMASK=255.255.0.0 IP_GATEWAY=xxx IP_BROADCAST=xxx READ_DEVNO=f618 WRITE_DEVNO=f619 DATA_DEVNO=f61a PORTNAME=OSAPORT INST_INFO=ftp FTPUSER=xxx FTPPASSWORD=xxx INST_IP_ADDR=(IPftpSERVER) INST_SCREEN=SSH IP_DEV=eth0 INST_IP_DIR=SLES-9-s390/SUSE-SLES-Version-9/CD1 autoyast=http://(whereTHEautoinstfileIS)/autoinst.xml install=http://xxx/SUSE-SLES-Version-9/CD1 During the first boot with this parmfile, The machine gets some files by FTP (content, /boot/root, media.l/info.txt, part.info (which is not available), control.xml, driverupdate (which is also not available), products, media, packages, packages.en, packages.en_us, Base-System.sel .....) Now the machine boots with this ramdisk and starts up with an SSH-Server (depending on selection in parmfile) and is reachable in the network. All this worked automatically. the autoinst.xml manually. Yast now askes for alle parameters like DASDs, Package selection, language, partiton... Under installation as VM-guest it works with the same parmfile and the machine gets the autoinst.xml. We already tried a http-source for the autoinst.xml-file, but without success. We cannot use a cdrom or floopy to boot the lpar because we are working via HMC on the machine and only the service element has a floopy or cdrom. We use installservers. Anybody has an idea / hint on how to make the machine getting the autoinst.xml ? Thank you in advance ! Stefan Mit freundlichen Grüßen / Best regards Stefan Leippert Praktikant eServer Software System Evaluation and Test