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] vmx status report against cset 15072 - one blocker issue

To: "Steven Hand" <Steven.Hand@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] vmx status report against cset 15072 - one blocker issue
From: "Zhao, Yunfeng" <yunfeng.zhao@xxxxxxxxx>
Date: Thu, 17 May 2007 09:22:01 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 16 May 2007 18:20:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <E1HoLBp-0004Sh-00@xxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AceXzMHch1XhRjU5RieaIjkMmJIJBwAVM8kg
Thread-topic: [Xen-devel] vmx status report against cset 15072 - one blocker issue
I can reproduce when boot a HVM Linux guest with 1GB mem, vcpu=2, acpi=1, 
apic=1 and sdl=1.

Thanks
Yunfeng

>-----Original Message-----
>From: Steven Hand [mailto:Steven.Hand@xxxxxxxxxxxx]
>Sent: 2007年5月16日 23:13
>To: Zhao, Yunfeng
>Cc: xen-devel@xxxxxxxxxxxxxxxxxxx; Steven.Hand@xxxxxxxxxxxx
>Subject: Re: [Xen-devel] vmx status report against cset 15072 - one blocker 
>issue
>
>
>>Today's testing is blocked by the issue below:
>>xen0 hang when destroy VMX guest
>>http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=3D981
>
>I can't reproduce this even vaguely in 15077 (and I can't see anything
>that would have fixed it).
>
>Might be related to the fact that you're using a non-debug build while
>I'm not :^/
>
>Your bugzilla suggests that you get a 'white window' from qemu - this
>typically means that the guest is alive but quite screwed - can you
>say some more about what guest and guest configuration you were using?
>
>
>cheers,
>
>S.

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