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/
Home Products Support Community News


Re: [Xen-devel] New release candidate for Xen 4.0.0 (RC9)

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] New release candidate for Xen 4.0.0 (RC9)
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Wed, 31 Mar 2010 21:07:31 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 31 Mar 2010 13:14:09 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100331195223.GA15322@xxxxxxxxxxxxxxxxxxx>
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: AcrRC8GcuHXNe6saT4yosh4JAUMx6wAAgm9N
Thread-topic: [Xen-devel] New release candidate for Xen 4.0.0 (RC9)
User-agent: Microsoft-Entourage/
On 31/03/2010 20:52, "Konrad Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx> wrote:

>>> I don't have a fix, but I did this (this is with xen/stable-2.6.32.x
>>> latest and also rolled back to git commit
>>> 47bd9cad11b1a723c6e5d1127aebe570a3e34f34
>>> with a cherry pick of d3b9e35a81e31ff4edb4666f9c36eb5b2032f4da - just in
>>> case
>>> the problem was due to the PAT changes):
>> Is it a regression?
> I haven't tried this type of operation before so I can't comment. I can
> spin out a Xen hypervisor - what version back do you want me to compare
> to?

Last stable release (3.4.2). Or even 3.4-testing tip.

I'm only interested in fixing regressions right now for 4.0.0. If this bug
has existed since at least 3.4 then the fix (when we have one!) can wait a
bit longer, for 4.0.1. My guess is that the MTRR interface is getting little
use and rotted some time ago.

 -- Keir

> Interestingly, on Intel it makes the machine crawl and gets CPU#0 stuck,
> while on AMD I get that nice crash.

Xen-devel mailing list