Re: Testing status of fully virtualized guests (Intel VT) on 64bit XEN unstable

[Ed Smith <esmith@virtualiron.com>]

Nakajima, Jun wrote:
> Ed Smith wrote:
>> * NEW: "__hvm_bug at vmx.c:2286" booting 32bit SMP guest kernel on
>>    64bit Hypervisor (see boot.7)
> 
> I need clarification. Are you seeing the following message at the time
Sorry my notes were misleading.  It was the domain that crashed as you
suggested.  The guest booted up to the point of

"Uncompressing Linux... Ok, booting the kernel"

and the the domain crashed with the __hvm_bug at vmx.c:2286.

> of "Then XEN crashed"? __hvm_bug is supposed to terminate the domain
> only, not Xen. Can you also please printk the exit_reason for this case?
> 
> From boot.7:
> ---
> Then XEN crashed
> 
> (XEN) __hvm_bug at vmx.c:2286
> (XEN) ----[ Xen-3.0-unstable    Not tainted ]----
> (XEN) CPU:    0
> (XEN) RIP:    0060:[<00000000c0100264>]
> (XEN) RFLAGS: 0000000000010006   CONTEXT: hvm
> (XEN) rax: 0000000000000671   rbx: 00000000c038fff0   rcx:
> 0000000000000003
> (XEN) rdx: 0000000000000fc0   rsi: 000000000000fffe   rdi:
> 00000000c040736c
> (XEN) rbp: 000000000048c007   rsp: 00000000c031c058   r8:
> 0000000000000000
> (XEN) r9:  0000000000000000   r10: 0000000000000000   r11:
> 0000000000000000
> (XEN) r12: 0000000000000000   r13: 0000000000000000   r14:
> 0000000000000000
> (XEN) r15: 0000000000000000   cr0: 0000000080050033   cr3:
> 00000000037f5000
> (XEN) ds: 007b   es: 007b   fs: 0000   gs: 0000   ss: 0068   cs: 0060
> (XEN) domain_crash_sync called from vmx.c:2286
> 
> 
> Thanks,
> Jun
> ---
> Intel Open Source Technology Center