Hi, everyone
I just started with Xen yesterday and have been doing a search through
Google and the mailing lists. So far, I can''t seem to get my
networking right (between dom0 and dom1) even though I think I''ve
followed the right steps.
Background:
Dom0: 192.168.0.1 / 255.255.0.0
Dom1: 192.168.0.2 / 255.255.0.0
Here''s what I have on the host OS:
eth0 Link encap:Ethernet HWaddr 00:0C:29:BA:AC:E0
inet addr:192.168.0.1 Bcast:192.168.255.255 Mask:255.255.0.0
vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
xen-br0 Link encap:Ethernet HWaddr 00:0C:29:BA:AC:E0
inet addr:192.168.0.1 Bcast:192.168.255.255 Mask:255.255.255.255
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 0.0.0.0 255.255.0.0 U 0 0
0 xen-br0
0.0.0.0 192.168.254.254 0.0.0.0 UG 0 0
0 xen-br0
And on the guest OS:
eth0 Link encap:Ethernet HWaddr DE:AD:29:BA:AC:EA
inet addr:192.168.0.2 Bcast:182.168.255.255 Mask:255.255.0.0
In the dom1 config, I''ve configured vif as follows:
vif = [ ''mac=DE:AD:29:BA:AC:EA, bridge=xen-br0'' ]
bridge utils seems to have it correct:
bridge name bridge id STP enabled interfaces
xen-br0 8000.000c29baace0 no eth0
vif1.0
I can''t even get the guest OS and the host OS to talk to each other.
I''ve also tried enabling ip_forward but still no dice. I was mucking
around before and managed to get them to talk to each other once, but
from there I couldn''t make the guest OS talk to the gateway of the
host OS.
Not sure what I''ve missed. I''m using xen-2.0.5 on Centos 4
(both host
and guest OSs).
Any advise appreciated.
- gino
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Gino LV. Ledesma wrote:> And on the guest OS: > eth0 Link encap:Ethernet HWaddr DE:AD:29:BA:AC:EA > inet addr:192.168.0.2 Bcast:182.168.255.255 Mask:255.255.0.0You have a typo here: 182.168. It''s confused about the network, if that is really the case. Your eth0 interface on the guest OS is not on the same subnet as the dom0 interface. That needs to be the same.> In the dom1 config, I''ve configured vif as follows: > vif = [ ''mac=DE:AD:29:BA:AC:EA, bridge=xen-br0'' ] > > bridge utils seems to have it correct: > > bridge name bridge id STP enabled interfaces > xen-br0 8000.000c29baace0 no eth0 > vif1.0 > I can''t even get the guest OS and the host OS to talk to each other. > I''ve also tried enabling ip_forward but still no dice. I was mucking > around before and managed to get them to talk to each other once, but > from there I couldn''t make the guest OS talk to the gateway of the > host OS.Also, are your routes setup on the guest domain? "netstat -rn" or "ip route show" will tell you.. thanks, nivedita _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 4/21/05, Nivedita Singhvi <niv@us.ibm.com> wrote:> Gino LV. Ledesma wrote: > > > And on the guest OS: > > eth0 Link encap:Ethernet HWaddr DE:AD:29:BA:AC:EA > > inet addr:192.168.0.2 Bcast:182.168.255.255 Mask:255.255.0.0 > > You have a typo here: 182.168. It''s confused about the network, > if that is really the case. > > Your eth0 interface on the guest OS is not on the same subnet > as the dom0 interface. That needs to be the same.Sorry, that was indeed a typo. It''s 192.168.255.255. Both dom0 and dom1 are within the same subnet (192.168.0.0/16).> Also, are your routes setup on the guest domain? > > "netstat -rn" or "ip route show" will tell you.. >I''ve managed to get the host and guest OSs talk to each other. I needed to have one of them ping the other for a couple of seconds (is this an ARP learning issue?). Now the next part, which is getting the guest OS to talk to the main router -- 192.168.254.254. Routes of the guest OS: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 192.168.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 0.0.0.0 192.168.254.254 0.0.0.0 UG 0 0 0 eth0 Looks simple enough. :-) thanks! gino _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 4/21/05, Nivedita Singhvi <niv@us.ibm.com> wrote:> Gino LV. Ledesma wrote: > > > I''ve managed to get the host and guest OSs talk to each other. I > > needed to have one of them ping the other for a couple of seconds (is > > this an ARP learning issue?). Now the next part, which is getting the > > Hmm, there is a race window where the bridge doesn''t get setup > because the interface transfer doesn''t happen in time, but that > is not what you are seeing here. If the bridge seems to be up, > they should ping themselves right away, the dom1->dom0 path is > mostly fake. > > I''d be interested in finding out if that is a persistent problem..Sorry... This was a fluke on my part. I was running Xen within VMware, and apparently, vmnet only bridges the guest OS''s interface to the host''s interface. After installing Xen on another dedicated machine (without LVM -- which was why I didn''t install it on my box earlier), everything worked out great out of the box. Thanks for the support. gino _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users