On 5/23/11 4:04 AM, Manuel Bouyer wrote:
On Fri, May 20, 2011 at 02:55:38PM -0700, Jeff Rizzo wrote:
Things sort-of look ok; but when I try to use 'xm' to start my domU,
it *seems* to work, but the domain isn't running - and when I check
xend.log, it seems to have crashed:
xenserver1# xm create -c boogers
Using config file "/usr/pkg/etc/xen/boogers".
Started domain boogers (id=3)
xenserver1# xm list
Name ID Mem VCPUs
State Time(s)
Domain-0 0 256 1
r----- 39.7
xenserver1#
From xend.log:
[2011-05-20 14:52:35 303] INFO (XendDomain:1225) Domain boogers (3)
unpaused.
[2011-05-20 14:52:35 303] WARNING (XendDomainInfo:2061) Domain has
crashed: name
=boogers id=3.
[2011-05-20 14:52:35 303] ERROR (XendDomainInfo:2195) VM boogers
restarting too
fast (Elapsed time: 0.790479 seconds). Refusing to restart to avoid
loops.
...any ideas?
Anything in 'xm dmesg' ? Maybe use a xen-debug kernel, to have more
details about the guest crash
xm dmesg gives something which might be useful in the right hands (ie,
not mine):
(XEN) traps.c:451:d3 Unhandled bkpt fault/trap [#3] on VCPU 0 [ec=0000]
(XEN) domain_crash_sync called from entry.S
(XEN) Domain 3 (vcpu#0) crashed on cpu#3:
(XEN) ----[ Xen-4.1.0 x86_64 debug=n Not tainted ]----
(XEN) CPU: 3
(XEN) RIP: e019:[<00000000c03b7d8c>]
(XEN) RFLAGS: 0000000000000286 EM: 1 CONTEXT: pv guest
(XEN) rax: 0000000000000001 rbx: 0000000000000002 rcx: 000000000000000a
(XEN) rdx: 00000000c0662000 rsi: 0000000000000000 rdi: 0000000000000000
(XEN) rbp: 00000000c0660b3c rsp: 00000000c0660b30 r8: 0000000000000000
(XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000
(XEN) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000000
(XEN) r15: 0000000000000000 cr0: 000000008005003b cr4: 00000000000026f0
(XEN) cr3: 000000023f500000 cr2: 0000000000000000
(XEN) ds: e021 es: e021 fs: 0000 gs: 0000 ss: e021 cs: e019
(XEN) Guest stack trace from esp=c0660b30:
(XEN) c03b7d8c 0001e019 00000086 c0660b4c c03b99c5 c0660b58 00000006
c0660b8c
(XEN) c031d707 c0455401 c0660b98 c047be00 c031e693 00000006 00000005
00000000
(XEN) 00000000 c0660ba8 c0660b98 00000000 00000000 00000000 00000104
c0660bbc
(XEN) c03cd4f7 c0461f5a 29f51308 00000002 29f4d001 00000002 bfdff018
29f4d001
(XEN) 00000000 00000001 00000002 c0660bfc c03c1619 29f51308 00000002
29f4d001
(XEN) 00000002 00661000 00000000 29f4d001 00000002 00661000 00000000
29f4d063
(XEN) 00000002 00661000 00000002 c0660c5c c03c14f2 bfe03308 29f4d001
00000002
(XEN) 00000000 00000000 00000000 00000000 00000000 00661000 00000000
00000000
(XEN) 00000000 00000000 bfe03308 00000000 00000000 29f4d001 00000002
00000000
(XEN) 00000000 1fa9e000 00000000 c0660ccc c03bdc43 c0661000 00661000
00000000
(XEN) 00000001 00000001 00000001 00000001 35692029 3034322d 50432030
00229f4d
(XEN) 30312e33 007a4847 76035a01 00f0b0ff 00000000 00ca0000 00000000
ffffffff
(XEN) c0660bb0 00000004 00000000 06100800 00000000 00000000 756e6547
c0660d3c
(XEN) c03be2a6 00000000 00000000 00000000 00000000 00000000 00000000
00000000
(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
(XEN) 00000000 00662000 00000000 00000000 00000000 00000000 00000000
00000000
(XEN) 756e6547 00661000 c04f2200 00000000 c0100063 00661000 00000000
00000000
(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
... do I perhaps need a newer domU kernel or something for Xen4.1?
+j