From: Karl Rister <kmr@us.ibm.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: hvm domain crash
Date: Fri, 22 Sep 2006 09:04:04 -0500 [thread overview]
Message-ID: <200609220904.04399.kmr@us.ibm.com> (raw)
In-Reply-To: <C138C8EE.1780%Keir.Fraser@cl.cam.ac.uk>
On Thursday 21 September 2006 4:55 pm, Keir Fraser wrote:
> That's quite a big CR3 value. How much memory does this guest have?
The guest was configured with 2GB of memory. In these particular tests we are
scaling up the VCPU count and as we do that we add memory as well. The 1way
test used 512MB and the 2way used 1GB.
Once I was able to recover my environment from this crash I discovered that
the problem is not occurring during the test run but during launch of the
domain. I find this curious because before I launched the tests I
successfully booted and then cleanly shutdown the hvm domain with 1, 2, 4, 8,
and 16 VCPUs. However, I did not scale the memory in that small functional
test. I am going to investigate and see if I can more clearly define that
the amount of memory is the issue and what the breaking point is.
Karl
>
> -- Keir
>
> On 21/9/06 10:56 pm, "Karl Rister" <kmr@us.ibm.com> wrote:
> > (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:
--
Karl Rister
IBM Linux Performance Team
kmr@us.ibm.com
next prev parent reply other threads:[~2006-09-22 14:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 21:56 hvm domain crash Karl Rister
2006-09-21 21:55 ` Keir Fraser
2006-09-22 14:04 ` Karl Rister [this message]
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=200609220904.04399.kmr@us.ibm.com \
--to=kmr@us.ibm.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--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.