thr3ads.net - Xen devel - [Xen-devel] xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain [Apr 2007]

If this information is useful, please help other people find it:
Share via:

Andi Kleen

2007-Apr-25 19:10 UTC

[Xen-devel] xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain

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


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Keir Fraser

2007-Apr-25 19:21 UTC

head link

Re: [Xen-devel] xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain

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)


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Andi Kleen

2007-Apr-25 19:27 UTC

head link

[Xen-devel] Re: xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain II

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

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Andi Kleen

2007-Apr-25 19:30 UTC

head link

Re: [Xen-devel] xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain

> 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

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Keir Fraser

2007-Apr-25 19:51 UTC

head link

Re: [Xen-devel] xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain

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


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Andi Kleen

2007-Apr-25 20:00 UTC

head link

Re: [Xen-devel] xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain

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

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Keir Fraser

2007-Apr-25 21:09 UTC

head link

Re: [Xen-devel] xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain

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



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Andi Kleen

2007-Apr-25 21:18 UTC

head link

Re: [Xen-devel] xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain

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

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Xen devel - Apr 2007 - xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain

[Xen-devel] xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain

Re: [Xen-devel] xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain

[Xen-devel] Re: xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain II

Re: [Xen-devel] xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain

Re: [Xen-devel] xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain

Re: [Xen-devel] xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain

Re: [Xen-devel] xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain

Re: [Xen-devel] xen 3.0.5-rc3 vmx_create_vmcs panic on starting VT HVM domain