* xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain
@ 2007-04-25 19:10 Andi Kleen
2007-04-25 19:21 ` Keir Fraser
2007-04-25 19:27 ` xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain II Andi Kleen
0 siblings, 2 replies; 8+ messages in thread
From: Andi Kleen @ 2007-04-25 19:10 UTC (permalink / raw)
To: xen-devel
I installed 3.0.5-rc3 on a SUSE 10.0 VT system.
First during the boot up I get one message like
(XEN) mm.c:633:d0 Error getting mfn 100 (pfn 5555555555555555) from L1 entry 8000000000100125 for dom32753
When I start a VT domain running an older linux system I get
(XEN) ----[ Xen-3.0.5-rc3 x86_64 debug=n Not tainted ]----
(XEN) CPU: 0
(XEN) RIP: e008:[<ffff83000015e806>] vmx_create_vmcs+0x416/0x480
(XEN) RFLAGS: 0000000000010242 CONTEXT: hypervisor
(XEN) rax: 0000000000002012 rbx: ffff830000220080 rcx: 000000003dcd5000
(XEN) rdx: 0000000000002012 rsi: 0000000000000000 rdi: 0000000000000650
(XEN) rbp: ffff830000220080 rsp: ffff8300001e3ce8 r8: ffffffffffffffff
(XEN) r9: 0000000000000000 r10: 0000000000000001 r11: 0000000000000001
(XEN) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000001
(XEN) r15: 0000000000000040 cr0: 000000008005003b cr4: 00000000000026f0
(XEN) cr3: 0000000008440000 cr2: 00002b7295df2f70
(XEN) ds: 0000 es: 0000 fs: 0063 gs: 0000 ss: e010 cs: e008
(XEN) Xen stack trace from rsp=ffff8300001e3ce8:
(XEN) ffff830000220080 ffff83000015e901 0000000000000000 ffff830000154f36
(XEN) 0001830000220080 0000000000000000 ffff830000220080 ffff830000149d59
(XEN) ffff830000220080 ffff830000220080 ffff830000236080 ffff83000012833e
(XEN) ffff830000220080 ffff830000220080 ffff830000236080 ffff8300001086c1
(XEN) 0000000000000042 0000000000000001 0000000000305000 ffff830000236080
(XEN) 0000000000305000 ffff8300001074e4 0000000100000000 0000000000000000
(XEN) 000000050000000f 0000000043800001 0000000000000001 00002b7293294662
(XEN) 00002b7295de46c0 00002b7293446e30 0000000043802bfc 0000000043802bf8
(XEN) 0000000000000001 0000000043802db8 000000000072f120 00002aaaaac16440
(XEN) 00002b72931c33c0 00002b7293443cc0 00002b7293443cc0 00002b7293443cc0
(XEN) 00002b7293443cc0 00002b7293298a0b 0000000100000001 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000003 0000000000000202
(XEN) ffffffff802098e4 0000000000000100 00002b7293ca8c19 000000000000e033
(XEN) 0000000000000202 ffff83000023a080 0000000043802ba0 0000000000305000
(XEN) 0000000000000009 0000000000305000 0000000000000000 ffff83000017c102
(XEN) 0000000000000000 0000000000305000 0000000000000009 0000000000305000
(XEN) 0000000043802ba0 ffff8800383b5880 0000000000000282 00002aaaaabdfa10
(XEN) Xen call trace:
(XEN) [<ffff83000015e806>] vmx_create_vmcs+0x416/0x480
(XEN) [<ffff83000015e901>] vmx_vcpu_initialise+0x61/0xa0
(XEN) [<ffff830000154f36>] vlapic_init+0xe6/0x150
(XEN) [<ffff830000149d59>] hvm_vcpu_initialise+0x29/0x110
(XEN) [<ffff83000012833e>] vcpu_initialise+0x2e/0x110
(XEN) [<ffff8300001086c1>] alloc_vcpu+0xb1/0x120
(XEN) [<ffff8300001074e4>] do_domctl+0x5c4/0xc40
(XEN) [<ffff83000017c102>] syscall_enter+0x62/0x67
(XEN)
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) FATAL TRAP: vector = 6 (invalid opcode)
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...
-Andi
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain
2007-04-25 19:10 xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain Andi Kleen
@ 2007-04-25 19:21 ` Keir Fraser
2007-04-25 19:30 ` Andi Kleen
2007-04-25 19:27 ` xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain II Andi Kleen
1 sibling, 1 reply; 8+ messages in thread
From: Keir Fraser @ 2007-04-25 19:21 UTC (permalink / raw)
To: Andi Kleen, xen-devel
On 25/4/07 20:10, "Andi Kleen" <ak@suse.de> wrote:
> I installed 3.0.5-rc3 on a SUSE 10.0 VT system.
Thanks!
> First during the boot up I get one message like
This one's harmless noise from a debug build. Default logging level is
everything.
> When I start a VT domain running an older linux system I get
Not good. 'Invalid opcode' with no BUG or ASSERT message probably means that
a VMWRITE instruction failed. Do you have your xen-syms file handy? If you
could send me that privately that would be superb (or an objdump -d of the
vmx_create_vmcs() function would suffice). What particular type of processor
were you running on?
Thanks again,
Keir
> (XEN) ----[ Xen-3.0.5-rc3 x86_64 debug=n Not tainted ]----
> (XEN) CPU: 0
> (XEN) RIP: e008:[<ffff83000015e806>] vmx_create_vmcs+0x416/0x480
> (XEN) RFLAGS: 0000000000010242 CONTEXT: hypervisor
> (XEN) rax: 0000000000002012 rbx: ffff830000220080 rcx: 000000003dcd5000
> (XEN) rdx: 0000000000002012 rsi: 0000000000000000 rdi: 0000000000000650
> (XEN) rbp: ffff830000220080 rsp: ffff8300001e3ce8 r8: ffffffffffffffff
> (XEN) r9: 0000000000000000 r10: 0000000000000001 r11: 0000000000000001
> (XEN) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000001
> (XEN) r15: 0000000000000040 cr0: 000000008005003b cr4: 00000000000026f0
> (XEN) cr3: 0000000008440000 cr2: 00002b7295df2f70
> (XEN) ds: 0000 es: 0000 fs: 0063 gs: 0000 ss: e010 cs: e008
> (XEN) Xen stack trace from rsp=ffff8300001e3ce8:
> (XEN) ffff830000220080 ffff83000015e901 0000000000000000 ffff830000154f36
> (XEN) 0001830000220080 0000000000000000 ffff830000220080 ffff830000149d59
> (XEN) ffff830000220080 ffff830000220080 ffff830000236080 ffff83000012833e
> (XEN) ffff830000220080 ffff830000220080 ffff830000236080 ffff8300001086c1
> (XEN) 0000000000000042 0000000000000001 0000000000305000 ffff830000236080
> (XEN) 0000000000305000 ffff8300001074e4 0000000100000000 0000000000000000
> (XEN) 000000050000000f 0000000043800001 0000000000000001 00002b7293294662
> (XEN) 00002b7295de46c0 00002b7293446e30 0000000043802bfc 0000000043802bf8
> (XEN) 0000000000000001 0000000043802db8 000000000072f120 00002aaaaac16440
> (XEN) 00002b72931c33c0 00002b7293443cc0 00002b7293443cc0 00002b7293443cc0
> (XEN) 00002b7293443cc0 00002b7293298a0b 0000000100000001 0000000000000000
> (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> (XEN) 0000000000000000 0000000000000000 0000000000000003 0000000000000202
> (XEN) ffffffff802098e4 0000000000000100 00002b7293ca8c19 000000000000e033
> (XEN) 0000000000000202 ffff83000023a080 0000000043802ba0 0000000000305000
> (XEN) 0000000000000009 0000000000305000 0000000000000000 ffff83000017c102
> (XEN) 0000000000000000 0000000000305000 0000000000000009 0000000000305000
> (XEN) 0000000043802ba0 ffff8800383b5880 0000000000000282 00002aaaaabdfa10
> (XEN) Xen call trace:
> (XEN) [<ffff83000015e806>] vmx_create_vmcs+0x416/0x480
> (XEN) [<ffff83000015e901>] vmx_vcpu_initialise+0x61/0xa0
> (XEN) [<ffff830000154f36>] vlapic_init+0xe6/0x150
> (XEN) [<ffff830000149d59>] hvm_vcpu_initialise+0x29/0x110
> (XEN) [<ffff83000012833e>] vcpu_initialise+0x2e/0x110
> (XEN) [<ffff8300001086c1>] alloc_vcpu+0xb1/0x120
> (XEN) [<ffff8300001074e4>] do_domctl+0x5c4/0xc40
> (XEN) [<ffff83000017c102>] syscall_enter+0x62/0x67
> (XEN)
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) FATAL TRAP: vector = 6 (invalid opcode)
> (XEN) ****************************************
> (XEN)
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain II
2007-04-25 19:10 xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain Andi Kleen
2007-04-25 19:21 ` Keir Fraser
@ 2007-04-25 19:27 ` Andi Kleen
1 sibling, 0 replies; 8+ messages in thread
From: Andi Kleen @ 2007-04-25 19:27 UTC (permalink / raw)
To: xen-devel
On Wednesday 25 April 2007 21:10:14 Andi Kleen wrote:
>
> I installed 3.0.5-rc3 on a SUSE 10.0 VT system.
>
> First during the boot up I get one message like
>
> (XEN) mm.c:633:d0 Error getting mfn 100 (pfn 5555555555555555) from L1 entry 8000000000100125 for dom32753
>
> When I start a VT domain running an older linux system I get
>
> (XEN) ----[ Xen-3.0.5-rc3 x86_64 debug=n Not tainted ]----
> (XEN) CPU: 0
> (XEN) RIP: e008:[<ffff83000015e806>] vmx_create_vmcs+0x416/0x480
It's inside this __vmwrite
__vmwrite(VIRTUAL_APIC_PAGE_ADDR,
page_to_maddr(vcpu_vlapic(v)->regs_page));
I guess my system is too old.
-Andi
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain
2007-04-25 19:21 ` Keir Fraser
@ 2007-04-25 19:30 ` Andi Kleen
2007-04-25 19:51 ` Keir Fraser
0 siblings, 1 reply; 8+ messages in thread
From: Andi Kleen @ 2007-04-25 19:30 UTC (permalink / raw)
To: Keir Fraser; +Cc: xen-devel
> Not good. 'Invalid opcode' with no BUG or ASSERT message probably means that
> a VMWRITE instruction failed. Do you have your xen-syms file handy? If you
> could send me that privately that would be superb (or an objdump -d of the
> vmx_create_vmcs() function would suffice). What particular type of processor
> were you running on?
It's this line
__vmwrite(VIRTUAL_APIC_PAGE_ADDR,
page_to_maddr(vcpu_vlapic(v)->regs_page));
It's an older preproduction VT P4 system. Worked with earlier Xen releases,
but perhaps it's too old now.
-Andi
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain
2007-04-25 19:30 ` Andi Kleen
@ 2007-04-25 19:51 ` Keir Fraser
2007-04-25 20:00 ` Andi Kleen
0 siblings, 1 reply; 8+ messages in thread
From: Keir Fraser @ 2007-04-25 19:51 UTC (permalink / raw)
To: Andi Kleen; +Cc: xen-devel
On 25/4/07 20:30, "Andi Kleen" <ak@suse.de> wrote:
> It's this line
>
> __vmwrite(VIRTUAL_APIC_PAGE_ADDR,
> page_to_maddr(vcpu_vlapic(v)->regs_page));
>
> It's an older preproduction VT P4 system. Worked with earlier Xen releases,
> but perhaps it's too old now.
It's possible, but actually this may be detectable and easily worked around.
What does MSR 0x482 contain?
-- Keir
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain
2007-04-25 19:51 ` Keir Fraser
@ 2007-04-25 20:00 ` Andi Kleen
2007-04-25 21:09 ` Keir Fraser
0 siblings, 1 reply; 8+ messages in thread
From: Andi Kleen @ 2007-04-25 20:00 UTC (permalink / raw)
To: Keir Fraser; +Cc: xen-devel
On Wednesday 25 April 2007 21:51:07 Keir Fraser wrote:
> On 25/4/07 20:30, "Andi Kleen" <ak@suse.de> wrote:
>
> > It's this line
> >
> > __vmwrite(VIRTUAL_APIC_PAGE_ADDR,
> > page_to_maddr(vcpu_vlapic(v)->regs_page));
> >
> > It's an older preproduction VT P4 system. Worked with earlier Xen releases,
> > but perhaps it's too old now.
>
> It's possible, but actually this may be detectable and easily worked around.
> What does MSR 0x482 contain?
0x6799fffe0401e172
-Andi
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain
2007-04-25 20:00 ` Andi Kleen
@ 2007-04-25 21:09 ` Keir Fraser
2007-04-25 21:18 ` Andi Kleen
0 siblings, 1 reply; 8+ messages in thread
From: Keir Fraser @ 2007-04-25 21:09 UTC (permalink / raw)
To: Andi Kleen; +Cc: xen-devel
[-- Attachment #1: Type: text/plain, Size: 500 bytes --]
On 25/4/07 21:00, "Andi Kleen" <ak@suse.de> wrote:
> On Wednesday 25 April 2007 21:51:07 Keir Fraser wrote:
>> On 25/4/07 20:30, "Andi Kleen" <ak@suse.de> wrote:
>>>
>>> It's an older preproduction VT P4 system. Worked with earlier Xen releases,
>>> but perhaps it's too old now.
>>
>> It's possible, but actually this may be detectable and easily worked around.
>> What does MSR 0x482 contain?
>
> 0x6799fffe0401e172
The attached patch should fix the crash. I've queued it for 3.0.5.
-- Keir
[-- Attachment #2: tpr-shadow.patch --]
[-- Type: application/octet-stream, Size: 4777 bytes --]
# HG changeset patch
# User Keir Fraser <keir@xensource.com>
# Date 1177535173 -3600
# Node ID 59ea9dadfd078d0beed86aa11c807aa62f6ce399
# Parent 2b09108f365ee98a033c4894a14fdcfda79128fd
hvm vmx: Only use TPR_SHADOW feature if supported.
Signed-off-by: Keir Fraser <keir@xensource.com>
diff -r 2b09108f365e -r 59ea9dadfd07 xen/arch/x86/hvm/vmx/vmcs.c
--- a/xen/arch/x86/hvm/vmx/vmcs.c Wed Apr 25 18:12:03 2007 +0100
+++ b/xen/arch/x86/hvm/vmx/vmcs.c Wed Apr 25 22:06:13 2007 +0100
@@ -45,9 +45,9 @@ u32 vmx_vmentry_control;
static u32 vmcs_revision_id;
-static u32 adjust_vmx_controls(u32 ctl_min, u32 ctl_max, u32 msr)
-{
- u32 vmx_msr_low, vmx_msr_high, ctl = ctl_max;
+static u32 adjust_vmx_controls(u32 ctl_min, u32 ctl_opt, u32 msr)
+{
+ u32 vmx_msr_low, vmx_msr_high, ctl = ctl_min | ctl_opt;
rdmsr(msr, vmx_msr_low, vmx_msr_high);
@@ -56,46 +56,55 @@ static u32 adjust_vmx_controls(u32 ctl_m
/* Ensure minimum (required) set of control bits are supported. */
BUG_ON(ctl_min & ~ctl);
- BUG_ON(ctl_min & ~ctl_max);
return ctl;
}
void vmx_init_vmcs_config(void)
{
- u32 vmx_msr_low, vmx_msr_high, min, max;
+ u32 vmx_msr_low, vmx_msr_high, min, opt;
u32 _vmx_pin_based_exec_control;
u32 _vmx_cpu_based_exec_control;
u32 _vmx_vmexit_control;
u32 _vmx_vmentry_control;
- min = max = PIN_BASED_EXT_INTR_MASK | PIN_BASED_NMI_EXITING;
+ min = PIN_BASED_EXT_INTR_MASK | PIN_BASED_NMI_EXITING;
+ opt = 0;
_vmx_pin_based_exec_control = adjust_vmx_controls(
- min, max, MSR_IA32_VMX_PINBASED_CTLS_MSR);
-
- min = max = (CPU_BASED_HLT_EXITING |
- CPU_BASED_INVDPG_EXITING |
- CPU_BASED_MWAIT_EXITING |
- CPU_BASED_MOV_DR_EXITING |
- CPU_BASED_ACTIVATE_IO_BITMAP |
- CPU_BASED_USE_TSC_OFFSETING);
+ min, opt, MSR_IA32_VMX_PINBASED_CTLS_MSR);
+
+ min = (CPU_BASED_HLT_EXITING |
+ CPU_BASED_INVDPG_EXITING |
+ CPU_BASED_MWAIT_EXITING |
+ CPU_BASED_MOV_DR_EXITING |
+ CPU_BASED_ACTIVATE_IO_BITMAP |
+ CPU_BASED_USE_TSC_OFFSETING);
+ opt = CPU_BASED_ACTIVATE_MSR_BITMAP;
#ifdef __x86_64__
- min = max |= CPU_BASED_CR8_LOAD_EXITING | CPU_BASED_CR8_STORE_EXITING;
-#endif
- max |= CPU_BASED_ACTIVATE_MSR_BITMAP;
+ opt |= CPU_BASED_TPR_SHADOW;
+#endif
_vmx_cpu_based_exec_control = adjust_vmx_controls(
- min, max, MSR_IA32_VMX_PROCBASED_CTLS_MSR);
-
- min = max = VM_EXIT_ACK_INTR_ON_EXIT;
+ min, opt, MSR_IA32_VMX_PROCBASED_CTLS_MSR);
#ifdef __x86_64__
- min = max |= VM_EXIT_IA32E_MODE;
+ if ( !(_vmx_cpu_based_exec_control & CPU_BASED_TPR_SHADOW) )
+ {
+ min |= CPU_BASED_CR8_LOAD_EXITING | CPU_BASED_CR8_STORE_EXITING;
+ _vmx_cpu_based_exec_control = adjust_vmx_controls(
+ min, opt, MSR_IA32_VMX_PROCBASED_CTLS_MSR);
+ }
+#endif
+
+ min = VM_EXIT_ACK_INTR_ON_EXIT;
+ opt = 0;
+#ifdef __x86_64__
+ min |= VM_EXIT_IA32E_MODE;
#endif
_vmx_vmexit_control = adjust_vmx_controls(
- min, max, MSR_IA32_VMX_EXIT_CTLS_MSR);
-
- min = max = 0;
+ min, opt, MSR_IA32_VMX_EXIT_CTLS_MSR);
+
+ min = opt = 0;
_vmx_vmentry_control = adjust_vmx_controls(
- min, max, MSR_IA32_VMX_ENTRY_CTLS_MSR);
+ min, opt, MSR_IA32_VMX_ENTRY_CTLS_MSR);
rdmsr(MSR_IA32_VMX_BASIC_MSR, vmx_msr_low, vmx_msr_high);
@@ -414,13 +423,12 @@ static void construct_vmcs(struct vcpu *
#ifdef __x86_64__
/* VLAPIC TPR optimisation. */
- v->arch.hvm_vcpu.u.vmx.exec_control |= CPU_BASED_TPR_SHADOW;
- v->arch.hvm_vcpu.u.vmx.exec_control &=
- ~(CPU_BASED_CR8_STORE_EXITING | CPU_BASED_CR8_LOAD_EXITING);
- __vmwrite(CPU_BASED_VM_EXEC_CONTROL, v->arch.hvm_vcpu.u.vmx.exec_control);
- __vmwrite(VIRTUAL_APIC_PAGE_ADDR,
- page_to_maddr(vcpu_vlapic(v)->regs_page));
- __vmwrite(TPR_THRESHOLD, 0);
+ if ( cpu_has_vmx_tpr_shadow )
+ {
+ __vmwrite(VIRTUAL_APIC_PAGE_ADDR,
+ page_to_maddr(vcpu_vlapic(v)->regs_page));
+ __vmwrite(TPR_THRESHOLD, 0);
+ }
#endif
__vmwrite(GUEST_LDTR_SELECTOR, 0);
diff -r 2b09108f365e -r 59ea9dadfd07 xen/include/asm-x86/hvm/vmx/vmcs.h
--- a/xen/include/asm-x86/hvm/vmx/vmcs.h Wed Apr 25 18:12:03 2007 +0100
+++ b/xen/include/asm-x86/hvm/vmx/vmcs.h Wed Apr 25 22:06:13 2007 +0100
@@ -119,6 +119,8 @@ extern u32 vmx_vmexit_control;
#define VM_ENTRY_DEACT_DUAL_MONITOR 0x00000800
extern u32 vmx_vmentry_control;
+#define cpu_has_vmx_tpr_shadow \
+ (vmx_cpu_based_exec_control & CPU_BASED_TPR_SHADOW)
#define cpu_has_vmx_msr_bitmap \
(vmx_cpu_based_exec_control & CPU_BASED_ACTIVATE_MSR_BITMAP)
extern char *vmx_msr_bitmap;
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain
2007-04-25 21:09 ` Keir Fraser
@ 2007-04-25 21:18 ` Andi Kleen
0 siblings, 0 replies; 8+ messages in thread
From: Andi Kleen @ 2007-04-25 21:18 UTC (permalink / raw)
To: Keir Fraser; +Cc: xen-devel
On Wednesday 25 April 2007 23:09:16 Keir Fraser wrote:
> On 25/4/07 21:00, "Andi Kleen" <ak@suse.de> wrote:
> > On Wednesday 25 April 2007 21:51:07 Keir Fraser wrote:
> >> On 25/4/07 20:30, "Andi Kleen" <ak@suse.de> wrote:
> >>>
> >>> It's an older preproduction VT P4 system. Worked with earlier Xen releases,
> >>> but perhaps it's too old now.
> >>
> >> It's possible, but actually this may be detectable and easily worked around.
> >> What does MSR 0x482 contain?
> >
> > 0x6799fffe0401e172
>
> The attached patch should fix the crash. I've queued it for 3.0.5.
Yes works now with that patch. Thanks
-Andi
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2007-04-25 21:18 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-04-25 19:10 xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain Andi Kleen
2007-04-25 19:21 ` Keir Fraser
2007-04-25 19:30 ` Andi Kleen
2007-04-25 19:51 ` Keir Fraser
2007-04-25 20:00 ` Andi Kleen
2007-04-25 21:09 ` Keir Fraser
2007-04-25 21:18 ` Andi Kleen
2007-04-25 19:27 ` xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain II Andi Kleen
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.