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

To: Stefan Berger <stefanb@xxxxxxxxxx>
Subject: Re: [Xen-devel] sHype changeset causes error in domU creation
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Thu, 23 Jun 2005 10:48:12 +0100
Cc: George Washington Dunlap III <dunlapg@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Steven Hand <Steven.Hand@xxxxxxxxxxxx>, Reiner Sailer <sailer@xxxxxxxxxx>
Delivery-date: Thu, 23 Jun 2005 09:43:13 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <OF700194E9.2EE90EC8-ON85257029.001036A4-85257029.00109DE0@xxxxxxxxxx>
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>
References: <OF700194E9.2EE90EC8-ON85257029.001036A4-85257029.00109DE0@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 23 Jun 2005, at 04:01, Stefan Berger wrote:

This is a problem that comes with an FC 4 install and the newer python
that comes along with it.
Below a patch that solves the problem. ( default=~0 would also work )

Signed-off-by: Stefan Berger <stefanb@xxxxxxxxxx>

Steve applied this patch, but I'd strongly argue for 0 as the default ssid value. I don't know if this this is a hard change to make?

As an aside, I also don't like the name of the policy hypercall and policy control tools. Can we call them 'acm_policy' or 'security_policy' or something like that? Calling them 'policy' with no further qualification is too vague.

 Cheers,
 Keir


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