[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-cim] XEN CIM memory allocation.


  • To: xen-cim@xxxxxxxxxxxxxxxxxxx
  • From: "Tej Parkash" <bewith.tej@xxxxxxxxx>
  • Date: Tue, 22 Jul 2008 10:35:56 +0530
  • Delivery-date: Mon, 21 Jul 2008 22:06:01 -0700
  • 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=M+J1uliEYZeUsGJnp7nJDldcLK+5rmGg11+b+ZeRx9MzZ7hvmhYyPVs5VxWgTDkrFF A+Esst3iR8mZtyxTTwvxSA4Hiq4GWYtbV5SA4I/E6T45geY1GehL0OWTgUVeXGW+zbHu jAQhdhwoxLdMn5RyBs+Cp7RqEfceR03xkkOfs=
  • List-id: xen-cim mailing list <xen-cim.lists.xensource.com>

I am trying to understand the 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-cim mailing list
Xen-cim@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-cim


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.