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: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] sHype changeset causes error in domU creation
From: Reiner Sailer <sailer@xxxxxxxxxx>
Date: Wed, 22 Jun 2005 20:42:40 -0400
Cc: George Washington Dunlap III <dunlapg@xxxxxxxxx>, Xen Mailing List <xen-devel@xxxxxxxxxxxxxxxxxxx>, stefanb@xxxxxxxxxx, sailer@xxxxxxxxxxxxxx
Delivery-date: Thu, 23 Jun 2005 00:41:44 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <5adcfcb1ac293d290776846909064241@xxxxxxxxxxxx>
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
Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote on 06/22/2005 01:09:09 PM:

> Having ssidref as a required parameter to domain_create is an ugly 
> nuisance for the 99.9% of people who don't care a jot about it. 

You don't have to set up an ssid if you don't run a policy. Using
the NULL policy, shype should not introduce any change in system

The problem at hand is that the defined default id is the largest u32 
number and with the (new?) Python version this seems not to work the 
way it does with older ones.

> I think 
> a separate one-time-only hypercall to set the ssidref on a newly 
> created domain would be neater? 

I consider this not an option because the ssidref is used for determining
about domain creation.

>Or at least, surely the sane default 
> value for an integer ssidref is zero, not fffffffff?

This is a very good idea. We must either fix the problem with setting
an unsigned number 0xffffffff as default or we change the default
number to one that Python can work with.

>   -- Keir
> On 22 Jun 2005, at 17:13, George Washington Dunlap III wrote:
> > Changing the following line makes a temporary fix:
> >
> > tools/python/xen/xm/create.py
> > --
> >  gopts.var('ssidref', val='SSIDREF',
> > -          fn=set_u32, default=0xfffffff,
> >            use="Security Identifier.")
> > ++
> > gopts.var('ssidref', val='SSIDREF',
> > +          fn=set_u32, default=0xffff,
> >           use="Security Identifier.")
> > ---

Xen-devel mailing list