This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] hvm domain crash

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] hvm domain crash
From: Karl Rister <kmr@xxxxxxxxxx>
Date: Fri, 22 Sep 2006 09:04:04 -0500
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 22 Sep 2006 07:05:14 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C138C8EE.1780%Keir.Fraser@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C138C8EE.1780%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.3
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.


>  -- Keir
> On 21/9/06 10:56 pm, "Karl Rister" <kmr@xxxxxxxxxx> 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 kernel.  Output from 'xm info' is:

Karl Rister
IBM Linux Performance Team

Xen-devel mailing list