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: Jim Fehlig <jfehlig@xxxxxxxxxx>
Subject: Re: [Xen-devel] That xenstored console leak...
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Tue, 15 Jan 2008 08:10:42 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "Daniel P. Berrange" <berrange@xxxxxxxxxx>, John Levon <levon@xxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 15 Jan 2008 00:11:17 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <478BF500.9050409@xxxxxxxxxx>
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: AchXTh8LXaM2zMNBEdyI+gAWy6hiGQ==
Thread-topic: [Xen-devel] That xenstored console leak...
User-agent: Microsoft-Entourage/11.3.6.070618
On 14/1/08 23:49, "Jim Fehlig" <jfehlig@xxxxxxxxxx> wrote:

>> 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.
>>   
> 
> Reverting changesets 15967 and 15957 in addition to the attached patch
> fixes the leak and allows multiple localhost migrations.  I'm not sure
> what we get by nuking /vm/<uuid>/device/vif/<dev_num> anyway - other
> than the problems we're seeing :-). vif appears to be the only device
> stored in the /vm/<uuid>/device path anyway.
> 
> I will continue testing with this setup ...

Isn't having two domains (even from the same vm) pointing at the same /vm/
path a recipe for further bugs? Most of the lowlevel xend code doesn't seem
to understand the concept that domains can map to the same vm, and could
hence tread on each others toes via the /vm/ path.

If we revert the two patches, what happens when you create/destroy lots of
domains all with different uuids? I expect the leak will still exist in that
case.

 -- Keir



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