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] Xen 4.0 crashes with pvops kernel

To: Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] Xen 4.0 crashes with pvops kernel
From: Cris Daniluk <cris.daniluk@xxxxxxxxx>
Date: Tue, 15 Jun 2010 11:01:51 -0400
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 15 Jun 2010 08:05:32 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=Vx0dWXzex2OFweRKsA1vmO2w2mo/wm9Mw4f81Iqj9Ik=; b=xHukAgCtzf9IpGLNnWWxH7p2jj1L4aHFeTnb0QEppKDFEEHs/VtGXgP0qand5bTXJ0 ACqOYoIOW3MC4Qd5FJp5WV4lZAzMHJcGN/xTNhxBgeukAf7QVceyLL3cu4eTH/FJKCk9 QZcKzi0KneVO18TfoMeRoHxqCNFP/7cTQDqgU=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=xp7ZMAFMDiGthuTmR3iyzz4XareH8ecxRC0rPhc6lpPNYnlt4cRO8kAW7WBzv9cloU RxJgRdN/Z4ASXDIFNcFPx/xMdgXGW8oQQn7rWbax3so4VwxqhB56M1H2kO856r2HG0BM NlBkLP2Xojjjc0hvoQV95qKBLOGV5v5z7j0nE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C17B15002000078000068D5@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: <4C17932F0200007800006821@xxxxxxxxxxxxxxxxxx> <C83D3707.178AF%keir.fraser@xxxxxxxxxxxxx> <4C179A47020000780000683A@xxxxxxxxxxxxxxxxxx> <AANLkTikq_pyi7ud-fRXCIN-p0JaheyXrbbBe65ctoNA4@xxxxxxxxxxxxxx> <4C179FBC020000780000685D@xxxxxxxxxxxxxxxxxx> <AANLkTinzH8yDGFREonrJwAn3A9SYYhC_1u_543tbsXWz@xxxxxxxxxxxxxx> <4C17A6B002000078000068A3@xxxxxxxxxxxxxxxxxx> <AANLkTikyc72h0CKY-KxHbXZXKG4tNdHGPRPHfk6MYiy4@xxxxxxxxxxxxxx> <4C17B15002000078000068D5@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, Jun 15, 2010 at 10:58 AM, Jan Beulich <JBeulich@xxxxxxxxxx> wrote:
>>>> On 15.06.10 at 16:35, Cris Daniluk <cris.daniluk@xxxxxxxxx> wrote:
>> Hmm, so could there be a Xen-based workaround in the interim, such as
>> bypassing the code page that is triggering this? It seems like that
>> may not provide too much relief given the nature of the issue.
>
> Unfortunately I can't think of anything.
>
> Jan
>

Fair enough. I will see if I can get some other hardware to test with.
What would the path toward resolution be here? It still seems like Xen
shouldn't be writing into that page, let alone reading..

Cris

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

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