Understanding Auto Power On | Auto Start
-
Hey guys,
Looking for some help at understanding auto power on as the documentation possibly looks to need some refreshing.
https://docs.xcp-ng.org/guides/autostart-vm/From the Xen Orchestra, the guide does not mention the pool level it is only under the CLI that it mentions the pool level.
Just looking for some clarification.
In order for auto power on to function, we need to enable it on the pool level, and then per VM correct?
If you have auto power on enabled at the VM level and the pool level disabled, the VM level is ignored, correct?
What is actually triggering the power on?
Is it XOA or the host itself?
I am assuming the host itself, just looking for clarification if XOA VM was part of the systems that went offline, should we expect to see it auto power back on if it is set to auto power on.What determines the start order for auto power on when you have multiple VMs on a host?
Thank you!!
-
Hey guys,
Looking for some help at understanding auto power on as the documentation possibly looks to need some refreshing.
https://docs.xcp-ng.org/guides/autostart-vm/From the Xen Orchestra, the guide does not mention the pool level it is only under the CLI that it mentions the pool level.
Just looking for some clarification.
In order for auto power on to function, we need to enable it on the pool level, and then per VM correct?
If you have auto power on enabled at the VM level and the pool level disabled, the VM level is ignored, correct?
What is actually triggering the power on?
Is it XOA or the host itself?
I am assuming the host itself, just looking for clarification if XOA VM was part of the systems that went offline, should we expect to see it auto power back on if it is set to auto power on.What determines the start order for auto power on when you have multiple VMs on a host?
Thank you!!
Yes, it needs to be enabled at pool level and at VM level. I tried once at only enabling at the VM level and it didn’t auto power on, as it wasn’t enabled at the pool level, it started auto powering on once it’s enabled at both levels.
It’s configuring a XAPI value as this occurs at the Xen level (virtualisation server). Xen Orchestra is just making this value visible with a nice UI interface toggle.
-
As far as I understand, @john.c has it right: both the pool-level and VM-level flags need to be on for it to work.
On what actually triggers it (or what I think I understood): it's XAPI itself running on the host, not XO. XO is just showing you a toggle for a value that lives in the hypervisor config, so if XOA goes down it doesn't affect the auto-start behaviour, right?
For start order: I honestly don't know enough about this part to give a confident answer, but I think there's a
start_orderparameter in XAPI'sother-configfor each VM that controls it.
Someone more familiar with the internals here would know for sure. The main docs don't seem to cover it well, which might be worth flagging.https://docs.xen-orchestra.com/xo5/manage_infrastructure#auto-power-vm
https://docs.xcp-ng.org/guides/autostart-vm#with-the-cli -
@poddingue there is a notion of appliance too (group of VMs)
https://docs.xcp-ng.org/appendix/cli_reference/#appliance-commandswhere you can start/stop a group of VMs, never tried it, doesn't seem to have a boot order in the vAPP neither
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login