Dear all, I'm trying to setup an enviroment for installing z/VM guests (SLES9-SP2/3, 31bit) completely unattended. This is my parmfile: ramdisk_size=65536 root=/dev/ram1 ro init=/linuxrc dasd=150,151 TERM=dumb AUTOYAST=http://<IP>/autoinst.xml AUTOINSTALL=yes IP_INTERFACE=qeth IP_HOST=<hostname> IP_ADDR=x.x.x.x IP_NETMASK=x.x.x.x IP_BROADCAST=x.x.x.x IP_GATEWAY=x.x.x.x IP_DNS=x.x.x.x IP_SEARCH=x.x.x.x READ_DEVNO=7000 WRITE_DEVNO=7001 DATA_DEVNO=7002 PORTNAME=xxxxxx INST_INFO=ftp INST_IP_ADDR=x.x.x.x INST_IP_DIR=/SLES/sles9_s390_sp3 FTPUSER=<user> FTPPASSWORD=<pw> INST_SCREEN=VNC VNC_PASSWORD=<pw> IP_MTU=1492 INST_PASSWORD=<pw> The forceboot option in the autoyast control file is set to true, confirm is set to false. The installation itself is running unattended (even if I had some problem in the past with the environment setup and a bug in YaST), so the major part of the game is basically solved. But after disk formatting/partitioning and package installation I always have to "trigger" the second stage by IPLing the guest manually since the automated reboot doesn't take place. This is my output: [...] umount: /y2update: not mounted umount: /var/adm/mount: not mounted Feb 15 19:48:19 suse sshd¬322|: Received signal 15; terminating. You should be able to login via telnet/ssh now. To restart network setup, enter: netsetup To continue the installation, enter: ./inst_source bash: no job control in this shell SuSE Instsys boeid120:/ # [...] After a manual IPL the system is doing the second stage installation - and it looks like the system installation is done completely and correctly. What do I have to do to prevent re-IPLing the system manually? BTW: Is it possible to "re-direct" installation output to 3270 instead of VNC? Mit freundlichen Gruessen/Kind regards Kai Dusek