Re: [Xen-users] Bridge Setup problem in domU!

[Mark Hurenkamp <mark.hurenkamp@xxxxxxxxx>]

Hi Jan,

I forgot to mention that you need to replace your existing eth0 entry with the following:

auto eth0

iface eth0 inet manual

And then let these lines be followed by the br0 entry.

After reboot, you should have an br0 where you would normally use eth0.

If things still don't work, then please attach a bit more information, it is hard for us to guess

what goes wrong, if we don't see the config files you are using.

So if you still have network problems then please attach your original and your altered

interfaces file.

Regards,

Mark.

On Feb 15, 2010, at 6:50 PM, Jan Muhammad wrote:

Hi Mark,

Thanks indeed for your response.
Do you mean I should disable earlier entries in (/etc/network/interfaces) config file; I already have static entries in this file. I note that when I did so the NFS seems to stoped/failed and also now I can't create new domU's due to unavailablity of Network Proxy... :(

Regards

-Jan

From: Mark Hurenkamp <mark.hurenkamp@xxxxxxxxx>
Subject: Re: [Xen-users] Bridge Setup problem in domU!
To: "Jan Muhammad" <janmuhd@xxxxxxxxx>
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Date: Monday, 15 February, 2010, 21:50

Hi Jan,


> Either I disable or enable DHCP option in config file still the error
> message is same (as follow).
> Although both dom0 and domU boot okay, except for a problem with bridge
> problem. The network bridge is never setup when the
> server is rebooted.  I have to shutdown domU, and then run
>
> ./network-bridge stop
> ./network-bridge start

I'm using a similar setup, running a Ubuntu Karmic dom0, and several
Debian/Ubuntu domU machines.

But I've completely stopped using the network-bridge scripts, and now
setup the bridge from my /etc/network/interfaces config file, which avoids
the whole problem of transfering IP, and renaming eth device completely.


Here's an example for setting up a bridge using Debian/Ubuntu:

auto br0
iface br0 inet static
        address 192.168.1.101
        network 192.168.1.0
        netmask 255.255.255.0
        broadcast 192.168.1.255
        gateway 192.168.1.1
        bridge_ports eth0

This has worked fine for me ever since the first xen-3.0 days ;-)


Regards,

Mark.

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