XOA is allways halted after the machine is rebooted
-
Greetings,
I am very new to XCP-ng. I enabled "auto power on" from web interface. However, my orchestrator's status is halted after each time the machine is rebooted.
Is there an option to make it "always on" after the boot. I am looking for a solution except defining a service file for this purpose.
Thanks in advance
-
Instructions
Set the "other-config:auto_poweron=true" parameter on both target VM and resource pool:#xe pool-param-set uuid=<pool_UUID> other-config:auto_poweron=true #xe vm-param-set uuid=<vm_UUID> other-config:auto_poweron=true -
@splastunov is correct. However, this can actually be enabled in XOA from the pool's Advanced tab, so no need for the CLI in this case.

-
@Danp said in XOA is allways halted after the machine is rebooted:
@splastunov is correct. However, this can actually be enabled in XOA from the pool's Advanced tab, so no need for the CLI in this case.

You mean the VM's Advanced tab.

-
@DustinB No, I would have said the VM's Advanced tab if that is what I had meant.

Did you look at the pool's Advanced tab?
-
@Danp yup

-
It's available in latest release channel.
-
@splastunov said in XOA is allways halted after the machine is rebooted:
xe vm-param-set uuid=<vm_UUID> other-config:auto_poweron=true
Thank you very much for detailed reply. It worked.
All the best
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