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] xm create option parsing..

To: Steven Hand <Steven.Hand@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] xm create option parsing..
From: Tom Wilkie <tw275@xxxxxxxxx>
Date: Wed, 28 Jul 2004 17:45:02 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 28 Jul 2004 17:45:19 +0100
Envelope-to: Steven.Hand@xxxxxxxxxxxx
In-reply-to: <E1BprRD-0008Hh-00@xxxxxxxxxxxxxxxxx>
References: <E1BprRD-0008Hh-00@xxxxxxxxxxxxxxxxx>
Yeah this happens as all option to set variables must come at the end of the command line, which all switch must come before them.

Its just the way the command line is parsed.

Tom

On 28 Jul 2004, at 17:37, Steven Hand wrote:


As far as I can see, "xm create -c vmid=1" will create a domain and
attach to its console while "xm create vmid=1 -c" won't.

Any reason for this? The option parsing routines xm/opts.py and
xm/create.py seems substantial enough.


cheers,

S.



-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel