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/
Home Products Support Community News


Re: [Xen-devel] connecting dom0 directly to the bridge(was:performance p

To: Xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] connecting dom0 directly to the bridge(was:performance problems...)
From: Goetz Bock <bock@xxxxxxxxxxx>
Date: Thu, 12 Jan 2006 22:44:59 +0100
Delivery-date: Thu, 12 Jan 2006 21:55:35 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77DAF0484@xxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Mail-followup-to: Goetz Bock <bock@xxxxxxxxxxx>, Xen-devel@xxxxxxxxxxxxxxxxxxx
References: <AEC6C66638C05B468B556EA548C1A77DAF0484@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.2i
On Fri, Jan 13 '06 at 08:00, James Harper wrote:
> > > On Thu, Jan 12 '06 at 12:24, Ian Pratt wrote:
> > > > You haven't connected dom0 directly to the bridge rather than
> > > > vif0.0 to the bridge have you?
> > >
> > > I've been doing that with xen 2.0 and xen 3.0.0, what's bad
> > > about doing this?
> > 
> > You shouldn't connect directly if you run services in dom0 for the
> > domU's. Using vif0.0 prevents a possible deadlock.
> > 
> I must be missing something here... doesn't the init script itself add
> eth0 to xen-br0??? Does dom0 somehow internally create vif0.0 as a
> mirror of eth0?
What the init script does is:
- rename eth0 to peth0
- make a bridge xen-br0
- add peth0 to the bridge
- create a virtual interface (vif0.0?) add it to the bridge
- (some how create a new interface named eth0 and connect it (via
  vif0.0?) to the bridge too)
- configore the old IP to this new interface

What I've been doing on all my xen and uml boxes, ever since:
- make a bridge: xen-br0
- add eth0 to the bridge
- configure the systems (dom0) IP to xen-br0

Seamed to work fine. But now that I think of it, I might have some
deadlocks, but they always locked up eth0 in a way that I had to
unload/reload the module...

BTW: when replying to my mails, could you PLEASE not also CC me. I read
     this list. If time permits all posts.
/"\ Goetz Bock at blacknet dot de  --  secure mobile Linux everNETting
\ /       (c) 2006 Creative Commons, Attribution-ShareAlike 2.0 de
 X   [ 1. Use descriptive subjects - 2. Edit a reply for brevity -  ]
/ \  [ 3. Reply to the list - 4. Read the archive *before* you post ]

Xen-devel mailing list

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