* Thomas <iamkenzo@xxxxxxxxx> [2008-06-08 14:33]:
> Here are my config files:
Because sometimes less is more, I used a stripped-down version of your
configuration files:
> node01:
# -*- mode: python; -*-
kernel="/boot/domU_64/vmlinuz-2.6.21-xxxx-xenU-ipv4-64"
memory = "256"
maxmem = "512"
name = "node02"
vcpus=1
vif = [ 'ip=10.0.0.2' ] # replace with DomU's IP
ip = "10.0.0.2"
gateway= "10.0.0.128" # Dom0
netmask = "255.255.255.0"
disk = [ 'file:/xen/node01.img,hda1,w',
'file:/xen/node01-swap.img,hda2,w' ]
root = "/dev/hda1"
extra='console=xvc0 xencons=xvc0'
nographics=0
> --------------------------------------------------------------
>
> node02:
> --------------------------------------------------------------
# -*- mode: python; -*-
kernel="/boot/domU_32/vmlinuz-2.6.21-xxxx-xenU-ipv4-32"
memory = "256"
maxmem = "512"
name = "node01"
vcpus=1
vif = [ 'ip=10.0.0.1' ] # replace with DomU's IP
ip = "10.0.0.1"
gateway= "10.0.0.128" # Dom0
netmask = "255.255.255.0"
disk = [ 'file:/xen/node02.img,hda1,w',
'file:/xen/node02-swap.img,hda2,w' ]
root = "/dev/hda1"
extra='console=xvc0 xencons=xvc0'
nographics=0
> --------------------------------------------------------------
both boot up fine. I didn't test networking yet, but If you're going to
use only NAT-based machines and none using your "failover-IP" I
recommend changing /etc/xen/xend-config.sxp anyway (comment the route
lines at lines 161, 162 and activate the NAT-lines at 167, 168)
> I have noticed that when only 1 VM is running I only have 1 vifxx.0
> When I start a second VM (although it hangs) I see a second vif that
> appears, is that normal?
On the host, there is one vif per virtual interface. That is, if you
have a VM with more than 1 NIC, you'll see accordingly more vifs on the
host.
Amicalement,
Félix
--
Félix Krohn, <felix.krohn@xxxxxxx>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home