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-users

Re: [Xen-users] usage of the extra parameter in vm configs

To: "Christopher G. Stach II" <cgs@xxxxxxxxx>
Subject: Re: [Xen-users] usage of the extra parameter in vm configs
From: "Henning Sprang" <henning_sprang@xxxxxx>
Date: Sun, 31 Dec 2006 18:40:52 +0100
Cc: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sun, 31 Dec 2006 09:40:49 -0800
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=KAHhe46iHPLi9p0dORZ22+BKwwB+jfSZb3XkXyTQ6joCtwadCfiLNBzU07t92eXiZ8CDCqncNWudEvKXjchs1UUKpDWTB6d3u5IqXn8pCCzgKXGyR+09dH+vW+JB9L196pMwDm0lleCYrIZrweUwHvjknKKGfzV/DnzR9HAXCJk=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4597F034.5030205@xxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <5bb00b3f0612291512q2fb40f10n87800e4e3a56b634@xxxxxxxxxxxxxx> <5bb00b3f0612300737y21428f31idf92893cc618cff3@xxxxxxxxxxxxxx> <Prayer.1.0.18.0612301553350.14270@xxxxxxxxxxxxxxxxxxxxxx> <4597F034.5030205@xxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On 12/31/06, Christopher G. Stach II <cgs@xxxxxxxxx> wrote:
I'd prefer that they be consolidated, as well.  As you said, the ip,
extra, etc. variables assume that the guest is Linux.  That is obviously
not always the case.  Having one generic cmdline variable would be
generic enough and keep all of the relevant information in one location.
 Simplifying the config file parsing would also be nice for future
automated tools.

Only one thing comes to my mind: at least ip (not sure which others)
is used for setting up the routes in a routed networking setup, so it
must be kept. Or parsed from the new single commandline variable -
which gets hard when different OSes use different ways to give an ip
on command line. Or worse, if you don't set it on the commandline,
you'd be forced to still write the command line, because it's parsed
for routing.

But when making "ip" indepenedent from the kernel command line, those
users that use routed networking and a static ip given at the kernel
command line, have to set the same information in two places. But I
think that's acceptable.

Henning

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