From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Daniel P. Berrange" Subject: Re: [1/3] [XEN] gnttab: Add new op unmap_and_replace Date: Mon, 4 Jun 2007 14:12:47 +0100 Message-ID: <20070604131247.GA17323@redhat.com> References: <20070603020132.GA15239@gondor.apana.org.au> Reply-To: "Daniel P. Berrange" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: Xen Development Mailing List , Herbert Xu List-Id: xen-devel@lists.xenproject.org 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 -=|