WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: Xen bug or VMware bug?

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: [Xen-devel] Re: Xen bug or VMware bug?
From: "Kip Macy" <kip.macy@xxxxxxxxx>
Date: Wed, 26 Dec 2007 12:19:54 -0800
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 26 Dec 2007 12:20:17 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=1uu6bQHVfZu39KEHjMx8cTY8ImCGRXaD/na8kTFc6So=; b=uk8F7GC1EvRzKxj+03m1rkRy18QMCSWWv1stdVRbQ8PwpCRIsk+b5FSsuXVK8UWW3f9x6evYUweOm6l9o/4+b4nlSgafuu7ArzHyLsXLcqYszVHU/8fc0Vzj4V6ZTs8W6RSXssOD2yPWq6DKPniCB3nGyC4Lg20FNrvtaVr85l8=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=mWhYrRAaJo0qZkZAB74A8cttiECgGD1ZNL07jqIOO8Y1Pqbib/a8wPDyKc38JHOpIy2SlcRk63qn+moAn8yQiU0adAiY07pksYqd5BV/aODczA3y9TecSfsA1tEvpqpLxdA4ztDsHPl9hat/BbAi5A1p8/86hNUPRSHlFeTUYKU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C397FB88.1184C%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: <b1fa29170712250216r340616dan7224d02833e7f422@xxxxxxxxxxxxxx> <C397FB88.1184C%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Dec 26, 2007 4:37 AM, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:
> On 25/12/07 10:16, "Kip Macy" <kip.macy@xxxxxxxxx> wrote:
>
> > Correct. Just start it up on a PAE xen.
> >
> > As it turns out *any* in-place updates to the L3 - even putting a zero
> > where there is currently a zero - will cause a system reset. At least
> > on VMWare Fusion. I've worked around it for the moment by allocatng a
> > new L3 and then switching to that.
>
> I can't reproduce this with xen-3.1-testing.hg c/s 15547 on real hardware.
> Although the domain does crash in a fairly intricate and interesting way.
> I've appended the Xen logging of the domain crash. I assume your 'whole
> machine' crash is simply inaccurate emulation of native behaviour by VMware
> Fusion.

Excellent, I'm glad to hear that it is a VMWare Fusion bug (as opposed
to an easily triggered Xen bug). PAE isn't expected to work just yet,
so *a* crash is expected.


Thanks.

    -Kip



>
>  -- Keir
>
> #8, proc0kstack=3227074560
> xen_setbootenv(): cmd_line='root=/dev/hda1 ro 4'
> gdt=0xc0596000
> PTmap=0xbf800000
> (XEN) Unhandled page fault in domain 1 on VCPU 0 (ec=0000)
> (XEN) Pagetable walk from bfe02cb4:
> (XEN)  L3[0x002] = 00000000aec46001 0000059c
> (XEN)  L2[0x1ff] = 0000000000000000 ffffffff
> (XEN) domain_crash_sync called from entry.S (ff17f5a2)
> (XEN) Domain 1 (vcpu#0) crashed on cpu#3:
> (XEN) ----[ Xen-3.1.3-rc1-devel  x86_32p  debug=y  Not tainted ]----
> (XEN) CPU:    3
> (XEN) EIP:    e019:[<c040a7e7>]
> (XEN) EFLAGS: 00000206   CONTEXT: guest
> (XEN) eax: 000c0596   ebx: 00000098   ecx: deadbeef   edx: deadbeef
> (XEN) esi: c04f2184   edi: 00000000   ebp: c0595d84   esp: c0595bf4
> (XEN) cr0: 8005003b   cr4: 000026f0   cr3: 00260d20   cr2: bfe02cb4
> (XEN) ds: e021   es: e021   fs: e021   gs: e021   ss: e021   cs: e019
> (XEN) Guest stack trace from esp=c0595bf4:
> (XEN)    00000000 c040a7e7 0001e019 00010006 c0492b92 bf800000 00000000
> 00000001
> (XEN)    00000000 00000000 00000001 00000000 00000000 00000000 00000000
> 00000000
> (XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000
> 00000000
> (XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000
> 00000000
>
>
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel