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] Test report for Xen-3.3.0-rc4 (#18314)

To: "Xu, Jiajun" <jiajun.xu@xxxxxxxxx>, "Li, Haicheng" <haicheng.li@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Test report for Xen-3.3.0-rc4 (#18314)
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Wed, 13 Aug 2008 10:48:38 +0100
Cc:
Delivery-date: Wed, 13 Aug 2008 02:49:04 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <DB3BD37E3533EE46BED2FBA80995557F019D03DA@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/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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acj9GE3rwozhsAPLQzWzjoCOtOVTDgABplJuAAGfavAAARduSg==
Thread-topic: [Xen-devel] Test report for Xen-3.3.0-rc4 (#18314)
User-agent: Microsoft-Entourage/11.4.0.080122
On 13/8/08 10:32, "Xu, Jiajun" <jiajun.xu@xxxxxxxxx> wrote:

> 1. Indiana HVM may reboot when loading grub, serial grub shows:
> (XEN) sh error: sh_remove_shadows(): can't find all shadows of mfn
> 1e4490 (shadow_flags=00000040)

At least it's not a hv crash. At this late stage I could perhaps live with
this.

> 2. "xm destroy" Indiana HVM may cause xen call trace. But there is no
> xen crash.

Both backtraces are from 3.3.0-rc1. You modified and tested the wrong tree.
:-) This second backtrace can no longer happen.

We're going to dig into the OOS bug a bit and decide what to do...

 -- Keir



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