WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] strange network problem

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] strange network problem
From: "Sebastian Reitenbach" <sebastia@xxxxxxxxxxxxxxxxxxxx>
Date: Wed, 21 Nov 2007 09:54:33 +0100
Delivery-date: Wed, 21 Nov 2007 00:55:17 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Organization: L00 bugdead prods.
Reply-to: Sebastian Reitenbach <sebastia@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

Sebastian Reitenbach <sebastia@xxxxxxxxxxxxxxxxxxxx> wrote: 
> Hi,
> 
> I some problem setup networking on a opensuse 10.3, x86_64, xen 3.1.0.
> I have four suse 10.3, x86_64 PVM hosts running on it, they are connected 
> via a bridge to get network.
> 
> I can connect from external hosts, to the virtual machine, and from the 
> virtual machines to the internet, no problem. But I cannot reach the dom0 
> from within the domU's or vice versa. Also the domU's are able to 
> communicate with each other via that bridge, so forwarding etc is active.
> 
> brctl show xenbr0
> bridge name     bridge id               STP enabled     interfaces
> xenbr0          8000.001871874e9d       no              vif45.0
>                                                         vif46.0
>                                                         eth1
>                                                         vif47.0
>                                                         vif48.0
> 
> 
> Only after I added the four host routes to the domU's I was able to 
> communicate between dom0 and domU. I have another Xen server, running 
> sles10, there I did not had to add these explicit routes.
> netstat -rn
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags   MSS Window  irtt 
> Iface
> 10.0.0.139      0.0.0.0         255.255.255.255 UH        0 0          0 
> xenbr0
> 10.0.0.138      0.0.0.0         255.255.255.255 UH        0 0          0 
> xenbr0
> 10.0.0.141      0.0.0.0         255.255.255.255 UH        0 0          0 
> xenbr0
> 10.0.0.140      0.0.0.0         255.255.255.255 UH        0 0          0 
> xenbr0
> 10.0.0.0        0.0.0.0         255.255.255.0   U         0 0          0 
> eth1
> 10.0.0.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 
> eth1
> 127.0.0.0       0.0.0.0         255.0.0.0       U         0 0          0 
lo
> 
> 
> The virtual interfaces are configured like this in the domU configuration 
> file:
> vif=[ 'mac=00:16:3e:6a:64:07,bridge=xenbr0', ]
> 
> 
> do I need to do any additional network configuration to allow 
communication 
> from domU do dom0?
> Any more information I should provide?

As a workaround I created a native bridge, with just my physical interface 
as a device, and then I reconfigured the xen domU's to bind to that bridge, 
instead of the xenbr0, and it works like a charm, but I doubt that it is the 
way it should work. That works for me, and I am fine with that, but if 
anybody has a hint on how to do it with using xenbr0, please let me know.

kind regards
Sebastian


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

<Prev in Thread] Current Thread [Next in Thread>