XCP-ng Centre 20.04.01 - VM Autostart on Server Boot not working
-
That's another good reason to use only a support XCP-ng client
-
@olivierlambert Is XCP-ng Centre no longer supported technically? i.e. only support is for XOA or XO?
-
@MichaelCropper XCP-ng Center as never been supported by Vates it's only a community tool
-
-
Good to know, thanks @olivierlambert and @Darkbeldin
What is the correct process for submitting bugs for XCP-ng Centre then? I'm assuming here, https://github.com/xcp-ng/xenadmin/issues ?
-
@MichaelCropper autostart in xen center is not a bug but a feature
In Xen Center, apart from enabling autostart of a vm you also need to manually (cli) enable the autostart-option on the server.
Xen Orchestra does enable this automatically when not yet enabled on the server when setting autostart for a vm.
-
@HeMaN
ah yes of course... a well designed 'feature' to not work unless one clicks heels together three times That sounds like you're right though, it's probably that XCP-ng Centre simply doesn't automatically turn this on.
As with anything XCP-ng related, no-one should need to work at the command line to basic tasks. Guess that's why we have XO to be a better supported platform over XCP-ng Centre.
The irony being, on initial setup - it's easier to install XCP-ng Centre to point to XCP-ng to set up a VM to install XO
Equivalent of using Internet Explorer to install Google Chrome or Firefox back in the day. -
If you go on your freshly XCP-ng installed host URL, you can deploy XOA from there.
Also, for people who are still against using XO for whatever reason, we are doing XO Lite that will be a small/embedded web UI inside each host.
-
@olivierlambert That's actually what I ended up doing which was very handy (eventually as part of the learning curve).
I've had so many different configurations and testing with this stuff. What I found was the easiest route to get to play around with everything was essentially;
Physical Server > Install XCP-ng Server via USB > (Physical Networking Magic, massively dependent on individual setup) > XCP-ng Centre on Windows laptop for ease of 'seeing' XCP-ng Server > Get IP of XCP-ng Server, put into browser and use the XOA Quick Setup > Get 95% of features out the box, but important ones to play with missing > Use XOA to Setup VM for XO > Install XO on new VM > Get full access.
Really interested to hear about XOA Lite once that is ready though, sounds exciting.
XOA is great, but when it's a case of people testing and playing around, the limiting features (allbeit minimal, but important) are just that extra hurdle to jump through which causes pain and friction to the learning curve. Not really sure what is the best approach to solve this to be fair though, since there is that fine balance between open source and commercial implementation opportunity. Even with other higher level technology layer systems such as WHM/cPanel, even they haven't figured out this perfect balance as it's still a pain to have that floating completely open licence when migrating from A to B and going through the usual pain on the journey. Usually ends up paying for duplicate licences for a short period of time which is a pain. It's a fine balance for sure.
-
What kind of features? XOA Free should be enough to manage your VMs/hosts
-
@olivierlambert I can't quite recall the details as once I got XO set up I just use that rather than XOA Free version, I must have needed to play with some of the features that get locked down after the free trial - I can't remember exactly what they were, you'll probably know what those features are off the top of your head.
From memory though the biggest challenge I had was that I just didn't have enough time to get under the skin within the limited time for the trial period. When I'm exploring any technology, I tend to play with something for many months as it's often only ~1-3% of my time I can carve out to play with things so I rarely dedicate solid blocks of time to use trial periods to have any value - that's just me though with any trial period of any software which usually puts me off from progressing (mainly with commercial non-open source software).
Thankfully though now I've got XO set up, I can play with it as much as I need in the small pockets of time to get familiar with the finer details of how it all works.
-
We are always happy to provide more time to test when people are asking for it
Also, no "basic management" features should be missing in XOA Free.Let me know if you want a longer XOA trial
-
Thanks @olivierlambert that's always good
I'll take you up on that offer probably in about 6 months once I've figured out XO, then I can understand how XO and XOA are different. It's taken me a couple of years to get to this point of understanding with all the supporting knowledge required even before XCP-ng is even installed
-
That's why we sell support
So you don't have to understand everything (which is OK I mean, but if you don't have time, we are here for you!) -
Im having issues with the auto start feature.
If i experience a power loss on my server, the VMs dont start. Is this expected behaviour?
My server stays on 24/7, so i dont have not been able to check that autostart functions on reboot, however i can check that too if needed.
Runningxe vm-param-list uuid=<uuid> | grep other-configgives me the expectedauto_poweron: true;. Is there anything else to check? -
Is that enabled on the pool level?
-
@olivierlambert Hmm im not sure how i can check that. It was configured via XOA, however the VMs were live migrated from a different host which has been decomissioned. Maybe there is some pool HA going on?
-
@olivierlambert HA is disabled on the pool level
-
@mathiashedberg try, with xo/xoa, toggeling autostart off and then on again for 1 of the vm on the new host so xo will also activate the autostart option at the (new) server if it was not already enabled
-
Hello,
You need to config pool poweron first, then vm poweron.
xe pool-param-set uuid=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX other-config:auto_poweron=truexe vm-param-set uuid=AAAAAAAA-AAAA-AAAA-AAAA-AAAAAAAAAAAA other-config:auto_poweron=true
