All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karl Rister <kmr@us.ibm.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: hvm domain crash
Date: Thu, 21 Sep 2006 16:56:27 -0500	[thread overview]
Message-ID: <200609211656.28500.kmr@us.ibm.com> (raw)

While running dbench inside an hvm domain I received the following on the 
console:

(XEN) Invalid CR3 value=10f780000domain_crash_sync called from vmx.c:1679
(XEN) Domain 5 (vcpu#1) crashed on cpu#4:
(XEN) ----[ Xen-3.0-unstable  x86_64  debug=n  Not tainted ]----
(XEN) CPU:    4
(XEN) RIP:    0010:[<ffffffff8017680c>]
(XEN) RFLAGS: 0000000000000293   CONTEXT: hvm
(XEN) rax: 000000010f780000   rbx: 0000000000000001   rcx: 0000000000000000
(XEN) rdx: ffff81010f780000   rsi: 0000000000000000   rdi: ffff81010fc6db5c
(XEN) rbp: ffffffff803f3000   rsp: ffff81010fc6fb48   r8:  0000000000000000
(XEN) r9:  0000000000000000   r10: 0000000000000000   r11: 0000000000000000
(XEN) r12: ffff81010fb39a80   r13: 0000000000000000   r14: ffff81010fc6d510
(XEN) r15: ffff81010fc66ac0   cr0: 000000008005003b   cr4: 00000000000006e0
(XEN) cr3: 000000015f4c1000   cr2: 0000000000000000
(XEN) ds: 0018   es: 0018   fs: 0000   gs: 0000   ss: 0018   cs: 0010

The domain was running with 4 VCPUs and had previously completed the test on a 
single VCPU and 2 VCPU configurations.  The domain was running a baremetal 
2.6.16.29 kernel.  Output from 'xm info' is:

host                   : x460c
release                : 2.6.16.29-xen0-up
version                : #1 Tue Sep 19 16:20:47 CDT 2006
machine                : x86_64
nr_cpus                : 16
nr_nodes               : 1
sockets_per_node       : 4
cores_per_socket       : 2
threads_per_core       : 2
cpu_mhz                : 3002
hw_caps                : 
bfebfbff:20100800:00000000:00000180:000065bd:00000000:00000001
total_memory           : 14335
free_memory            : 13633
xen_major              : 3
xen_minor              : 0
xen_extra              : -unstable
xen_caps               : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p 
hvm-3.0-x86_64
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : Tue Sep 19 08:26:47 2006 +0100 11536:041be3f6b38e
cc_compiler            : gcc version 4.1.0 (SUSE Linux)
cc_compile_by          : root
cc_compile_domain      : ltc.austin.ibm.com
cc_compile_date        : Tue Sep 19 16:15:52 CDT 2006
xend_config_format     : 2


-- 
Karl Rister
IBM Linux Performance Team
kmr@us.ibm.com

             reply	other threads:[~2006-09-21 21:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-21 21:56 Karl Rister [this message]
2006-09-21 21:55 ` hvm domain crash Keir Fraser
2006-09-22 14:04   ` Karl Rister
2006-09-25 22:19   ` Karl Rister
2006-09-25 22:35     ` Ian Pratt
2006-09-26 20:36       ` Karl Rister
2006-09-26 20:48         ` Ian Pratt
2006-09-26 21:10           ` Karl Rister

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200609211656.28500.kmr@us.ibm.com \
    --to=kmr@us.ibm.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.