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. Xen: #17501 & Xen0: #524 -- two new i

To: "Li, Haicheng" <haicheng.li@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] VMX status report. Xen: #17501 & Xen0: #524 -- two new issues
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Wed, 23 Apr 2008 13:18:42 +0100
Cc: Kevin Wolf <kwolf@xxxxxxx>
Delivery-date: Wed, 23 Apr 2008 05:19:48 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <FC1D1B23302A22499C60C967336B2AE002B0E6AD@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: AcilKK2Z9ZBbRqIESv6ia56nvm3K+AAE32DD
Thread-topic: [Xen-devel] VMX status report. Xen: #17501 & Xen0: #524 -- two new issues
User-agent: Microsoft-Entourage/11.4.0.080122
On 23/4/08 10:59, "Li, Haicheng" <haicheng.li@xxxxxxxxx> wrote:

> 1. Fail to create any HVM guest on IA32PAE host
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1221

Looks like it is due to Kevin Wolf's changeset 17499. Your attempt to go
back to older tools obviously didn't work -- the backtrace in xend.log comes
from a line introduced by c/s 17499.

> 2. Dom0 hangs at booting if loglvl and guest_loglvl are set as all.
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1222

Well, the obvious answer is to print less drivel in the VT-d code. There's
no reason at all to print so much useless text, even in a debug build.

Actually a second point is that we should drop characters from the 16kB
serial buffer rather than spin in the hypervisor waiting for the buffer to
empty. I'll implement that.

 -- Keir



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