Xen users - Jan 2009 - IP config problem with HVM

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''
on_poweroff = ''destroy''
on_reboot = ''restart''
on_crash = ''restart''

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''
on_poweroff = ''destroy''
on_reboot = ''restart''
on_crash = ''restart''

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@gmail.com


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

On Fri, Jan 30, 2009 at 5:58 AM, Rich Sage <rich.sage@gmail.com>
wrote:
> The 3rd
> is Windows Server 2003
Just to be sure, is it a new install? Win 2003 sp1 has firewall which
isn''t enabled by default. Make sure it''s not running an
blocking ping
request :)
> vif = [ ''type=ioemu, bridge=xenbr0'' ]
Does type=ioemu realy needed these days?
Here''s what I use

vif = [ ''mac=00:16:3E:XX:XX:XX, bridge=br6'' ]

change XX to whatever MAC you choose. This helps by making domUs MAC
persistent (which should help prevent certain network problems). My
bridge is br6, in your case it would be xenbr0.

Using this config, I installed Win 2003 (which can access network
correctly), updated to SP1, then installed GPLPV driver (which boosts
network performance greatly).
> I''ve also enabled proxy_arp on peth0 via:
>
> echo 1 > /proc/sys/net/ipv4/conf/peth0/proxy_arp
It should not matter for bridged setup. Leave it 0.
> 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
:-)
>
After setting up static MAC address (and making sure there''s no
firewall on Windows side), try this :
- make sure that dom0 has no firewall, or make sure that it allows
traffic from bridged domU
- ping to and from dom0, snoop the traffic for arp and icmp using

tcpdump -n -i xenbr0 arp or icmp

do it on the bridge, domU''s tap device, and peth0. That should at
least give some info on where the packets are missing.

Regards,

Fajar

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