Noel Milton Vega
2007-Dec-05 03:02 UTC
Failed boot of xVM on an AMD Turion 64 X2 TL-52 based laptop (with 4GB RAM) ...
Hello: I successfully installed Solaris10 nv77 x86 on my Compaq NX6325 laptop with the following specs: - Mobile AMD Turion 64 X2 TL-52 (dual core 64bit). - 4GB RAM. The installation destination was an external 120GB USB 2.0 drive. I was able to successfully boot into regular Solaris, but not into xVM Solaris. Meaning, after highlighting the xVM menu item and pressing enter, the screen turns black, as if about to book, then a quick burst of text pops up and disappears (so fast that you cannot see it), and then the screen goes blank again. And thats the end - I have to power cycle. Is there any way to debug this? Should nv77 work on this model (or later versions)? Is there a hardware compat list? I''m looking for an environment to practice on. Any relatively inexpensive platform suggestions welcome too, (even from Sun''s site) if you know it to work with Solaris Xen in it current state. Thanks in advance. Regards, Noel Milton Vega
Jürgen Keil
2007-Dec-05 11:01 UTC
Re: Failed boot of xVM on an AMD Turion 64 X2 TL-52 based laptop (with 4GB
> I was able to successfully boot into regular Solaris, but not into xVM > Solaris. Meaning, after highlighting the xVM menu item and pressing enter, > the screen turns black, as if about to book, then a quick burst of text > pops up and disappears (so fast that you cannot see it), and then the > screen goes blank again. And thats the end - I have to power cycle. > > Is there any way to debug this?Yes. Assuming this is a panic from the Solaris kernel: In the GRUB menu, edit the "Solaris xVM" boot entry, append options " -kv" at the end of the "module$ /platform/i86xpv/kernel/$ISADIR/unix /platform/i86xpv/kernel/$ISADIR/unix" line, and boot the modified xVM entry. Now the system should stop in the kernel debugger if we do get a kernel panic. Before it stops in the debugger, a panic message is printed, cpu registers are dumped and a stack backtrace is printed. Instead of using kernel options "-kv" you can also try "-kdv". In this case it stops in the debugger before starting the Solaris kernel. To start the kernel use the kmdb command "::cont" (or ":c") This message posted from opensolaris.org