https://bugzilla.novell.com/show_bug.cgi?id=347416 User gb2@c5i.net added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c23 --- Comment #23 from Glen Barney <gb2@c5i.net> 2008-04-04 22:14:13 MST --- No, the error came up after a normal install, under xen-pae, runlevel 5, freshly-created guest. Previously I was unable to do an install from CD - something wasn't being configured correctly by the vm-tools, I think. So I didn't even have a guest to work with. This time I *was* able to do an install... at least farther than before. I booted my physical machine under the xen-pae kernel, went to runlevel 5, logged in to KDE, chose to install a virtual machine, upgraded to root, set up the machine, and ran the install. The domU machine read the DVD in the dom0 machine drive, which DVD was the original download of the OpenSuSE 10.3 32-bit DVD master ISO image from opensuse.org, and went through the entire installation procedure up to and including the installation of packages. BUT, when the domU machine went to do the first reboot (preparatory to setting the root password and continuing with YaST install), the boot failed before domU even opened a console window. The popup message appeared to come from the vm-install tool, and was that "guest type xen-3.0-x86_32 not supported by Xen kernel, sorry" message (complete with the escaped newline showing :-). I haven't been able to work on it since, but I *assume* it's because there have been so many upgrades to 10.3's kernels and Xen packages since that first DVD, that the kernel loaded from the DVD is not being recognized by the significantly-upgraded kernel running on my dom0 host. (I have no idea, I'm just guessing.) My intent is to try to mount the domU filesystem from dom0, and manually copy in the kernels from dom0's boot area into the domU filesystem, and hope that lets the domU machine start and continue the installation procedure? If you have any thoughts, guidance or commentary on this, I'd love to hear it. I am most likely totally wrong. :-/ Nevertheless I did at least get this far in the installation, in that all packages from the source DVD did get applied to the domU filesystem without the entire physical machine halting, and the dom0 machine was still perfectly responsive after the process. It's just that the domU won't boot now because of this error message, so I'll have to attack that next. I understand that what you want me to do now is try to get this domU machine to boot, and run network load testing from within that machine. Fantastic! I will make that my next move. As soon as I can get the domU machine to finish the install. :-) In response to your last question, no, I just took the defaults on this test install. One disk (40GB), one virtual network card, etc. Too tired of that to customize each install. :-) I just want an install to succeed, then I'll go back and redo it the way I want it. Hope this helps and, again, if anyone has any thoughts or can point me to anything that will expedite my fight with this partially-installed domU, I would be most grateful! Thanks -Glen -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.