Re: [Xen-devel] VMX status report. Xen: #17304 & Xen0: #496 -- n

To:	"Li, Haicheng" <haicheng.li@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	Re: [Xen-devel] VMX status report. Xen: #17304 & Xen0: #496 -- no new issue
From:	Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date:	Mon, 31 Mar 2008 10:18:32 +0100
Delivery-date:	Mon, 31 Mar 2008 02:19:50 -0700
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
In-reply-to:	<FC1D1B23302A22499C60C967336B2AE002952181@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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:	AciQpKWD0nUpLcYoQJO5vdBPtedtsQAAGYrCAARoKiAACWpq/QCJQougAAD5LxsAAFt/IAACX16s
Thread-topic:	[Xen-devel] VMX status report. Xen: #17304 & Xen0: #496 -- no new issue
User-agent:	Microsoft-Entourage/11.4.0.080122

On 31/3/08 09:57, "Li, Haicheng" <haicheng.li@xxxxxxxxx> wrote:

>> How early during boot does it crash? If it's early perhaps I can
>> repro if you send me the vmlinux file, or attach it to the bug, or
>> otherwise make it available for download?
> 
> Since it is too large to be added to bugzilla, vmlinux is attached here.
> It crashes very early in booting, just after uncompressing kernel.

It's rather big for a ML posting too. It looks like the list server ate the
whole email, which is probably just as well. I received the attachment to my
own email address okay though, and I'll try it out shortly.

 -- Keir



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

WARNING - OLD ARCHIVES

xen-devel

Re: [Xen-devel] VMX status report. Xen: #17304 & Xen0: #496 -- no new is