All those interested,
Here's how I solved this (kind of dirty, but it worked).
1. I hacked site-packages/xen/xm/create.py and added a couple of new
options that can be specified in the domain config file (IP, gateway
etc).
2. Those options were passed to the kernel as parameters and then I
grabbed those parameters (they're set to environment variables) in
the /etc/init.d/rcS init file and created a
custom /etc/network/interfaces with them.
Let me know if you have questions about how I did this or any better
suggestions.
Michael
On Tue, 2005-06-07 at 10:54 -0600, Michael Musson wrote:
> Hello all,
>
> I'm attempting to manually set my domain eth0 address in the domain
> config file instead of using DHCP. Here's the config file:
>
> kernel ="/boot/vmlinuz-2.6.11-1.1369_FC4xenU"
> memory = 64
> name = "D1"
> dhcp = "off"
> nics = 1
> disk = ['file:/root/xen/d1/d1.img,sda1,w']
> root = "/dev/sda1 ro"
> nics = 1
> vif = ['mac=AA:00:00:18:98:FB']
> netmask = "255.255.255.0"
> ip = "10.10.10.11"
> gateway = "10.10.10.99"
>
> The dmesg output is:
>
> <snip>
> Kernel command line:
> ip=10.10.10.11:1.2.3.4:10.10.10.99:255.255.255.0::eth0:off
> root=/dev/sda1 ro
> <snip>
>
> Then, eth0 can be brought with "ifconfig eth0 up", but it doesn't have
> an IP address assigned. Is there something I'm missing out on?
>
> Best,
> Michael
>
> [Fedora Core 4 test 3,
> kernel-xen0.i686 2.6.11-1.1369_FC4,
> kernel-xenU.i686 2.6.11-1.1369_FC4,
> xen.i386 2-20050530,
> debian domain filesystem ]
>
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home