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] Re: [Xen-staging] [xen-3.1-testing] xend: Fix use ofPIFI

To: "Krysan, Susan" <KRYSANS@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [Xen-staging] [xen-3.1-testing] xend: Fix use ofPIFIsPhysical (takes no arguments).
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Thu, 03 May 2007 21:29:43 +0100
Cc: Pascal Bouchareine <pascal@xxxxxxxxx>, Tom Wilkie <tom.wilkie@xxxxxxxxx>, Alex Williamson <alex.williamson@xxxxxx>
Delivery-date: Thu, 03 May 2007 13:26:35 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <EF8D308BE33AF54D8934DF26520252D30350486A@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: AceNp8ls9QZ4AT1/Roa+SZRPlkf/PAAEAOdgAAAFxFAAAnkF6A==
Thread-topic: [Xen-devel] Re: [Xen-staging] [xen-3.1-testing] xend: Fix use ofPIFIsPhysical (takes no arguments).
User-agent: Microsoft-Entourage/
On 3/5/07 20:25, "Krysan, Susan" <KRYSANS@xxxxxxxxxx> wrote:

> I am running on a Unisys ES7000 with changeset 15006, and I still see
> this problem.  I believe it only happens when I stop the server,
> reconfigure the amount of host processors and RAM, and then reboot.

Xen-unstable c/s 15006, I assume?

In that case your xend hasn't been properly re-installed: line 208 in your
Python backtrace changed from pif.destroy() to XendBase.destroy() in
changeset 15000. That was the fix for this bug. :-)

 -- Keir

Xen-devel mailing list

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