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] ip=x.y.z.w in config file ends up in pv guest /proc/cmdline

To: "Xen-Devel (E-mail)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] 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, 1 Apr 2009 15:34:05 -0700 (PDT)
Delivery-date: Wed, 01 Apr 2009 15:35:47 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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
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.


Xen-devel mailing list

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