Solaris 10 #GP #173
Comments
Thanks. This looks similar to #172, except that the guest exception is #GP (General Protection Fault). But still, the first step is to disassemble the guest code and locate the faulting instruction ( |
Ive extracted the offending instruction. Its related to MSR as in #172
I don't know which way to read the stack dump but there is a 0xc0000080 (leftmost col, 2nd from the top) - looks like MSR number. I'll set up a breakpoint at 0x0100f490 and peek at the stack. |
It looks like %ecx is IA32_EFER and %eip on rdmsr so the same issue. Does it boot for you with this patch: #172 (comment) |
Very good! So we have the bug reproduced on two different systems. Ill test the patch.
|
My fault for having old haxm, after updating to HEAD and applying @krytarowski 's patch it boots up to a later stage. The kernel crashes though as this turned out to be a 64-bit os, the 32 bit bootloader works for sure. |
Please test with qemu-system-x86_64 |
#172 (comment) Please test the newest HAXM with this patch applied... and use qemu-system-x86_64. |
Any news about Sol 10 ? BTW, which particular Solaris release do you use for testing? |
Solaris needs CR8 support. |
Describe the Bug
This bug makes it unable to boot solaris 10 in QEMU/HAXM on NetBSD/amd64
Summary: Solaris 10 install CD bootloader fails to boot, triggers a GPF (code 0)
Host Environment
Guest Environment
To Reproduce
1. Boot in qemu with default options, a little more RAM and HAX enabled
qemu-system-i386 -accel hax -cdrom [solaris install CD iso] -m 4G
Expected Behavior
Solaris boots as if it was a physical machine.
Reproducibility
Always
Diagnostic Information
Host crash dump: n/a
HAXM log: No useful information (Only the start version info,
HAX_LOWMEM_4G ignored
andhax_teardown_vm
, we've already recompiled it with noisiest loglevel)Screenshots: Boot panic, solaris prints a very verbose panic with a stack dump
Additional context
This install medium uses GNU GRUB for boot option selection. GRUB works fine, then there is a sequence of dots (indicating loading of some sort), then panic (screenshot below)
Host and env same as in #172
The text was updated successfully, but these errors were encountered: