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] dom0 networking disabled

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] dom0 networking disabled
From: "Kirk Brown" <kbrown@xxxxxxxxxxxxx>
Date: Fri, 16 Mar 2007 07:02:27 -0500 (CDT)
Delivery-date: Fri, 16 Mar 2007 05:01:39 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
Importance: Normal
In-reply-to: <20070316044013.GG18608@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>
References: <1314.66.25.182.130.1174003072.squirrel@xxxxxxxxxxxxxxxxxx> <20070316044013.GG18608@xxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: SquirrelMail/1.4.5
Hi jez, thanks for the advice - it worked perfectly. To clarify for others
having the same problem - I was using the xen bridge script which would
kill the networking for Dom0, but work with the DomU's. The fix was to
*not* use xen's bridging.

My original /etc/network/interfaces looked like this:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
        address XXX.XXX.XXX.XXX
        netmask 255.255.255.0
        gateway XXX.XXX.XXX.XXX

and in the xend-config, I had:
(network-script network-bridge)


The fix was to set up the bridge directly in /etc/network/interfaces by
changing eth0 to:

auto xenbr0
iface xenbr0 inet static
        address XXX.XXX.XXX.XXX
        netmask 255.255.255.0
        gateway XXX.XXX.XXX.XXX
        bridge_ports eth0

and use the network-dummy in xend-config:
(network-script network-dummy)

Reboot and everything comes up OK.

Thanks again!

K

> 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
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>



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