I'm having very fun testing this out. And you've really got something with extreme potential here. And I am very impressed. Thank you!
So far I've noticed a couple of things, both very small and medium in size. And I've tried to collect my initial thoughts below.
v2v xo6 thought
"next: mapping" is far down, when browsing "ALL". Could be remedied with placing it up at the top. With the header fixed at the top as well.
Consider showing what networks are attached in the VM-list.
Further suggestion could be to look into some smart-mapping. A simple (not saying the implementation would be easy, but the matching algorithm), that matches source-VLAN vs target-VLAN.
Have a V2V settings page, where many defaults could be set. Examples are:
Tags: Although you can click into each VM that is supposed to be migrated. Doing so for hundreds of VMs would be tedious very quickly. So an on-masse applying of tags would be great. (yes I'm aware there is a notice specifically about tags.
Deciding what would be the active default. Such as example deciding if Docking and "Start the VM on XCP-ng" would be pre-checked or not (current default).
Concurrent VMs
Incorporate an option to set if a VM should be booted with BIOS or UEFI. Perhaps be able to match with vmware-source?
When creating a migration, there is no way to discard already existing list, except for continuing with existing list and clear it inside.
When a migration is underway. It would be nice if the migration task for that VM would show up under the Tasks-tab for that particular VM as well. Not just in the "Tasks-section for XO"
Questions:
When importing a VM. The task for that particular VM has a percentage counter for its import. This does not seem to work. So my question is, what is the percentage of completion based on?