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] Re: Communicating with VM before Network is configured.

To: "tbrown@xxxxxxxxxxxxx" <tbrown@xxxxxxxxxxxxx>
Subject: Re: [Xen-users] Re: Communicating with VM before Network is configured.
From: "Chris McKeever" <techjedi@xxxxxxxxx>
Date: Mon, 17 Jul 2006 18:45:53 -0500
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 17 Jul 2006 16:46:37 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=UHjFrTepwgg5umSBSG3m79AHgS1dOmNjOuskX4+dudXl+aaytWBo57qdMLDfvzzZlZ2aDMdOcl7JmuHKgYmP9tDXMSZ4D1PZgr8fTNssZ6fkV3jr7nXZa1vhi4TWGKuTdS+XThYeC3sEf5wU6uz8ilmIXYC4nSU2MHOtFab+9ug=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <Pine.LNX.4.44.0607171509100.5814-100000@xxxxxxxxxxxxxxxxxx>
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: <20060718071115.GA11356@xxxxxxxxxx> <Pine.LNX.4.44.0607171509100.5814-100000@xxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On 7/17/06, tbrown@xxxxxxxxxxxxx <tbrown@xxxxxxxxxxxxx> wrote:
   extra="NBDHOST=65.39.183.43 NBDPORT=8001
      ip=192.168.2.254:1.1.1.1:192.168.2.86:255.255.255.0"

for an init script it's really simple, as those NBD* parms are already
loaded into environment variables :) ... but in the more general
case you would need to parse them out of /proc/cmdline

I don't believe xen has any specific methods for passing config
parameters to the domU, but I'm no expert.

Oh, and looking back at the subject line... those ip config parameters
might be of use to you... ip=192...


I have been playing with this myself - and I can't seem to get the
kernel autoconfig working (FC5) -
My xen kernel has been compiled with the CONFIG_IP_PNP
option set, and then reboot

I 'try' to pass  the kernel the following parameters at boot, but they
just dont seem to take:

vif = [ 'ip=192.168.1.61' ]
netmask = "255.255.255.0"
gateway = "192.168.1.1"
hostname = "ds-1"


any suggestions as to what I may be missing?

Thanks
Chris



You'll need a kernel with autoconfig enabled.

-Tom



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



--
----------------------------------
please respond to the list .. if you need to contact me direct
cgmckeever is the account
prupref.com is the domain

<A href="http://www.prupref.com";>Simply Chicago Real Estate</A>

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

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