[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [1/3] [XEN] gnttab: Add new op unmap_and_replace
- To: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
- From: Keir Fraser <keir@xxxxxxxxxxxxx>
- Date: Mon, 04 Jun 2007 14:18:13 +0100
- Cc: Xen Development Mailing List <xen-devel@xxxxxxxxxxxxxxxxxxx>, Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Delivery-date: Mon, 04 Jun 2007 06:16:50 -0700
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
- Thread-index: Acemqs3BDJAdWhKeEdyEowAX8io7RQ==
- Thread-topic: [Xen-devel] [1/3] [XEN] gnttab: Add new op unmap_and_replace
On 4/6/07 14:12, "Daniel P. Berrange" <berrange@xxxxxxxxxx> 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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel