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/
Home Products Support Community News


RE: [Xen-devel] [PATCH]:libxl__get_free_memory_slack cannot return when

To: Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH]:libxl__get_free_memory_slack cannot return when creating a vm by xl
From: "Jun Zhu (Intern)" <Jun.Zhu@xxxxxxxxxx>
Date: Mon, 27 Sep 2010 11:58:01 +0100
Accept-language: en-US
Acceptlanguage: en-US
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 27 Sep 2010 03:59:49 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <alpine.DEB.2.00.1009271136220.2864@kaball-desktop>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <433DDF91DFB08148BAD3FDB6FDDA314C9F3703C5FF@xxxxxxxxxxxxxxxxxxxxxxxxx>, <alpine.DEB.2.00.1009271136220.2864@kaball-desktop>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: ActeMEf7PzmOXmYaSGCPkOYhPOz+eQAAVNMy
Thread-topic: [Xen-devel] [PATCH]:libxl__get_free_memory_slack cannot return when creating a vm by xl

> How did you get in the state of having the target on xenstore but not
> freemem-slack?
> If you are using libxl this shouldn't be possible unless you mess around
> with xenstore directly.

I did not try to find where target is created. I think the target is created 
when dom0 starts. 
I do nothing related with the dom0 infomation in xenstore. 

But, in my opition, it is not enough to check dom0 memory info only by target. 
BTW, is it consistent with the xm? 

Jun Zhu
Citrix Systems UK

Xen-devel mailing list