[opensuse-autoinstall] How to debug a failed Autoyast install of a Factory-Xen DomU?
I use Autoyast to install Xen DomUs. Installing an OpenSuse 11.1 DomU, with autoyast= invoked in the DomU's .cfg, works just fine. Installing an OpenSuse Factory DomU, the install launches, and proceeds to some random , late-stage package install (@ ~ 80-90% complete, in each of 4 attempts), then just hangs -- taking the Dom0 with it. All connections are dropped, and a system reboot is required. I'm trying to debug the process. Launching the DomU with, extra = 'linuxrc.debug=1 linuxrc.log=/dev/console linemode=1 textmode=1 xencons=tty vnc=0 edd=off autoyast=nfs://192.168.1.200/home/autoyast.xml install=http://download.opensuse.org/factory/repo/oss?device=eth0 netdevice=eth0 hostip=192.168.1.201/24 gateway=192.168.1.101 nameserver=192.168.1.106' isn't providing any log trace of what the problem might be. At least not that I've been able to see/find @ the xen console, or in any logs @ the Dom0. What/where additional logging can I turn on to track down the failure in the autoyast DomU process? Thanks. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
on Sunday 25 October 2009 PGNet Dev wrote:
Installing an OpenSuse Factory DomU, the install launches, and proceeds to some random , late-stage package install (@ ~ 80-90% complete, in each of 4 attempts), then just hangs -- taking the Dom0 with it. All connections are dropped, and a system reboot is required.
I'm trying to debug the process.
Launching the DomU with,
extra = 'linuxrc.debug=1 linuxrc.log=/dev/console linemode=1 textmode=1 xencons=tty vnc=0 edd=off autoyast=nfs://192.168.1.200/home/autoyast.xml install=http://download.opensuse.org/factory/repo/oss?device=eth0 netdevice=eth0 hostip=192.168.1.201/24 gateway=192.168.1.101 nameserver=192.168.1.106'
add y2confirm there too, then check if the partitioning looks correct when autoyast stops in the proposal screen
What/where additional logging can I turn on to track down the failure in the autoyast DomU process?
you have network, so "loghost=HOST" might help to get the logs from the machine before it freezes. The syslog on HOST has to accept logging from the network of course -- ciao, Uwe Gansert Uwe Gansert SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug listening to: "Alive" by Assemblage 23 -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Hi,
What/where additional logging can I turn on to track down the failure in the autoyast DomU process?
you have network, so "loghost=HOST" might help to get the logs from the machine before it freezes. The syslog on HOST has to accept logging from the network of course
Alternatively, there is YaST remote logging how-to: http://en.opensuse.org/YaST_Remote_Logging_in_Installation Use whichever is more simple hB. -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
participants (3)
-
Katarina Machalkova -
PGNet Dev -
Uwe Gansert