WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] That xenstored console leak...

To: John Levon <levon@xxxxxxxxxxxxxxxxx>, Jim Fehlig <jfehlig@xxxxxxxxxx>
Subject: Re: [Xen-devel] That xenstored console leak...
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Mon, 14 Jan 2008 21:29:38 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 14 Jan 2008 13:30:10 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20080114200853.GA27586@xxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AchW9JC3zwEWnMLnEdyLPAAWy6hiGQ==
Thread-topic: [Xen-devel] That xenstored console leak...
User-agent: Microsoft-Entourage/11.3.6.070618
On 14/1/08 20:08, "John Levon" <levon@xxxxxxxxxxxxxxxxx> wrote:

> I see the behaviour in 3.1 with HVM domains. If I live migrate twice,
> then the MAC address is lost, and a new random one is generated:
> 
> I don't have to do anything "special", this happens every time on 3.1. I
> presume that the troublesome changeset fixes this exact problem.

Yes, device controllers clean up by deleting /vm/<uuid>/path/to/device. This
aliases with the new domain's device information (because they're really the
same vm) and so when the old domain is cleaned up the new domain loses
information. Disambiguating with an extra level of indirection seemed the
simplest fix for this. I'm not sure why this leads to xenstore leaks.

When a domain is finally garbage collected in xend, perhaps we should delete
its entire /vm/<uuid>/<unique-number>? That would seem a nice and reasonable
catch-all.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel