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] sHype changeset causes error in domU creation

To: Steven Hand <Steven.Hand@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] sHype changeset causes error in domU creation
From: Steven Hand <Steven.Hand@xxxxxxxxxxxx>
Date: Thu, 23 Jun 2005 10:40:17 +0100
Cc: George Washington Dunlap III <dunlapg@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 23 Jun 2005 09:39:42 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: Your message of "Thu, 23 Jun 2005 00:35:59 BST." <E1DlElD-0005Fw-00@xxxxxxxxxxxxxxxxx>
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
> >Changing the following line makes a temporary fix:
> Well not really a fix so much as a "make the exception go away" :-) 
> I'll take a look tomorrow at the best way to fix this - may be that
> Keir's suggestion of using 0 as the 'null' ssidref is correct, although
> zero currently has another meaning... 

I've checked in a [potential] fix for now, but since I don't have a 
python 2.4 install handy it'd be great if you could test it. 

Longer term (next week?) we should probably think more about whether
we can move to a '0' default (or at least 'null') ssidref.



Xen-devel mailing list