VMware migration tool: we need your feedback!
-
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 -
Any plans to check how many vNICs there are and allow us to map each one correctly.
All of our vmware VMs have multiple vNICs and are in different port-groups.
Its not a major hassle to change them post-migration - just a nice-to-have.
-
You mean to map each VIF to each Network of your choice?
-
@olivierlambert - Yes, so when we do a V2V there is only 1 VIF listed to put the migrated VIFs in to, even if the VM has 5 VIFs
Is it possible to query each vmx and allow us to select a 'network' for each VIF that it has?
-
Question for @florent
-
@Riven said in VMware migration tool: we need your feedback!:
@olivierlambert - Yes, so when we do a V2V there is only 1 VIF listed to put the migrated VIFs in to, even if the VM has 5 VIFs
Is it possible to query each vmx and allow us to select a 'network' for each VIF that it has?
not for now
-
@olivierlambert I wanted to comment on this topic, we have migrated around 450 vms in 3 months using this feature, it really was a game changer and without it we were never able to make the step to XCP-NG. during the migration process we saw the feature being improved, overall speed and reliability were great. Compliments on this feature and i think it will help a lot of future customers migrating to XCP-NG.
-
Migration fails, here is the raw log;
{ "id": "0lxdi3kqv", "properties": { "name": "importing vms 14", "userId": "9045a9e7-f9b2-44fd-81e9-02c1ea88b37b", "total": 1, "done": 0, "progress": 0 }, "start": 1718297723335, "status": "interrupted", "updatedAt": 1718298405138, "tasks": [ { "id": "c3bsox2ydxp", "properties": { "name": "importing vm 14" }, "start": 1718297723339, "status": "pending", "tasks": [ { "id": "lvtzb0k3sc9", "properties": { "name": "connecting to 10.x.x.12" }, "start": 1718297723341, "status": "success", "end": 1718297723756, "result": { "_events": {}, "_eventsCount": 0 } }, { "id": "n6tsha4ebu", "properties": { "name": "get metadata of 14" }, "start": 1718297723756, "status": "pending" } ] } ] }
-
@tcp_len We recently released a Vmware migration checklist that you can view here -- https://help.vates.tech/kb/en-us/37/133
Frankly, that log doesn't give us much to go on so you will need to provide more details if you want further assistance, ie:
- ESXi version
- Type of datastore
- Version of XOA or current commit if using XO from sources
- XCP host version; fully patched?
- Warm or cold migration?
- Does the VM have any snapshots?
- etc
-
- ESXI version 6.5
- Data Store - VMFS5
- XOA
- XCP - Welcome To XCP-Ng 8.2.1
- Cold Migraration
- No Snapshots
From the checklist posted, I should uninstall the Vmware tools before I attempt migration as well as run #yum update on the XCP host.