On Wed, Feb 20, 2008 at 08:07:17AM -0700, John R. Shannon wrote:
What does the following mean?
(XEN) domain_crash_sync called from entry.S (ff1664ae)
(XEN) Domain 2 (vcpu#0) crashed on cpu#1:
(XEN) ----[ Xen-3.1.3 x86_32 debug=n Not tainted ]----
(XEN) CPU: 1
(XEN) EIP: 0009:[<c03e0e70>]
(XEN) EFLAGS: 00010282 CONTEXT: guest
(XEN) eax: 00000006 ebx: c0a3cb00 ecx: ccf5105e edx: cce04002
(XEN) esi: 000005ea edi: 00000000 ebp: ccf51010 esp: ccf50fe0
(XEN) cr0: 8005003b cr4: 000006d0 cr3: 95472000 cr2: ccf50ff4
(XEN) ds: 0011 es: 0011 fs: 0031 gs: 0011 ss: 0011 cs: 0009
(XEN) Guest stack trace from esp=ccf50fe0:
(XEN) Fault while accessing guest memory.
4.99.54 (yesterday) dom0
4.0-PATCH guest
Could be interesting to see to what function 0xc03e0e70 points to in the
guest's kernel. But at this point, the stack pointer is completely off
(it looks like it's in Xen's private VM space). Does this happens at boot,
or was the domU already running ?