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] Biweekly VMX status report. Xen: 22653 & Dom0:862ef9719

To: Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: RE: [Xen-devel] Biweekly VMX status report. Xen: 22653 & Dom0:862ef9719
From: "Zhang, Yang Z" <yang.z.zhang@xxxxxxxxx>
Date: Tue, 11 Jan 2011 09:00:58 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 10 Jan 2011 17:02:46 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4D2AE150020000780002B4EE@xxxxxxxxxxxxxxxxxx>
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: <749B9D3DBF0F054390025D9EAFF47F2231A9F838@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4D2AE150020000780002B4EE@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcuwqfYXX+bzmpTOS1+KX55UDrcYYgAgOrxQ
Thread-topic: [Xen-devel] Biweekly VMX status report. Xen: 22653 & Dom0:862ef9719
Ok, I will try 22683 to see whether it will fix this issue.

best regards
yang

> -----Original Message-----
> From: Jan Beulich [mailto:JBeulich@xxxxxxxxxx]
> Sent: Monday, January 10, 2011 5:37 PM
> To: Zhang, Yang Z
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] Biweekly VMX status report. Xen: 22653 &
> Dom0:862ef9719
> 
> >>> On 10.01.11 at 06:23, "Zhang, Yang Z" <yang.z.zhang@xxxxxxxxx> wrote:
> > 3. Xen panic with x2apic enabled
> > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1702
> 
> This very likely requires debugging on the particular system - from
> the log, an L2 page table entry of compatibility m2p table's gets
> overwritten with "Interrup", which I don't think has been seen
> anywhere else. A slight possibility exists that this is fixed by
> 22683:533d6e5c0099.
> 
> Jan


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

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