V2V migrated VMs don't autostart

jr-m4

I'm at the moment doing alot of test with V2V (applause on getting rid of the vddk-dependency btw )

However, what I'm noticing is that the migrated VMs don't automatically start when the import has completed. This is contrary to current documentation.

Is this a potential bug? Or am I missing something obvious?

PS: The imports are all sucessfull. It's just the auto-start part that I'm noticing doesn't work.

Cheers!

Commit: dc573

Template used for testig is: Rocky Linux 9

tjkreidl

@jr-m4 Hi there... A warm VMware V2V migration should indeed start up by itself, so I'm not sure what you are experiencing is normal. This is documented, as you've probably seen, at: https://xcp-ng.org/blog/2022/10/19/migrate-from-vmware-to-xcp-ng/

That said, in addition, if you want your imported VMs to start up automatically every time your XCP-ng server or pool boots up, you have to enable the Auto Power On / Auto Start configuration.

For this to work, it must be enabled at both the Pool level and the individual VM level.

Method using Xen Orchestra (Recommended):
Go to the VM tab, select your imported VM, and navigate to the Advanced view.
Toggle the Auto power on switch to ON. (XO will handle configuring both the host pool and the VM flags for you).

Or alternatively, via the bash shell:
--> Get your Pool UUID
xe pool-list

--> Set the auto_poweron parameter to true
xe pool-param-set uuid=<POOL_UUID> other-config:auto_poweron=true

Enable Autostart on the Imported VM:
--> Get your VM UUID
xe vm-list name-label="Your_Imported_VM"

--> Set the VM param to true
xe vm-param-set uuid=<VM_UUID> other-config:auto_poweron=true

jr-m4

@tjkreidl

Thanks for your long post. I hope someone else will find it helpfull.
However, I am pretty much reporting that the autostart after importing with V2V might be buggy at best or broken at worst. Not the autostart after boot part (that works).

Cheers

jr-m4

Further testing:

Testing with newer commit: 27882fb1dcd24fc5257835e60b3fa1002e4e885c
Still same results.

I've tried with both original VM powered on, and off. No change in end-result. The VM imports properly. But it doesn't power on automatically as expected after the import has completed. Manual powering on is then needed to be performed.

I'm only importing 1 VM at a time. And I've tried with the field Number of VMs to import in parallel both at the default value of 2 and reduced to 1. No change in behaviour from this either.