jez,
I have had the exactly the same problem in Fedora Core 6, which uses
/etc/sysconfig/network-scripts/ifcfg-eth0 etc to configure nics.
when i copied your code to ifcfg-xbr0 and tried ifup xbr0, i got errors saying
command bridge_ports not found.
i would appreciate it very much for your help.
Message: 2
Date: Fri, 16 Mar 2007 05:40:13 +0100
From: jez <jez@xxxxxxxxxx>
Subject: Re: [Xen-users] dom0 networking disabled
To: xen-users@xxxxxxxxxxxxxxxxxxx
Message-ID: <20070316044013.GG18608@xxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=us-ascii
On Thu, Mar 15, 2007 at 06:57:52PM -0500, kbrown@xxxxxxxxxxxxx wrote:
>
> I installed Debian Etch and the Xen (3.03) kernels / binaries on a Dell
> server. It works fantastic with all the default configurations with one
> strange flaw - as soon as the /etc/xen/scripts/network-bridge script runs,
> dom0 loses all network connectivity. It is no longer possible to ping in
> or out of the IP for the machine, and it throws no errors, just sits on a
> blinking prompt.
>
> I have 4 domU machines running on 4 different IPs and they all work
> perfectly, with perfect connectivity. All the default configuration files
> seem correct, and there are no firewall problems that I can see. Nothing
> gets in or out of dom0, though, from anywhere. Running
> '/etc/xen/scripts/network-bridge stop' will return eth0 to its former
> state and everything starts working again.
>
> So either I'm missing something very obvious, or something is very wrong -
> I've attached several readouts below, but let me know if any other info
> would be helpful in solving this thing, its had us stumped and seems to be
> the only thing keeping us from putting this box into production.
>
> Thanks for any insight,
>
> Kirk
>
Hi Kirk
I've looked through the information that you posted but I can't see
anything wrong with any of it.
I reckon that you should bypass the network-bridge script and just use
your own bridge set up in /etc/network/interfaces. It's insanely easy to
set up, and if nothing else it might shed some more light on your
predicament.
Here are the steps to take:
1. Change your /etc/network/interfaces to look like this. Make sure you
remove or comment out your previous eth0 entry:
auto lo
iface lo inet loopback
auto xbr0
iface xbr0 inet static
address 146.6.135.253
netmask 255.255.255.0
gateway 146.6.135.1 # <- put your gateway here
bridge_ports eth0
2. Change your xend-config.sxp to read:
(network-script network-dummy)
(vif-script vif-bridge)
3. Double check that the settings for xbr0 in /etc/network/interfaces
are exactly the same as eth0 previously had. Then when you are
satisfied, reboot.
If your computer resurfaces, and you can contact it over the network,
then the bridge is up. If not, well eh ... you're own your own mate!
Now when you start each of the DomU's xen should put the vif*.0
interfaces on your bridge. All in all, I think you'll find that
this is a much more transparent configuration.
Let us know how you get on.
jez
John Shen
System Coordinator, Online Information System
Student Affairs, University of California, Office of the President
<<winmail.dat>> _______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home