[Xen-users] Re: dom0 and domU don't want to talk IP to each other

["Robert Gubler" <rgubler@xxxxxxxxx>]

Hey, 

So I fixed the problem.  Turns out after I create a new bridge interface using brctl I then have to do `ifconfig [bridge-name] [ip] up`.  Doing this lets dom0 talk to domU. Also, the interface [bridge-name] has to be brought up in order for domU's to talk among themselves.

Regards,

Rob

On 10/15/06, Robert Gubler <rgubler@xxxxxxxxx> wrote:

Hello,

I am having trouble getting dom0 and a domU to talk IP to each other over the virtual ethernet devices that the xend scripts creates.  Ideally I'd like my dom0 setup such that it does not automatically configure the vifXX.Y interfaces to be bridged with my physical device.  I couldn't find a simple way to do this with the xend scripts, so instead I have specified my own bridge in the domU config file.

Its worth noting that during the domU boot I see the following message: "XENBUS: Device with no driver: device/vif/0."  I am getting around this by manually loading the xennet module.  Also, during the shutdown of domU it prints out this message: "Device eth0 has MAC address 00:16:3E:00:01:01, instead of configured address 00:08:74:26:75:C7. Ignoring."  (That second MAC address happens to be my physical NIC's MAC address)

I configured both domU's eth0 and dom0's vifXX.Y to have an IP address on the same network.  Running tcpdump on domU and then when I try to ping the domU IP from the dom0 IP I can see ARP requests and ARP responses.  Ping fails however, and no ARP entry is added to the table.  This is even true if I setup tcpdump on dom0's vifXX.Y interface.  I also setup a static arp entry on either end and this failed as well.  I don't know what is going on that is preventing this from working.

Here is the play by play:

ON dom0:

# brctl addbr test
# xm create myconfig
Using config file "myconfig".
Started domain myconfig
# ifconfig vif5.0 192.168.0.6
# ping 192.168.0.5&
# tcpdump -i vif5.0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vif5.0, link-type EN10MB (Ethernet), capture size 96 bytes
16:11:35.353437 arp who-has 192.168.0.5 tell 192.168.0.6
16:11:35.354645 arp reply 192.168.0.5 is-at 00:16:3e:00:01:01 (oui Unknown)
16:11:36.353479 arp who-has 192.168.0.5 tell 192.168.0.6
16:11:36.354114 arp reply 192.168.0.5 is-at 00:16:3e:00:01:01 (oui Unknown)
16:11:37.353544 arp who-has 192.168.0.5 tell 192.168.0.6
16:11:37.354202 arp reply 192.168.0.5 is-at 00:16:3e:00:01:01 (oui Unknown)
From 192.168.0.6 icmp_seq=1 Destination Host Unreachable
From 192.168.0.6 icmp_seq=2 Destination Host Unreachable
From 192.168.0.6 icmp_seq=3 Destination Host Unreachable


ON domU:

# insmod xennet.ko
# ifconfig eth0 192.168.0.5
# tcpdump -i eth0
audit(1160953759.735:2): dev=eth0 prom=256 old_prom=0 auid=4294967295
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
19:11:34.779231 arp who-has 192.168.0.5 tell 192.168.0.6
19:11:34.779289 arp reply 192.168.0.5 is-at 00:16:3e:00:01:01 (oui Unknown)
19:11:35.779179 arp who-has 192.168.0.5 tell 192.168.0.6
19:11:35.779215 arp reply 192.168.0.5 is-at 00:16:3e:00:01:01 (oui Unknown)
19:11:36.779278 arp who-has 192.168.0.5 tell 192.168.0.6
19:11:36.779310 arp reply 192.168.0.5 is-at 00:16:3e:00:01:01 (oui Unknown)

DomU is running a fedore core 5 based filesystem, with the 2.6.17-1.2187_FC5xenU kernel.  Dom0 is running fedore core 5 with the 2.6.17-1.2174_FC5xen0 kernel.  

Any ideas??

Thanks,

Rob

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