[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-devel] Problems creating DomUs with large memory system/PAEenabled
Keir, I am seeing the same issue with x86_64 Xen on the ES7000. We are looking into the problem. Aravindh (XEN) (file=traps.c, line=960) Non-priv domain attempted RDMSR(00000000c0000080,00020000,00020000). (XEN) CPU: 3 (XEN) RIP: e010:[<ffff830000123cff>] get_page_from_l1e+0x1af/0x4e0 (XEN) RFLAGS: 0000000000010246 CONTEXT: hypervisor (XEN) rax: 0000000080000002 rbx: 0000000080000003 rcx: 00000000001f7080 (XEN) rdx: 00000000001f7080 rsi: 0000000080000002 rdi: 000000000047e825 (XEN) rbp: 00000000001f7080 rsp: ffff8300001dfdb8 r8: 00000000001f7080 (XEN) r9: 00000000000e61a3 r10: 0fffffffe0000000 r11: ffff830000196680 (XEN) r12: 0000000080000002 r13: ffff8284023f4128 r14: ffff8300001f7080 (XEN) r15: ffff8300001f7080 cr0: 000000008005003b cr3: 00000000e7ea0000 (XEN) Xen stack trace from rsp=ffff8300001dfdb8: (XEN) ffff830000184ca0 ffff83000012000b ffff8300e61a3600 00000000e61a1065 (XEN) 00000000e61a1067 ffff8300001f7080 000000000047e82f ffff830000124d31 (XEN) ffff8284023f4178 00000000e61a1065 ffff8284023f4178 ffff8300e61a3600 (XEN) ffff828400000000 ffff8300001294e8 ffff8300001f4080 000000000007a120 (XEN) 0000000000000000 0000000000000002 ffff8284021b1f50 ffff8300001f7080 (XEN) ffff8300001f7080 00000000000e61a3 ffff8300001dff28 ffff8300001f4080 (XEN) 00000000ffc03ff8 0000000000000003 0000000000000000 00000000000e61a3 (XEN) 00007ff000000003 0000000000000000 00000001001f7080 ffffffff80393e40 (XEN) ffffffff807ff000 ffff8300001286c5 000000000000002c 0000000000183900 (XEN) 00000000e61a3600 00000000e61a1065 ffff8300001f4080 ffff8300001f4080 (XEN) 0000000000000600 ffffffff8034696d ffffffff802b0af3 ffffffff802b0ae3 (XEN) ffff880000000000 ffff83000013be3c ffff880000000000 ffffffff802b0ae3 (XEN) ffffffff802b0af3 ffffffff8034696d 0000000000000600 00000000e61a3000 (XEN) 0000000000000206 0000000000007ff0 0000000000000000 0000000000000000 (XEN) 0000000000000001 ffffffff8011caa1 0000000000000000 0000000000000001 (XEN) ffffffff80393e40 0000010000000000 ffffffff8011caa1 000000000000e033 (XEN) 0000000000000206 ffffffff80393e40 000000000000e02b 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000003 (XEN) ffff8300001f4080 (XEN) Xen call trace: (XEN) [<ffff830000123cff>] get_page_from_l1e+0x1af/0x4e0 (XEN) [<ffff83000012000b>] apic_timer_interrupt+0x2b/0x30 (XEN) [<ffff830000124d31>] mod_l1_entry+0x121/0x2d0 (XEN) [<ffff8300001294e8>] do_mmu_update+0x808/0x1a00 (XEN) [<ffff8300001286c5>] do_update_va_mapping+0xc5/0x5f0 (XEN) [<ffff83000013be3c>] syscall_enter+0x5c/0x61 (XEN) (XEN) (XEN) **************************************** (XEN) Panic on CPU 3: (XEN) CPU3 FATAL TRAP: vector = 17 (alignment check) (XEN) [error_code=0000] (XEN) **************************************** > -----Original Message----- > From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx] > Sent: Thursday, September 22, 2005 4:54 PM > To: Subrahmanian, Raj > Cc: Vessey, Bruce A; Puthiyaparambil, Aravindh; xen- > devel@xxxxxxxxxxxxxxxxxxx; Koren, Bradley J > Subject: Re: [Xen-devel] Problems creating DomUs with large memory > system/PAEenabled > > > On 22 Sep 2005, at 21:43, Subrahmanian, Raj wrote: > > > I started xend and when I tried to bring up a virtual machine, the > > system crashed. > > This is what I see on the serial output. > > Please dig deeper if you can. Something is odd here -- you cannot crash > on an 'alignment check' in Xen, as that fault can only occur in ring 3, > and with the AC flag set in EFLAGS (which it isn't). > > That's got to be worth tracking down if this problem is reproducible > for you. > > -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |