[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] IP config problem with HVM


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Rich Sage <rich.sage@xxxxxxxxx>
  • Date: Thu, 29 Jan 2009 22:58:05 +0000
  • Delivery-date: Thu, 29 Jan 2009 14:59:28 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=fMO0JKB6s/MdBbNwSBBywzQZF8dymMHy/mPnXl+hor83u4FYFLtmvrItAAQoTxwWlS fzI7rUl2cK2M8T7EoDP4FREaCUp9xi1BsQJe5TqJf7XdCaneyqzdVAr8Qo+EQGj9voWV cx9FYJEotnDHZyp86oou/R0tDuodn+FVT36So=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi all,

I'm having some troubles setting up 4 x domUs on Xen 3.2.1, running on Debian Etch.  3 of the domUs are to have externally visible IPs, with the 4th domU being accessible internally only.

2 of the externally visible domUs are Linux-based (Fedora, Debian).  The 3rd is Windows Server 2003, running using hvmloader.  This final domain is the one I'm having problems with.  It installs fine, I can configure it in Windows with an IP address (through VNC to the main box's IP), but this IP is never available externally through the bridge.

My IP configuration is as follows:

domU - #1: 192.168.0.75  (Debian)
domU - #2: 192.168.0.76  (Fedora)
domU - #3: 192.168.0.77  (Windows)  << not available to ping either from the dom0 or externally.
domU - #4: 10.0.0.53 (internal Xen network Fedora)

In /etc/xen/xend-config.sxp:

(network-script 'network-bridge bridge=xenbr0')
(vif-script vif-bridge)
(dom0-min-mem 128)
(dom0-cpus 0)

In one of the Linux VM cfg files: (the other is identical save for the root FS path)

kernel = '/boot/vmlinuz-2.6.18-6-xen-amd64'
ramidks = '/boot/initrd.img-2.6.18-6-xen-amd64'
memory = '768'
root = '/dev/sda1 ro'
disk = ['phy:VolGroup1/simon-disk,sda1,w', 'phy:VolGroup1/simon-swap,sda2,w']
name = 'simon'
vif = [ 'ip=192.168.0.75' ]
dhcp = 'off'
hostname = 'simon'
>>>
and in the Windows VM:

kernel = '/usr/lib/xen-3.2.1/boot/hvmloader'
builder = 'hvm'
memory = '768'
device_model = '/usr/lib/xen-3.2.1/bin/qemu-dm'
disk = [ 'phy:/dev/VolGroup1/chris-disk,ioemu:hda,w', 'file:/root/win2k3.iso,ioemu:hdc:cdrom,r' ]
name = 'chris'
vif = [ 'type=ioemu, bridge=xenbr0' ]
boot = 'd'
sdl = '0'
>>>
Running 'brctl show' gives a bridge name of 'xenbr0' with peth0,vif2.0,vif3.0,vif5.0,tap0,vif6.0 all part of the bridge.

I've also enabled proxy_arp on peth0 via:

echo 1 > /proc/sys/net/ipv4/conf/peth0/proxy_arp

but not sure if this is having a positive/negative effect as if its enabled or not, there is no difference...!

Is there something crucial I'm missing here? If I've forgotten to provide any more useful information, please let me know and I'll post it :-)

Thanks in advance,

Rich

--
Rich Sage
Leeds, UK
rich.sage@xxxxxxxxx
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.