Andrew Lyon
2008-Nov-30 19:47 UTC
[Xen-devel] (XEN) mm.c:707:d49 Error getting mfn 2fef3 (pfn 6aef3) from L1 entry
Hi, Can anybody advise me how to debug this crash? it happens when I try to start a 32 bit kernel on my 64 bit Xen system, the kernel is my own using opensuse 11.1 rc1 2.6.27.7 xen patches, the kernel works as 32 and 64 bit dom0, and as 64 bit domU PV, is there a technique to find out where in the kernel source the crash happens? i.e what line in the source code? (XEN) mm.c:707:d49 Error getting mfn 2fef3 (pfn 6aef3) from L1 entry 000000002fef3061 for dom49 (XEN) traps.c:437:d49 Unhandled invalid opcode fault/trap [#6] on VCPU 0 [ec=0000] (XEN) domain_crash_sync called from entry.S (XEN) Domain 49 (vcpu#0) crashed on cpu#7: (XEN) ----[ Xen-3.3.0 x86_64 debug=n Not tainted ]---- (XEN) CPU: 7 (XEN) RIP: e019:[<00000000c0212033>] (XEN) RFLAGS: 0000000000000282 EM: 1 CONTEXT: pv guest (XEN) rax: 00000000ffffffea rbx: 00000000f56fb000 rcx: 000000002fef3061 (XEN) rdx: 0000000000000000 rsi: 0000000000000006 rdi: 0000000000000000 (XEN) rbp: 000000000002fef3 rsp: 00000000c047df54 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: 000000022feeb000 cr2: 0000000000000000 (XEN) ds: e021 es: e021 fs: e021 gs: 0000 ss: e021 cs: e019 (XEN) Guest stack trace from esp=c047df54: (XEN) c0212033 0001e019 00010082 00000000 00000061 00000000 c020fd81 00104000 (XEN) f56fb000 00000000 000004ad 00000103 000012b4 c048afc6 00000061 80000000 (XEN) 004ad000 00000000 0061a027 00000000 00000000 c0445980 c0479640 c047dff4 (XEN) c048662f 00000000 0061f000 00000000 00000000 03040800 c0616000 00000000 (XEN) 00000000 03040800 c0616000 00000000 00000000 c04814fb c03b5000 c03f0102 (XEN) c0616000 03040800 00000000 c04813bc c04814c1 c04814c9 c04814d1 c0202408 (XEN) c020243b c02024dd c03a9bc8 c02027b4 c0202a79 c0202b4f c02032ef c0203818 (XEN) c0203c97 c0204331 c0204344 c0204368 c0204375 c02043f7 c02046d4 c0205134 (XEN) c0205203 c0205d42 c0205d87 c0205ddd c0206013 c02060c8 c02069b8 c0487768 (XEN) c0487770 c0207bf0 c0207bfe c0207c6e c0207c7c c0488973 c0488986 c02080e3 (XEN) c020816d c0208e42 c020903e c0209068 c0209070 c0209289 c0209290 c0209dd8 (XEN) c0209e5f c0209e6e c0209ea1 c0209eab c0209ee6 c0209eee c0209ef6 c03abf44 (XEN) c03ac0ea c03ac145 c03ac165 c03ac319 c03ac3d9 c03ac814 c0488c62 c0488c6a (XEN) c03acce5 c03acd47 c0488d8c c0488d94 c0488d9c c0488da4 c0488db2 c0488dba (XEN) c0488dc8 c0488dd0 c03ace21 c03ace8a c03ad00c c03ad026 c03ad078 c03ad0d7 (XEN) c03ad0dc c03ad301 c03ad374 c03ad37f c03ad38d c03ad416 c03ad428 c03ad517 (XEN) c03ad522 c03ad527 c03ad6a1 c03ad8ad c03ada60 c03ada99 c03adaaa c03adb00 (XEN) c03adb92 c03adb97 c03adba2 c03adc99 c03adcab c03adef7 c03adf5a c03adfc6 (XEN) c03adfe7 c03ae0dc c03ae0e6 c03ae0f0 c03ae10a c03ae114 c03ae154 c020a842 (XEN) c020be0f c020bf56 c0489e4b c048a12d c020d76c c020e04e c020ff99 c020ffa0 (XEN) mm.c:707:d50 Error getting mfn 3b5fb (pfn 5f9fb) from L1 entry 000000003b5fb061 for dom50 (XEN) traps.c:437:d50 Unhandled invalid opcode fault/trap [#6] on VCPU 0 [ec=0000] (XEN) domain_crash_sync called from entry.S (XEN) Domain 50 (vcpu#0) crashed on cpu#2: (XEN) ----[ Xen-3.3.0 x86_64 debug=n Not tainted ]---- (XEN) CPU: 2 (XEN) RIP: e019:[<00000000c0212033>] (XEN) RFLAGS: 0000000000000282 EM: 1 CONTEXT: pv guest (XEN) rax: 00000000ffffffea rbx: 00000000f56fb000 rcx: 000000003b5fb061 (XEN) rdx: 0000000000000000 rsi: 0000000000000006 rdi: 0000000000000000 (XEN) rbp: 000000000003b5fb rsp: 00000000c047df54 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: 00000003f2d5c000 cr2: 0000000000000000 (XEN) ds: e021 es: e021 fs: e021 gs: 0000 ss: e021 cs: e019 (XEN) Guest stack trace from esp=c047df54: (XEN) c0212033 0001e019 00010082 00000000 00000061 00000000 c020fd81 00104000 (XEN) f56fb000 00000000 000004ad 00000103 000012b4 c048afc6 00000061 80000000 (XEN) 004ad000 00000000 0061a027 00000000 00000000 c0445980 c0479640 c047dff4 (XEN) c048662f 00000000 0061f000 00000000 00000000 06040800 c0616000 00000000 (XEN) 00000000 06040800 c0616000 00000000 00000000 c04814fb c03b5000 c03f0102 (XEN) c0616000 06040800 00000000 c04813bc c04814c1 c04814c9 c04814d1 c0202408 (XEN) c020243b c02024dd c03a9bc8 c02027b4 c0202a79 c0202b4f c02032ef c0203818 (XEN) c0203c97 c0204331 c0204344 c0204368 c0204375 c02043f7 c02046d4 c0205134 (XEN) c0205203 c0205d42 c0205d87 c0205ddd c0206013 c02060c8 c02069b8 c0487768 (XEN) c0487770 c0207bf0 c0207bfe c0207c6e c0207c7c c0488973 c0488986 c02080e3 (XEN) c020816d c0208e42 c020903e c0209068 c0209070 c0209289 c0209290 c0209dd8 (XEN) c0209e5f c0209e6e c0209ea1 c0209eab c0209ee6 c0209eee c0209ef6 c03abf44 (XEN) c03ac0ea c03ac145 c03ac165 c03ac319 c03ac3d9 c03ac814 c0488c62 c0488c6a (XEN) c03acce5 c03acd47 c0488d8c c0488d94 c0488d9c c0488da4 c0488db2 c0488dba (XEN) c0488dc8 c0488dd0 c03ace21 c03ace8a c03ad00c c03ad026 c03ad078 c03ad0d7 (XEN) c03ad0dc c03ad301 c03ad374 c03ad37f c03ad38d c03ad416 c03ad428 c03ad517 (XEN) c03ad522 c03ad527 c03ad6a1 c03ad8ad c03ada60 c03ada99 c03adaaa c03adb00 (XEN) c03adb92 c03adb97 c03adba2 c03adc99 c03adcab c03adef7 c03adf5a c03adfc6 (XEN) c03adfe7 c03ae0dc c03ae0e6 c03ae0f0 c03ae10a c03ae114 c03ae154 c020a842 (XEN) c020be0f c020bf56 c0489e4b c048a12d c020d76c c020e04e c020ff99 c020ffa0 Andy _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jan Beulich
2008-Dec-01 09:07 UTC
Re: [Xen-devel] (XEN) mm.c:707:d49 Error getting mfn 2fef3 (pfn 6aef3)from L1 entry
That''s a kernel side bug in that a type incorrectness slipped in during the 2.6.27 merge. It''s already fixed in our local trees, and expected to make it into RC2). The only workaround I know of is to prevent Xen from using any memory above 4G (i.e. use mem=4G on the Xen command line). As to associating the register dump and call trace with the source - you''d want to disassemble vmlinux, associate the reported rIP with an address in the disassembly, and then work yourself up the stack and/or associate assembly code with source code. Jan>>> "Andrew Lyon" <andrew.lyon@gmail.com> 30.11.08 20:47 >>>Hi, Can anybody advise me how to debug this crash? it happens when I try to start a 32 bit kernel on my 64 bit Xen system, the kernel is my own using opensuse 11.1 rc1 2.6.27.7 xen patches, the kernel works as 32 and 64 bit dom0, and as 64 bit domU PV, is there a technique to find out where in the kernel source the crash happens? i.e what line in the source code? (XEN) mm.c:707:d49 Error getting mfn 2fef3 (pfn 6aef3) from L1 entry 000000002fef3061 for dom49 (XEN) traps.c:437:d49 Unhandled invalid opcode fault/trap [#6] on VCPU 0 [ec=0000] (XEN) domain_crash_sync called from entry.S (XEN) Domain 49 (vcpu#0) crashed on cpu#7: (XEN) ----[ Xen-3.3.0 x86_64 debug=n Not tainted ]---- (XEN) CPU: 7 (XEN) RIP: e019:[<00000000c0212033>] (XEN) RFLAGS: 0000000000000282 EM: 1 CONTEXT: pv guest (XEN) rax: 00000000ffffffea rbx: 00000000f56fb000 rcx: 000000002fef3061 (XEN) rdx: 0000000000000000 rsi: 0000000000000006 rdi: 0000000000000000 (XEN) rbp: 000000000002fef3 rsp: 00000000c047df54 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: 000000022feeb000 cr2: 0000000000000000 (XEN) ds: e021 es: e021 fs: e021 gs: 0000 ss: e021 cs: e019 (XEN) Guest stack trace from esp=c047df54: (XEN) c0212033 0001e019 00010082 00000000 00000061 00000000 c020fd81 00104000 (XEN) f56fb000 00000000 000004ad 00000103 000012b4 c048afc6 00000061 80000000 (XEN) 004ad000 00000000 0061a027 00000000 00000000 c0445980 c0479640 c047dff4 (XEN) c048662f 00000000 0061f000 00000000 00000000 03040800 c0616000 00000000 (XEN) 00000000 03040800 c0616000 00000000 00000000 c04814fb c03b5000 c03f0102 (XEN) c0616000 03040800 00000000 c04813bc c04814c1 c04814c9 c04814d1 c0202408 (XEN) c020243b c02024dd c03a9bc8 c02027b4 c0202a79 c0202b4f c02032ef c0203818 (XEN) c0203c97 c0204331 c0204344 c0204368 c0204375 c02043f7 c02046d4 c0205134 (XEN) c0205203 c0205d42 c0205d87 c0205ddd c0206013 c02060c8 c02069b8 c0487768 (XEN) c0487770 c0207bf0 c0207bfe c0207c6e c0207c7c c0488973 c0488986 c02080e3 (XEN) c020816d c0208e42 c020903e c0209068 c0209070 c0209289 c0209290 c0209dd8 (XEN) c0209e5f c0209e6e c0209ea1 c0209eab c0209ee6 c0209eee c0209ef6 c03abf44 (XEN) c03ac0ea c03ac145 c03ac165 c03ac319 c03ac3d9 c03ac814 c0488c62 c0488c6a (XEN) c03acce5 c03acd47 c0488d8c c0488d94 c0488d9c c0488da4 c0488db2 c0488dba (XEN) c0488dc8 c0488dd0 c03ace21 c03ace8a c03ad00c c03ad026 c03ad078 c03ad0d7 (XEN) c03ad0dc c03ad301 c03ad374 c03ad37f c03ad38d c03ad416 c03ad428 c03ad517 (XEN) c03ad522 c03ad527 c03ad6a1 c03ad8ad c03ada60 c03ada99 c03adaaa c03adb00 (XEN) c03adb92 c03adb97 c03adba2 c03adc99 c03adcab c03adef7 c03adf5a c03adfc6 (XEN) c03adfe7 c03ae0dc c03ae0e6 c03ae0f0 c03ae10a c03ae114 c03ae154 c020a842 (XEN) c020be0f c020bf56 c0489e4b c048a12d c020d76c c020e04e c020ff99 c020ffa0 (XEN) mm.c:707:d50 Error getting mfn 3b5fb (pfn 5f9fb) from L1 entry 000000003b5fb061 for dom50 (XEN) traps.c:437:d50 Unhandled invalid opcode fault/trap [#6] on VCPU 0 [ec=0000] (XEN) domain_crash_sync called from entry.S (XEN) Domain 50 (vcpu#0) crashed on cpu#2: (XEN) ----[ Xen-3.3.0 x86_64 debug=n Not tainted ]---- (XEN) CPU: 2 (XEN) RIP: e019:[<00000000c0212033>] (XEN) RFLAGS: 0000000000000282 EM: 1 CONTEXT: pv guest (XEN) rax: 00000000ffffffea rbx: 00000000f56fb000 rcx: 000000003b5fb061 (XEN) rdx: 0000000000000000 rsi: 0000000000000006 rdi: 0000000000000000 (XEN) rbp: 000000000003b5fb rsp: 00000000c047df54 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: 00000003f2d5c000 cr2: 0000000000000000 (XEN) ds: e021 es: e021 fs: e021 gs: 0000 ss: e021 cs: e019 (XEN) Guest stack trace from esp=c047df54: (XEN) c0212033 0001e019 00010082 00000000 00000061 00000000 c020fd81 00104000 (XEN) f56fb000 00000000 000004ad 00000103 000012b4 c048afc6 00000061 80000000 (XEN) 004ad000 00000000 0061a027 00000000 00000000 c0445980 c0479640 c047dff4 (XEN) c048662f 00000000 0061f000 00000000 00000000 06040800 c0616000 00000000 (XEN) 00000000 06040800 c0616000 00000000 00000000 c04814fb c03b5000 c03f0102 (XEN) c0616000 06040800 00000000 c04813bc c04814c1 c04814c9 c04814d1 c0202408 (XEN) c020243b c02024dd c03a9bc8 c02027b4 c0202a79 c0202b4f c02032ef c0203818 (XEN) c0203c97 c0204331 c0204344 c0204368 c0204375 c02043f7 c02046d4 c0205134 (XEN) c0205203 c0205d42 c0205d87 c0205ddd c0206013 c02060c8 c02069b8 c0487768 (XEN) c0487770 c0207bf0 c0207bfe c0207c6e c0207c7c c0488973 c0488986 c02080e3 (XEN) c020816d c0208e42 c020903e c0209068 c0209070 c0209289 c0209290 c0209dd8 (XEN) c0209e5f c0209e6e c0209ea1 c0209eab c0209ee6 c0209eee c0209ef6 c03abf44 (XEN) c03ac0ea c03ac145 c03ac165 c03ac319 c03ac3d9 c03ac814 c0488c62 c0488c6a (XEN) c03acce5 c03acd47 c0488d8c c0488d94 c0488d9c c0488da4 c0488db2 c0488dba (XEN) c0488dc8 c0488dd0 c03ace21 c03ace8a c03ad00c c03ad026 c03ad078 c03ad0d7 (XEN) c03ad0dc c03ad301 c03ad374 c03ad37f c03ad38d c03ad416 c03ad428 c03ad517 (XEN) c03ad522 c03ad527 c03ad6a1 c03ad8ad c03ada60 c03ada99 c03adaaa c03adb00 (XEN) c03adb92 c03adb97 c03adba2 c03adc99 c03adcab c03adef7 c03adf5a c03adfc6 (XEN) c03adfe7 c03ae0dc c03ae0e6 c03ae0f0 c03ae10a c03ae114 c03ae154 c020a842 (XEN) c020be0f c020bf56 c0489e4b c048a12d c020d76c c020e04e c020ff99 c020ffa0 Andy _______________________________________________ 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
Andrew Lyon
2008-Dec-01 16:59 UTC
Re: [Xen-devel] (XEN) mm.c:707:d49 Error getting mfn 2fef3 (pfn 6aef3)from L1 entry
On Mon, Dec 1, 2008 at 9:07 AM, Jan Beulich <jbeulich@novell.com> wrote:> That''s a kernel side bug in that a type incorrectness slipped in during the > 2.6.27 merge. It''s already fixed in our local trees, and expected to make > it into RC2). The only workaround I know of is to prevent Xen from using > any memory above 4G (i.e. use mem=4G on the Xen command line).Can you not post the patch/fix?> > As to associating the register dump and call trace with the source - you''d > want to disassemble vmlinux, associate the reported rIP with an address > in the disassembly, and then work yourself up the stack and/or associate > assembly code with source code. > > Jan > >>>> "Andrew Lyon" <andrew.lyon@gmail.com> 30.11.08 20:47 >>> > Hi, > > Can anybody advise me how to debug this crash? it happens when I try to start > a 32 bit kernel on my 64 bit Xen system, the kernel is my own using > opensuse 11.1 > rc1 2.6.27.7 xen patches, the kernel works as 32 and 64 bit dom0, and > as 64 bit domU PV, is there a technique to find out where in the > kernel > source the crash happens? i.e what line in the source code? > > (XEN) mm.c:707:d49 Error getting mfn 2fef3 (pfn 6aef3) from L1 entry > 000000002fef3061 for dom49 > (XEN) traps.c:437:d49 Unhandled invalid opcode fault/trap [#6] on VCPU > 0 [ec=0000] > (XEN) domain_crash_sync called from entry.S > (XEN) Domain 49 (vcpu#0) crashed on cpu#7: > (XEN) ----[ Xen-3.3.0 x86_64 debug=n Not tainted ]---- > (XEN) CPU: 7 > (XEN) RIP: e019:[<00000000c0212033>] > (XEN) RFLAGS: 0000000000000282 EM: 1 CONTEXT: pv guest > (XEN) rax: 00000000ffffffea rbx: 00000000f56fb000 rcx: 000000002fef3061 > (XEN) rdx: 0000000000000000 rsi: 0000000000000006 rdi: 0000000000000000 > (XEN) rbp: 000000000002fef3 rsp: 00000000c047df54 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: 000000022feeb000 cr2: 0000000000000000 > (XEN) ds: e021 es: e021 fs: e021 gs: 0000 ss: e021 cs: e019 > (XEN) Guest stack trace from esp=c047df54: > (XEN) c0212033 0001e019 00010082 00000000 00000061 00000000 c020fd81 00104000 > (XEN) f56fb000 00000000 000004ad 00000103 000012b4 c048afc6 00000061 80000000 > (XEN) 004ad000 00000000 0061a027 00000000 00000000 c0445980 c0479640 c047dff4 > (XEN) c048662f 00000000 0061f000 00000000 00000000 03040800 c0616000 00000000 > (XEN) 00000000 03040800 c0616000 00000000 00000000 c04814fb c03b5000 c03f0102 > (XEN) c0616000 03040800 00000000 c04813bc c04814c1 c04814c9 c04814d1 c0202408 > (XEN) c020243b c02024dd c03a9bc8 c02027b4 c0202a79 c0202b4f c02032ef c0203818 > (XEN) c0203c97 c0204331 c0204344 c0204368 c0204375 c02043f7 c02046d4 c0205134 > (XEN) c0205203 c0205d42 c0205d87 c0205ddd c0206013 c02060c8 c02069b8 c0487768 > (XEN) c0487770 c0207bf0 c0207bfe c0207c6e c0207c7c c0488973 c0488986 c02080e3 > (XEN) c020816d c0208e42 c020903e c0209068 c0209070 c0209289 c0209290 c0209dd8 > (XEN) c0209e5f c0209e6e c0209ea1 c0209eab c0209ee6 c0209eee c0209ef6 c03abf44 > (XEN) c03ac0ea c03ac145 c03ac165 c03ac319 c03ac3d9 c03ac814 c0488c62 c0488c6a > (XEN) c03acce5 c03acd47 c0488d8c c0488d94 c0488d9c c0488da4 c0488db2 c0488dba > (XEN) c0488dc8 c0488dd0 c03ace21 c03ace8a c03ad00c c03ad026 c03ad078 c03ad0d7 > (XEN) c03ad0dc c03ad301 c03ad374 c03ad37f c03ad38d c03ad416 c03ad428 c03ad517 > (XEN) c03ad522 c03ad527 c03ad6a1 c03ad8ad c03ada60 c03ada99 c03adaaa c03adb00 > (XEN) c03adb92 c03adb97 c03adba2 c03adc99 c03adcab c03adef7 c03adf5a c03adfc6 > (XEN) c03adfe7 c03ae0dc c03ae0e6 c03ae0f0 c03ae10a c03ae114 c03ae154 c020a842 > (XEN) c020be0f c020bf56 c0489e4b c048a12d c020d76c c020e04e c020ff99 c020ffa0 > (XEN) mm.c:707:d50 Error getting mfn 3b5fb (pfn 5f9fb) from L1 entry > 000000003b5fb061 for dom50 > (XEN) traps.c:437:d50 Unhandled invalid opcode fault/trap [#6] on VCPU > 0 [ec=0000] > (XEN) domain_crash_sync called from entry.S > (XEN) Domain 50 (vcpu#0) crashed on cpu#2: > (XEN) ----[ Xen-3.3.0 x86_64 debug=n Not tainted ]---- > (XEN) CPU: 2 > (XEN) RIP: e019:[<00000000c0212033>] > (XEN) RFLAGS: 0000000000000282 EM: 1 CONTEXT: pv guest > (XEN) rax: 00000000ffffffea rbx: 00000000f56fb000 rcx: 000000003b5fb061 > (XEN) rdx: 0000000000000000 rsi: 0000000000000006 rdi: 0000000000000000 > (XEN) rbp: 000000000003b5fb rsp: 00000000c047df54 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: 00000003f2d5c000 cr2: 0000000000000000 > (XEN) ds: e021 es: e021 fs: e021 gs: 0000 ss: e021 cs: e019 > (XEN) Guest stack trace from esp=c047df54: > (XEN) c0212033 0001e019 00010082 00000000 00000061 00000000 c020fd81 00104000 > (XEN) f56fb000 00000000 000004ad 00000103 000012b4 c048afc6 00000061 80000000 > (XEN) 004ad000 00000000 0061a027 00000000 00000000 c0445980 c0479640 c047dff4 > (XEN) c048662f 00000000 0061f000 00000000 00000000 06040800 c0616000 00000000 > (XEN) 00000000 06040800 c0616000 00000000 00000000 c04814fb c03b5000 c03f0102 > (XEN) c0616000 06040800 00000000 c04813bc c04814c1 c04814c9 c04814d1 c0202408 > (XEN) c020243b c02024dd c03a9bc8 c02027b4 c0202a79 c0202b4f c02032ef c0203818 > (XEN) c0203c97 c0204331 c0204344 c0204368 c0204375 c02043f7 c02046d4 c0205134 > (XEN) c0205203 c0205d42 c0205d87 c0205ddd c0206013 c02060c8 c02069b8 c0487768 > (XEN) c0487770 c0207bf0 c0207bfe c0207c6e c0207c7c c0488973 c0488986 c02080e3 > (XEN) c020816d c0208e42 c020903e c0209068 c0209070 c0209289 c0209290 c0209dd8 > (XEN) c0209e5f c0209e6e c0209ea1 c0209eab c0209ee6 c0209eee c0209ef6 c03abf44 > (XEN) c03ac0ea c03ac145 c03ac165 c03ac319 c03ac3d9 c03ac814 c0488c62 c0488c6a > (XEN) c03acce5 c03acd47 c0488d8c c0488d94 c0488d9c c0488da4 c0488db2 c0488dba > (XEN) c0488dc8 c0488dd0 c03ace21 c03ace8a c03ad00c c03ad026 c03ad078 c03ad0d7 > (XEN) c03ad0dc c03ad301 c03ad374 c03ad37f c03ad38d c03ad416 c03ad428 c03ad517 > (XEN) c03ad522 c03ad527 c03ad6a1 c03ad8ad c03ada60 c03ada99 c03adaaa c03adb00 > (XEN) c03adb92 c03adb97 c03adba2 c03adc99 c03adcab c03adef7 c03adf5a c03adfc6 > (XEN) c03adfe7 c03ae0dc c03ae0e6 c03ae0f0 c03ae10a c03ae114 c03ae154 c020a842 > (XEN) c020be0f c020bf56 c0489e4b c048a12d c020d76c c020e04e c020ff99 c020ffa0 > > Andy > > _______________________________________________ > 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
Apparently Analagous Threads
- Xen 3.2.1-rc1: ptwr_emulate: could not get_page_from_l1e()
- debian lenny domU installation
- latest pv_ops dom0 (2.6.29-rc6) crashes / unhandled page fault
- 2.6.26-rc8 pv_ops causes Unhandled invalid opcode fault/trap
- Loading FreeBSD in an HVM-domain on Intel-based host with GRUB