VMware migration tool: we need your feedback!
-
@akaylee what is your current commit ?
this is the right one : 0f0c0ec -
@florent sorry, overlooked!
Yes, I was able to connect to my esxi host after updating to 0f0c0ec, testing migration right now
Thank you! -
@florent Just updated from sources, but my latest commit looks to be 0f0c0ec0d. Have I missed something ?
-
@andyh that's ok, I only pasted the start of the hash
As long as you're up to date on master, it should work (also it does not disable certifictae check for the whole process now )
-
@florent I still look to be receiving the same error, after updating to 0f0c0ec
write EPROTO C0D7ADA7B77F0000:error:0A000102:SSL routines:ssl_choose_client_version:unsupported protocol:../deps/openssl/openssl/ssl/statem/statem_lib.c:1987:Any further thoughts?
-
Gave this is a try earlier with some changes to my openssl.cnf
Sadly still coming across the same error, is there a minimum ESXi version that the import tool will connect to ?
-
Hi!
I did try the migration from the GUI for the first time.
The job did start and create a VM on XCP-ng. But there is no snapshot on the "VMWare-side" and there is no progress on the import.The job did start and XO-tasks is now showing "importing vms, duration a few seconds, status green"
There is no "cancel" option.
On the XCP-ng-SR, there are the new disks, but they are empty.
Do you have any idea, what I did wrong and how I can proceed?
Tested on XOA on latest stable
Thank you and best wishes
-
@KPS is there anything in the log ( journalctl ) ?
we can't migrate live data. Is the VM running ?
-
@florent
Sorry, that was the problem.
I was mislead by the wording "Source VM stopped before the last delta transfer (after final snapshot). Needed to fully transfer a running VM" in the GUI. -
O olivierlambert moved this topic from News on
-
Hi!
I am still struggeling with the VMWare migration tool.
According to the docs, it should be possible to "warm-migrate" a VM, but when I try to, I am getting errors:
"message": "500 Internal Server Error https://vcenter/folder/InetTS00_U20.04/InetTS00_U20.04-flat.vmdk?dcPath=HZ&dsName=OpenE-2_vmware-1_LUN2",What is the "right" way to migrate a running VM?
-
@KPS It should, but there are some case where the esxi lock all the files of a VM, and other where it only locks the last snapshot. We're still working on the exact limit, what is the version of esxi used ? what storage do you use ( local VMFS, iscsi, NFS, ... ) ?
In parallel we're putting the finishing touch of a huge change that give a big speedup. that way the penalty of stopping the VM will be lighter. You can test by switching to the branch xva_generation
https://github.com/vatesfr/xen-orchestra/pull/7323closed Import disks from ESXi to XCP-ng using XVA format #7323
-
@florent
Thank you for your answer. I am using vSphere 7 with iSCSI-storage.
Can you give me a hint on the "most stable" way to migrate? -
@KPS the most stable is always to stop the VMs
Trying to warm migrate a running VM between different hypervisor is always tricky, if not brittle, and we work to harden this process, define more clearly the limits and extends the possibilty (for example vsan)What are the rough sizes of the VMs ? how many VM ? What is the timeframe of the full migration ?
Do you think you can give a try to the xva import on a stopped VM ? on some of my tests, this migration is completely saturating my network link and my disks, as shown in the PR. The fastest way is to have the XO doing the migration directly in the ESXI. As an additional bonus, the disk produced is thin
-
When migrating VMs from ESXi, the CPU count and Memory allocation is taken over to XCP-ng.
That's all fine for me.
However, after import, the static min memory allocation cannot be reduced.
Is there a workaround?[02:56 xcp01 ~]# xe vm-param-get uuid=... param-name=memory-static-min
8589934592
[02:57 xcp01 ~]# xe vm-memory-static-range-set uuid=... min=4294967296 max=8589934592
The dynamic memory range violates constraint static_min <= dynamic_min <= dynamic_max <= static_max. -
If you want to change the min, just change the min not the whole range
-
Hello Olivier
Min value is deactivated and not changeable via GUI.
However, I found out, that the static max value can be changed below the currently set static min value. (looks a bit strange to me?)
Example:
before change
=> min 8GB max 8GB
change max value via GUI to 4GB
after change
=> min 4GB max 4GB
Then change the max value to 8GB again.
=> min 4GB max 8GBBest regards
Thomas -
Yes, because there's no reason to modify the static min. I was asking why are you trying to change the whole range via the CLI.
But first, what do you want to achieve functionally speaking?
-
To be able to start with dynamic memory at 4GB (min max) for the Windows Guest.
And then if needed, to be able, to expand to 8GB (min max) on the fly.
However, it seems, that the Windows Guest (2022 Server) always sees static max correct? -
Do you really need dynamic memory? I would prefer to avoid it if you can. Each migration will deflate the VM to the dynamic min, which is a cause of a lot of crashes and migration issues (if not taken into account, eg dynamic too low vs current usage). Keep it with static as far as possible.
-
Ok. Thank you for the advise.
Will follow as recommended.
Best regards
