All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Keir Fraser <keir@xensource.com>
Cc: Xen Development Mailing List <xen-devel@lists.xensource.com>,
	Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [1/3] [XEN] gnttab: Add new op unmap_and_replace
Date: Mon, 4 Jun 2007 14:12:47 +0100	[thread overview]
Message-ID: <20070604131247.GA17323@redhat.com> (raw)
In-Reply-To: <C289C437.FF03%keir@xensource.com>

On Mon, Jun 04, 2007 at 01:29:27PM +0100, Keir Fraser wrote:
> 
> > [NET] Remove netloop and make copy_skb the default
> 
> Applied, thanks. But there still seem to be references to xenbr0 in the
> tools/ directory. And when I start xend I end up with two bridges, one
> called eth0 (which I think is the proper one?) and also a xenbr0 (probably
> bogus?). PV guests seem to by default correctly attach to the eth0 bridge,
> but HVM guests are ending up on this goes-nowhere xenbr0 bridge. Probably
> because it's still the hardcoded default bridge in qemu-dm?

Is that XenD itself keeping around bogus cached state about your network
and re-creating xenbr0 from this ?  Try rm -rf on /var/lib/xend/state
and reboot. The only places we reference xenbr0 is in the vif-bridge
and qemu-ifup scripts where we do auto-translation from xenbr0 to eth0
for back-compatability with old guest configs.

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

  parent reply	other threads:[~2007-06-04 13:12 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
2007-06-04 13:22           ` Daniel P. Berrange
2007-06-04 13:12       ` Daniel P. Berrange [this message]
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=20070604131247.GA17323@redhat.com \
    --to=berrange@redhat.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=keir@xensource.com \
    --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.