From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: Re: Communicating with the Guest Os before the network comes up. Date: Wed, 19 Jul 2006 08:45:49 +0200 Message-ID: <44BDD51D.4000208@suse.de> References: <20060718115411.GA3210@lxlabs.com> <20060719054509.GA13957@lxlabs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20060719054509.GA13957@lxlabs.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ligesh Cc: xen-devel@lists.xensource.com, Jacob Gorm Hansen List-Id: xen-devel@lists.xenproject.org > Yes, on linux you can pass arguments to the kernel commandline which > can be read from the /proc/cmdline. But I needed a cross platform > generic method by which to bootstrap the network of the guest OS, and > currently it appears there isn't one. In fact, when it comes to Xen, > my primary aim is to run Windows. I still can't see what is wrong with the DHCP approach ... * You can give every virtual machine a fixed MAC address. * DHCP can be configured to hand out fixed IP address (based on the machines MAC address). * You can even invent some scheme to map mac addresses to ip addresses (something like aa:bb:01:02:03:04 => 1.2.3.4), then you can easily script-generate the dhcp config file entries. That will "just work" with almost every OS on the planet ;) cheers, Gerd -- Gerd Hoffmann http://www.suse.de/~kraxel/julika-dora.jpeg