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

Re: [Xen-API] ha-restart-policy =1, 2, 3 invalid for latest version of Xenserver

  • To: John Else <john.else@xxxxxxxxxx>, "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>
  • From: Pankaj Kumar Biswas <pankaj.kumarbiswas@xxxxxxxxxx>
  • Date: Tue, 13 Dec 2011 17:05:54 +0530
  • Accept-language: en-US
  • Acceptlanguage: en-US
  • Delivery-date: Tue, 13 Dec 2011 11:37:07 +0000
  • List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
  • Thread-index: Acy5fcxm66dUJP26RwW43aBbU+HWFQAAHZ6AAAKSHIAAAJOIUA==
  • Thread-topic: [Xen-API] ha-restart-policy =1, 2, 3 invalid for latest version of Xenserver

Thanks a ton !! .  Really appreciate the quick response John. Please do let me know when the xapi-document gets updated.

Thank you once again.





From: John Else
Sent: Tuesday, December 13, 2011 4:54 PM
To: Pankaj Kumar Biswas; xen-api@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-API] ha-restart-policy =1, 2, 3 invalid for latest version of Xenserver


> In Xenserver 6.0 (boston release) ha-restart-policy we cannot set to 1,2 or 3 ...only we can make it to best-effort and restart..


> Is it true?? If yes may I have the reason to do so??  Do we have any documentation regarding that??


Hi Pankaj,


The HA API was changed in XenServer 6.0 – there is a new VM field “order”, which is used together with ha-restart-priority to define a VM’s HA behaviour.

Where previously you would have set a VM’s restart priority to 1, you would now call:


xe vm-param-set uuid=<vm-uuid> ha-restart-priority=restart order=1


The order field can hold any non-negative 64 bit integer, and VMs with a lower order will be restarted first after an HA failover.


It looks like the administrator’s guide still refers to the old API – I’ll see about getting this updated.





xen-api mailing list



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