[Xen-users] DomU network issues

[Colin Coe <CCoe@xxxxxxxxxxxxxxx>]

Hi all

Hopefully this will be the last of my issues...  I'm using Xen 3.0.0 (built
from the source tar ball) on RHEL4 on IBM HS20 blades with dual EM64T HT
Xeons.  I want a simple network setup where all the domU guest OS's are on
the same subnet as the dom0 host and all of the domU's are visible to the
rest of the LAN devices.

I've only been able to connect to domO from a device on the LAN since adding
the below to /etc/rc.d/rc.local (following
http://lists.xensource.com/archives/html/xen-devel/2005-01/msg00418.html)
but I still can't connect to domU (vm1 from now on) at OSI layer 3 or above.

With respect to the link above, I found doing 'brctl addif xenbr0 eth0'
catastrophic to our network, like really really really bad m'kay.

>From any device on the LAN I can arping vm1 but ping, ssh, etc don't work.
The link above mentioned an iptables MASQ rule which I tried without
success.

Can anyone give me a pointer on this?

Thanks in advance

CC


/etc/xen/xend-config.sxp
------------------------
(xend-http-server yes)
(xend-relocation-server yes)
(xend-address localhost)
(xend-relocation-address localhost)
(network-script network-bridge)
(vif-script vif-bridge)
(dom0-min-mem 196)
(dom0-cpus 0)

/etc/xen/vm1
------------
kernel = "/boot/vmlinuz-2.6-xen"
ramdisk = "/boot/initrd-2.6-xenU.img"
memory = 256
name = "vm1"
vcpus = 2
nics=1
vif = [ 'mac=aa:00:00:00:00:10, bridge=xenbr0' ]
disk = [ 'phy:rootvg/xen_vm1,sda1,w' ]
ip = "x.x.x.120"
netmask = "255.255.255.0"
gateway = "x.x.x.254"
hostname = "vm1"
root = "/dev/sda1 ro"
extra = "4"
on_crash    = 'destroy'

xm list
-------
Name                              ID Mem(MiB) VCPUs State  Time(s)
Domain-0                           0      251     4 r-----    63.6
vm1                                3      256     2 -b----     6.6

/etc/xen/scripts/network-bridge status
--------------------------------------
============================================================
3: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
    link/ether 00:14:5e:3c:41:98 brd ff:ff:ff:ff:ff:ff
    inet x.x.x.114/24 brd x.x.x.255 scope global eth0
20: xenbr0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
    inet x.x.x.114/24 brd x.x.x.255 scope global xenbr0

bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.feffffffffff       no              peth0
                                                        vif0.0
                                                        vif3.0

x.x.x.0/24 dev eth0  proto kernel  scope link  src x.x.x.114
x.x.x.0/24 dev xenbr0  proto kernel  scope link  src x.x.x.114
169.254.0.0/16 dev eth0  scope link
default via x.x.x.254 dev xenbr0

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
x.x.x.0         0.0.0.0         255.255.255.0   U     0      0        0 eth0
x.x.x.0         0.0.0.0         255.255.255.0   U     0      0        0
xenbr0
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth0
0.0.0.0         x.x.x.254       0.0.0.0         UG    0      0        0
xenbr0
============================================================

/etc/rc.d/rc.local
------------------
/sbin/ip route del default via x.x.x.254 dev eth0
/sbin/service xend start
/sbin/ip addr add x.x.x.114/24 brd x.x.x.255 scope global dev xenbr0
/sbin/ip route add default via x.x.x.254 dev xenbr0
************************************************************************
Bunnings Legal Disclaimer:

1)     This email is confidential and may contain legally privileged
information.  If you are not the intended recipient, you must not
disclose or use the information contained in it.  If you have received
this email in error, please notify us immediately by return email and
delete the document.

2)     All emails sent to and sent from Bunnings Group Limited.
are scanned for content.  Any material deemed to contain inappropriate
subject matter will be reported to the email administrator of all
parties concerned.
************************************************************************


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