From: Keir Fraser <keir@xensource.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Xen Development Mailing List <xen-devel@lists.xensource.com>,
"Daniel P. Berrange" <berrange@redhat.com>
Subject: Re: [1/3] [XEN] gnttab: Add new op unmap_and_replace
Date: Mon, 04 Jun 2007 14:15:20 +0100 [thread overview]
Message-ID: <C289CEF8.FF1B%keir@xensource.com> (raw)
In-Reply-To: <20070604123934.GA404@gondor.apana.org.au>
On 4/6/07 13:39, "Herbert Xu" <herbert@gondor.apana.org.au> wrote:
> That's weird.
>
> There is only one call to 'brctl addbr' and that's via network-bridge.
> So if xend's only been started once then I can't see how you could end
> up with two bridges.
>
> Can you add a set -x to xen-network-common.sh to see who's creating
> two bridges?
It's also invoked by create_bridge() inside xend. So I had to blow away
/var/lib/xend/state and that's fixed the problem.
Anyway, all seems better now except for some hotplug slowness on my test
machine for the first VM I create after rebooting the host (possibly a stale
lock file that I'm having to wait to time out).
However, there *are* still a lot of references to xenbr0 in the tools/
directory, including in our example configs. Should we get rid of these
references, or change to 'bridge=eth0'?
-- Keir
next prev parent reply other threads:[~2007-06-04 13:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 4:55 [1/3] [XEN] gnttab: Add new op unmap_and_replace Herbert Xu
2007-05-29 4:55 ` [2/3] [LINUX] gnttab: Add basic DMA tracking Herbert Xu
2007-06-06 6:18 ` Isaku Yamahata
2007-06-06 8:37 ` Herbert Xu
2007-06-06 12:35 ` Herbert Xu
2007-06-07 4:32 ` [LINUX] gnttab: Fix copy_grant_page race with seqlock Herbert Xu
2007-06-07 8:36 ` [2/3] [LINUX] gnttab: Add basic DMA tracking Isaku Yamahata
2007-06-07 8:44 ` Isaku Yamahata
2007-06-07 8:48 ` was " Isaku Yamahata
2007-06-07 8:51 ` Herbert Xu
2007-05-29 4:55 ` [3/3] [NET] back: Add lazy copying Herbert Xu
2007-05-30 11:50 ` [1/3] [XEN] gnttab: Add new op unmap_and_replace Keir Fraser
2007-05-30 13:09 ` Herbert Xu
2007-06-03 2:01 ` Herbert Xu
2007-06-04 12:29 ` Keir Fraser
2007-06-04 12:39 ` Herbert Xu
2007-06-04 13:15 ` Keir Fraser [this message]
2007-06-04 13:22 ` Daniel P. Berrange
2007-06-04 13:12 ` Daniel P. Berrange
2007-06-04 13:18 ` Keir Fraser
2007-06-04 13:29 ` Daniel P. Berrange
2007-06-04 14:12 ` Gerd Hoffmann
2007-06-05 16:17 ` Keir Fraser
2007-06-05 16:36 ` Daniel P. Berrange
2007-06-06 7:54 ` Gerd Hoffmann
2007-06-12 17:10 ` Keir Fraser
2007-06-14 7:41 ` Gerd Hoffmann
2007-06-14 11:01 ` Daniel P. Berrange
2007-06-06 7:50 ` Gerd Hoffmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C289CEF8.FF1B%keir@xensource.com \
--to=keir@xensource.com \
--cc=berrange@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.