Christopher S. Aker
2007-Nov-19 18:00 UTC
[Xen-devel] Xen 3.1.2 + 2.6.23.8 == traps.c:403:d0 Unhandled invalid opcode fault/trap [#6] in domain 0 on VCPU 0 [ec=0000]
Xen 3.1.2, 64bit + 2.6.23.8-pae for Dom0 gives me the following (XEN) Freed 108kB init memory. (XEN) traps.c:403:d0 Unhandled invalid opcode fault/trap [#6] in domain 0 on VCPU 0 [ec=0000] (XEN) domain_crash_sync called from entry.S (XEN) Domain 0 (vcpu#0) crashed on cpu#0: (XEN) ----[ Xen-3.1.2 x86_64 debug=n Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: e019:[<00000000c06402a8>] (XEN) RFLAGS: 0000000000000202 CONTEXT: guest (XEN) rax: 00000000c0703000 rbx: 0000000000000000 rcx: 0000000000000000 (XEN) rdx: 0000000000000000 rsi: 00000000c0703007 rdi: 00000000c0579f44 (XEN) rbp: 0000000000000000 rsp: 00000000c0633fd4 r8: 0000000000000000 (XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000 (XEN) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000000 (XEN) r15: 0000000000000000 cr0: 000000008005003b cr4: 00000000000026b0 (XEN) cr3: 00000006209f3000 cr2: 0000000000000000 (XEN) ds: e021 es: e021 fs: e021 gs: e021 ss: e021 cs: e019 (XEN) Guest stack trace from esp=c0633fd4: (XEN) c06402a8 0001e019 00010002 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 c0703000 00000000 c0639736 c063973e c0639746 c01012c5 c0101dab (XEN) c0101df7 c0640890 c01020d7 c01024da c0640adf c0640b09 c0104455 c0104475 (XEN) c01044b3 c0640b8f c0640c08 c0640c4c c0104937 c01049fb c0104a51 c0104ad9 (XEN) c0104b57 c0104d25 c01052d8 c0105e6d c0106037 c0106057 c01063c1 c0106444 (XEN) c01079d2 c0108da0 c0109685 c01096bb c0109a77 c0109a80 c0109ac0 c0109acd (XEN) c0109ae3 c0109dac c0109db5 c0109dc7 c0109e1b c0109e79 c0109e99 c0109ea2 (XEN) c0109fb7 c0109fc9 c010a144 c010a1c4 c010a400 c010a688 c010a6de c010a7a1 (XEN) c010a8bb c010aa26 c010aa64 c06411fd c010ad13 c0642c71 c0642c79 c06431ea (XEN) c06431f3 c0643649 c06436d5 c064384e c0643b9a c0643ba9 c0643baf c0643bbe (XEN) c0643bce c0643e6c c06441f8 c064449a c06444f8 c064450e c064451c c064452b (XEN) c064454a c0644663 c064473e c06447bc c06447c2 c0644bcd c0644be2 c0644bec (XEN) c0644e0e c0644edf c064519d c064526c c0645271 c0645282 c064542a c064547d (XEN) c0645532 c064594a c0645bac c0645c7f c0645c8e c0645d41 c0645d55 c0645d75 (XEN) c0645d9d c0645da7 c06468a9 c0646987 c06469a5 c06469ac c0646be8 c010e91e (XEN) c010e959 c010e979 c01104a7 c01114f2 c0111552 c0111be2 c0111c52 c0111eec (XEN) c0111f17 c0112ae8 c0112b60 c0112c62 c0112c82 c0112ce0 c0112d26 c0112d9f (XEN) c0112e39 c0113095 c0113175 c01132cc c06486f9 c0648784 c064878f c0648797 (XEN) c064879c c06487a4 c06487ac c06487bd c06487d0 c0648868 c064887b c06488a4 (XEN) c06488b2 c0648984 c064898c c0648994 c064899c c0648af8 c0648c2f c0648ca4 Full log here: http://pastebin.linode.com/20 Thoughts? Thanks, -Chris _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2007-Nov-20 10:41 UTC
Re: [Xen-devel] Xen 3.1.2 + 2.6.23.8 == traps.c:403:d0 Unhandled invalid opcode fault/trap [#6] in domain 0 on VCPU 0 [ec=0000]
On 19/11/07 18:00, "Christopher S. Aker" <caker@theshore.net> wrote:> Full log here: http://pastebin.linode.com/20 > > Thoughts?There are some possibilities. Do you have the vmlinux file for the crashing kernel? -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Christopher S. Aker
2007-Nov-20 14:10 UTC
Re: [Xen-devel] Xen 3.1.2 + 2.6.23.8 == traps.c:403:d0 Unhandled invalid opcode fault/trap [#6] in domain 0 on VCPU 0 [ec=0000]
Keir Fraser wrote:> On 19/11/07 18:00, "Christopher S. Aker" <caker@theshore.net> wrote: > >> Full log here: http://pastebin.linode.com/20 >> >> Thoughts? > > There are some possibilities. Do you have the vmlinux file for the crashing > kernel?Xen, the dom0 kernel and config are located here: http://www.linode.com/~caker/xen/BUGopcode1/ Thanks, -Chris _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2007-Nov-20 14:22 UTC
Re: [Xen-devel] Xen 3.1.2 + 2.6.23.8 == traps.c:403:d0 Unhandled invalid opcode fault/trap [#6] in domain 0 on VCPU 0 [ec=0000]
Two compounded problems. Firstly, the 2.6.23 Xen support only works as domU, not as dom0. Secondly, because the dom0 domain builder inside Xen sets a ''magic'' string in start_info as ''xen-3.1-...'' rather than ''xen-3.0-...'' as the user-space domain builder does, the 2.6.23 kernel BUG_ON()s very very early when run as dom0. I''ve cc''ed Jeremy as I believe the BUG_ON() should simply be got rid of (or at least should perhaps only check for the ''xen-'' prefix). But you''re not going to have any luck running that kernel as dom0 even if the offending BUG_ON() is removed. -- Keir On 19/11/07 18:00, "Christopher S. Aker" <caker@theshore.net> wrote:> Xen 3.1.2, 64bit + 2.6.23.8-pae for Dom0 gives me the following > > (XEN) Freed 108kB init memory. > (XEN) traps.c:403:d0 Unhandled invalid opcode fault/trap [#6] in domain > 0 on VCPU 0 [ec=0000] > (XEN) domain_crash_sync called from entry.S > (XEN) Domain 0 (vcpu#0) crashed on cpu#0: > (XEN) ----[ Xen-3.1.2 x86_64 debug=n Not tainted ]---- > (XEN) CPU: 0 > (XEN) RIP: e019:[<00000000c06402a8>] > (XEN) RFLAGS: 0000000000000202 CONTEXT: guest > (XEN) rax: 00000000c0703000 rbx: 0000000000000000 rcx: 0000000000000000 > (XEN) rdx: 0000000000000000 rsi: 00000000c0703007 rdi: 00000000c0579f44 > (XEN) rbp: 0000000000000000 rsp: 00000000c0633fd4 r8: 0000000000000000 > (XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000 > (XEN) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000000 > (XEN) r15: 0000000000000000 cr0: 000000008005003b cr4: 00000000000026b0 > (XEN) cr3: 00000006209f3000 cr2: 0000000000000000 > (XEN) ds: e021 es: e021 fs: e021 gs: e021 ss: e021 cs: e019 > (XEN) Guest stack trace from esp=c0633fd4: > (XEN) c06402a8 0001e019 00010002 00000000 00000000 00000000 00000000 > 00000000 > (XEN) 00000000 c0703000 00000000 c0639736 c063973e c0639746 c01012c5 > c0101dab > (XEN) c0101df7 c0640890 c01020d7 c01024da c0640adf c0640b09 c0104455 > c0104475 > (XEN) c01044b3 c0640b8f c0640c08 c0640c4c c0104937 c01049fb c0104a51 > c0104ad9 > (XEN) c0104b57 c0104d25 c01052d8 c0105e6d c0106037 c0106057 c01063c1 > c0106444 > (XEN) c01079d2 c0108da0 c0109685 c01096bb c0109a77 c0109a80 c0109ac0 > c0109acd > (XEN) c0109ae3 c0109dac c0109db5 c0109dc7 c0109e1b c0109e79 c0109e99 > c0109ea2 > (XEN) c0109fb7 c0109fc9 c010a144 c010a1c4 c010a400 c010a688 c010a6de > c010a7a1 > (XEN) c010a8bb c010aa26 c010aa64 c06411fd c010ad13 c0642c71 c0642c79 > c06431ea > (XEN) c06431f3 c0643649 c06436d5 c064384e c0643b9a c0643ba9 c0643baf > c0643bbe > (XEN) c0643bce c0643e6c c06441f8 c064449a c06444f8 c064450e c064451c > c064452b > (XEN) c064454a c0644663 c064473e c06447bc c06447c2 c0644bcd c0644be2 > c0644bec > (XEN) c0644e0e c0644edf c064519d c064526c c0645271 c0645282 c064542a > c064547d > (XEN) c0645532 c064594a c0645bac c0645c7f c0645c8e c0645d41 c0645d55 > c0645d75 > (XEN) c0645d9d c0645da7 c06468a9 c0646987 c06469a5 c06469ac c0646be8 > c010e91e > (XEN) c010e959 c010e979 c01104a7 c01114f2 c0111552 c0111be2 c0111c52 > c0111eec > (XEN) c0111f17 c0112ae8 c0112b60 c0112c62 c0112c82 c0112ce0 c0112d26 > c0112d9f > (XEN) c0112e39 c0113095 c0113175 c01132cc c06486f9 c0648784 c064878f > c0648797 > (XEN) c064879c c06487a4 c06487ac c06487bd c06487d0 c0648868 c064887b > c06488a4 > (XEN) c06488b2 c0648984 c064898c c0648994 c064899c c0648af8 c0648c2f > c0648ca4 > > Full log here: http://pastebin.linode.com/20 > > Thoughts? > > Thanks, > -Chris > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2007-Nov-20 15:11 UTC
Re: [Xen-devel] Xen 3.1.2 + 2.6.23.8 == traps.c:403:d0 Unhandled invalid opcode fault/trap [#6] in domain 0 on VCPU 0 [ec=0000]
Keir Fraser wrote:> Two compounded problems. Firstly, the 2.6.23 Xen support only works as domU, > not as dom0. Secondly, because the dom0 domain builder inside Xen sets a > ''magic'' string in start_info as ''xen-3.1-...'' rather than ''xen-3.0-...'' as > the user-space domain builder does, the 2.6.23 kernel BUG_ON()s very very > early when run as dom0. > > I''ve cc''ed Jeremy as I believe the BUG_ON() should simply be got rid of (or > at least should perhaps only check for the ''xen-'' prefix).Fair enough. I was wondering what it actually means: is it just a hypervisor version string, or is it a hypervisor ABI signature? Could I reasonably check for "xen-3", or will Xen 4.x put something else there? J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2007-Nov-20 15:30 UTC
Re: [Xen-devel] Xen 3.1.2 + 2.6.23.8 == traps.c:403:d0 Unhandled invalid opcode fault/trap [#6] in domain 0 on VCPU 0 [ec=0000]
On 20/11/07 15:11, "Jeremy Fitzhardinge" <jeremy@goop.org> wrote:> Fair enough. I was wondering what it actually means: is it just a > hypervisor version string, or is it a hypervisor ABI signature? Could I > reasonably check for "xen-3", or will Xen 4.x put something else there?I think it''s most useful as an interface string so I''ll fix Xen to poke the same thing as the user-space builder. But there will still be Xen versions out there that poke xen-3.1 rather than xen-3.0. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel