Bugzilla – Bug 200195
VM Client Installation Deadlock?
Last modified: 2006-10-02 20:19:30 UTC
I tried to add a client using the YaST "Virtual Machine Management (XEN)" module. I did a network installation into a file. At the end, the boot loader installation failed (something with address space error -- maybe this happened because I didn't install kernel-xenpae?). I continued nevertheless and in the xterm I now see: Skipped services in runlevel 3: acpid irq_balancer nfs Welcome to SUSE LINUX 10.1 (i586) - Kernel 2.6.16.13-4-xen (tty1). INIT: Id "2" respawning too fast: disabled for 5 minutes INIT: Id "3" respawning too fast: disabled for 5 minutes INIT: Id "4" respawning too fast: disabled for 5 minutes INIT: Id "5" respawning too fast: disabled for 5 minutes INIT: Id "6" respawning too fast: disabled for 5 minutes But what bugs me more is, that I cannot "Abort" the still open "Preparing Installation of Virtual Machine"--it insists on displaying "75%" since half an hour. I will now crash all open windows and attach log files.
Created attachment 96509 [details] xen install log
These issues have been fixed in SLES 10 and will not be backported to SL 10.1 as it would require installation media to be remastered.
(In reply to comment #2) > will not be backported to SL 10.1 as it would require installation media to > be remastered. The 10.1 installation media *will* be remastered (see bug 197784). Please consider to include the fix for this bug as well.
Jason, what is the problem that the media need remastering?
To fix the "respawning too fast" problem, an updated yast2-vm needs to be included on the installation source. The vm_finish.ycp file is used to clean up the system at some point during the install. If you are updated libzypp, you need a completely new yast2-vm anyway, because (as I understand it) the APIs have changed and yast2-vm had to change to match. To fix the boot loader installation error, an updated kernel-xen needs to be included on the installation source. (If you took the latest kernel-xen from SLES 10, rather than just this single patch, then an updated [matching] xen would also be required.) We're not sure where the fix for the last problem is; we do know that linuxrc crashes at the end of the installation and can cause the problem described. If a new linuxrc was required to fix this, that also need to be on the installation media.
This is fixed in SLES 10 and will be fixed in openSUSE 10.2. Other priorities will not allow the Xen team to go back and address this issue for openSUSE 10.1. 10.2 is just around the corner. Marking as won't fix.