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

[Xen-devel] Xen Memory allocation.

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Xen Memory allocation.
From: "Tej Parkash" <bewith.tej@xxxxxxxxx>
Date: Tue, 22 Jul 2008 11:15:32 +0530
Delivery-date: Mon, 21 Jul 2008 22:45:55 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=gfFOtqsOHeuD5Vjen3+PqlAnU/2C7v0hNFUrDcFwdso=; b=kXRmm03cCbbrmEwSrx//m1EsRxg6hofGBF+T9CGXXKiEWLfMOz4obNTu9lu4Q5Qkn1 YXHZ6z4PhGDDFUcdLM4SPhyBgAZkRep4CjpWCa7d/G+hnP0r4aUXkWsRnLyn+1wuADKx 9m6PwBxCH3SzLBZTfjnuH23Zjsjc691cAo59c=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=h5Q95kjwjMSoHvD4RrQYFCqCSDm2RxRElHwOdiK8OBEFZVoIjgJkClN8ZDY/DqRtyg gwxh2ykqwSfwbxOlHk+luzWm+AjeyEID7v+T0OggY7wxmSw4A7TZG9z0gpV00DtAcu43 znasqnmF913Ixy7RZv8seQ2ZH9lQTOcz7XOvg=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I am trying to understand the xen provider implementation for Xen VM
lifecycle management.
Does the xen provider (libvirt/xen-cim) uses the xenstore to
access/change the configuration information regarding the domains.
e.g if Xen Client has to changes the memory allocation for any of the
domain (i assume discover of domain/UUID/domid is already done)  then
can it uses xenstore to perform the operation in following way.

*xenstore-write /local/domain/domid/memory/target  <value> (balloon watch node)*
Or Is there any other method to perform the same operations

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Xen Memory allocation., Tej Parkash <=