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

Re: [Xen-API] power state evaluation

  • To: "Uli Staerk" <Uli.Staerk@xxxxxxxxxxxxxx>
  • From: Tom Wilkie <tom.wilkie@xxxxxxxxx>
  • Date: Thu, 16 Aug 2007 18:52:56 +0100
  • Cc: xen-api@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 16 Aug 2007 10:52:29 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:in-reply-to:references:mime-version:content-type:message-id:cc:from:subject:date:to:x-mailer; b=ImohW5qx/FIbntqwIi78MhijCW3fHm1N0so86VoCkB9qOPguPRVFCkPUQQnbWM1c7+CvsEwRvnSwIS1299ow6yh2ZXUmVVIC8bVhrEorDfKYOpOvixLUhJn9F/zR6v5Cer/IXSUadC6s2B6XzMJL2/zxP1ADqGXUat1JA6l+nxw=
  • List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>

If I call VM.get_record() I get an key named

    [power_state] => Running

This is the power state of the vm ie running, halted, suspended etc.

If I fetch the metrics by VM_metrics.get_record() I get a similar information:

    [state] => Array
            [0] => running

These are the individual statues of the vcpus, ie running, paused, blocked etc

xen-api mailing list



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