From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir@xensource.com>
Subject: Re: [1/3] [XEN] gnttab: Add new op unmap_and_replace
Date: Mon, 04 Jun 2007 14:18:13 +0100
Message-ID: <C289CFA5.FF1D%keir@xensource.com>
References: <20070604131247.GA17323@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20070604131247.GA17323@redhat.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Xen Development Mailing List <xen-devel@lists.xensource.com>, Herbert Xu <herbert@gondor.apana.org.au>
List-Id: xen-devel@lists.xenproject.org

On 4/6/07 14:12, "Daniel P. Berrange" <berrange@redhat.com> wrote:

> 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.

Oh, I see. In that case I think everything is now fine. Perhaps we should
leave the xenbr0 references as is then: at least it's clear we're talking
about a bridge in the contexts where we use it, as opposed to an interface
for local packet delivery.

 -- Keir