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

Re: [Xen-devel] Re: VM Entry fails in changesets since 19095

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: VM Entry fails in changesets since 19095
From: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>
Date: Wed, 28 Jan 2009 12:23:28 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 28 Jan 2009 04:25:10 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=jm7LzGmF737zYaChwvErDiqnl5cNmg1nODDH0NnEIgU=; b=sytG41et/5T0sQSNs3TDqcKjPTZ6nXUYG2o8+O2AESiCadbBHFxsOsrXg/Mgs74Ubo 7NKocTFbASmb4gh930IFxveptYAFEevypKqLiDVOFnJcYOVIvkliviUlo/OvkfKqrFh1 +GeEkrtTyMugzbR5FGGrGxN43Y+Ly6g6yMXBQ=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=Gamcb6Npuf7NzapZZVlRG4eH1vWt5l73AEAEFOHe7kVo6ysI+0SCYyf4H0P0uLcLnH +BaoikE0kH2hUTrj9lVImKhHe2pNJHChDnSUvdwmqu2MDzmCRERYuFPdsEP9nchLThGp OurL9I/StcDooOuDGLJJ/TVXIDoRxgLUQIJko=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C5A5F622.1DE8%keir.fraser@xxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <de76405a0901280305x15e635f3x2d38f045c5821e40@xxxxxxxxxxxxxx> <C5A5F622.1DE8%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I just did a "make mrproper" and re-built.  Still crashes.

I assume the automated test suites include a test with a 32-bit dom0
and a 64-bit hypervisor (which is my configuration)?

I narrowed it down to cs 18090.  With build of 18090 (plus a backport
of 18095 so that dom0 boots) the domain will crash, but with a build
of 18089 (plus a backport of 18095 for good measure) the domain will
boot fine.

Going to dig a little deeper...

 -George

On Wed, Jan 28, 2009 at 11:46 AM, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> wrote:
> It's going to be a slightly subtle one since it works for and for our
> automated tests. It would be worth making sure you've done a 'make clean' in
> the xen directory -- I recently changed the dependency system, and I'm still
> not 100% sure of it yet. I actually got a broken image myself somehow, which
> was fixed by 'make clean', but I haven't tracked down the issue as yet.
>
>  -- Keir
>
> On 28/01/2009 11:05, "George Dunlap" <George.Dunlap@xxxxxxxxxxxxx> wrote:
>
>> I started to work on the fix for the PoD, only to discover that just
>> starting a normal HVM on recent -unstable build (no PoD enabled), the
>> domain crashes with invalid guest state.
>>
>> I did a binary search, and found that the change which breaks things
>> was introduced sometime between CS 19089 and 19095
>>
>> I'm still looking into it, but if anyone else has any ideas, they'd be
>> appreciated.
>>
>> I'm attaching a console log and cpuinfo.  The chip is an older one, a
>> dual-core Intel Conroe.
>>
>>  -George
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>

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

<Prev in Thread] Current Thread [Next in Thread>