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-cim

Re: [Xen-cim] XEN CIM memory allocation.

To: "Szymanski, Lukasz K" <Lukasz.Szymanski@xxxxxxxxxx>
Subject: Re: [Xen-cim] XEN CIM memory allocation.
From: Tej <bewith.tej@xxxxxxxxx>
Date: Wed, 23 Jul 2008 20:41:30 +0530
Cc: "xen-cim@xxxxxxxxxxxxxxxxxxx" <xen-cim@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 23 Jul 2008 08:11:34 -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:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=luW3+q4kad0g7LlsXqPoCH5wvqFRXuoroVggDGizpOk=; b=bMHBMp5R9RYVsoxStA2Nau5QFOL8NhGWzkGPM4KUXfTi/5THn2t83N46I1cPgZr5T+ O3xWyucbOnbZgd2Htj8wSdnPxeoSImt4oTpZ7MdAog1MUZJ+Xg02frecg/0IRZtjD6e3 EFQA/B4TyVNH7U7pHeSBfvIJYH/I73+u0O01A=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=CarrVPnUoWbrxn92OqDegR+fkCCbMfmTxVZa9OHcUSVIlBk0+vmCPlp2TQANjn+2vS LiyHrjPJBCX9QHoNkTjBuCku9LxsldbF94kHumD6scX/aNuGvtt3ahoC6wlhW86ft7tu Fey4zfc/mFEdUGknSRYTDo+EDWhr9jkIKGL6Q=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <F089913638199841958E00B22EF169880AC1CE63C6@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-cim-request@lists.xensource.com?subject=help>
List-id: xen-cim mailing list <xen-cim.lists.xensource.com>
List-post: <mailto:xen-cim@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-cim>, <mailto:xen-cim-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-cim>, <mailto:xen-cim-request@lists.xensource.com?subject=unsubscribe>
References: <f1c9d250807212205x5f6dd91fn1877a55d01203250@xxxxxxxxxxxxxx> <F089913638199841958E00B22EF169880AC1CE63C6@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-cim-bounces@xxxxxxxxxxxxxxxxxxx
thank you.

I will post the question on libvirt-CIM.

-TEJ

On 7/23/08, Szymanski, Lukasz K <Lukasz.Szymanski@xxxxxxxxxx> wrote:
> Tej -
>
> This group has been inactive for over a year ... You would be better off
> posting to the libvirt-CIM group http://libvirt.org/CIM/
>
> -----Original Message-----
> From: xen-cim-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-cim-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Tej Parkash
> Sent: Tuesday, July 22, 2008 1:06 AM
> To: xen-cim@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-cim] XEN CIM memory allocation.
>
> 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
>

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

<Prev in Thread] Current Thread [Next in Thread>