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


[Xen-devel] RE: ip=x.y.z.w in config file ends up in pv guest /proc/cmdl

To: dan.magenheimer@xxxxxxxxxx, "Xen-Devel (E-mail)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] RE: ip=x.y.z.w in config file ends up in pv guest /proc/cmdline (but not in xen 3.3)
From: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Date: Wed, 8 Apr 2009 15:42:24 +0000 (GMT)
Delivery-date: Wed, 08 Apr 2009 08:43:10 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <435216e6-7011-4be7-a34a-de528b366e58@default>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
If anyone is interested, I tracked this down (with
some help from Zhigang Wang) to a recent change in
pygrub.  This one, I think:


Substituting the xen-unstable /usr/bin/pygrub into
a xen-3.3.1 toolset provides the same functionality.

> -----Original Message-----
> From: Dan Magenheimer 
> Sent: Wednesday, April 01, 2009 4:34 PM
> To: Xen-Devel (E-mail)
> Subject: ip=x.y.z.w in config file ends up in pv guest /proc/cmdline
> (but not in xen 3.3)
> I found that if you specify ip="ip_address" in
> a PV config file, when the PV guest comes up,
> /proc/cmdline contains the ip= (and some other
> stuff).  Cool!  With minor init script mods, it's
> now possible to "configure" a network interface
> with an ip specified in the config file, thus
> making it easier to "clone" VMs.
> I was then disappointed to find that this feature
> (bug fix?) isn't in xen 3.3, just in xen-unstable.
> Can someone point me to the patch that made this
> new feature work?  If it's not too interdependent
> with other stuff, I might try to backport it.
> Thanks,
> Dan

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>