Hi! I'v been testing Hyper-V to ESXi VM/disk migration. What I noticed is that when I use the CLI (V2V_ConverterConsole.exe), network transfer speed is about 0.5Gbps. When I do the exact same migration job with Console (V2V_Converter.exe), network transfer speed is around 1Gbps. I tried everyway ar...

Each drive is independent from what I can see in VCenter. It definitely is strange but I am fine with moving each drive during the course of the day. Thank you and the Starwind team for creating such a useful tool and being so responsive on the forums. I have successfully migrated hundreds of VMs u...

No. StarWind V2V does not support 8 KB allocation units. I searched through StarWind documentation but could not find any details on what they support. So, before I embark on re-formatting my CSVs, I am wondering if this answer is definitive? CynthiaGutierrez, with all due respect, I see you are a ...

Thanks for the update. I find it interesting that StarWind does not support 8kb allocation units when it is the default allocation size from Microsoft. I am curious what the reason for that it. Now I need to move VMs off my new, six 20 TB CVS and format them with, ummm wait What allocation size does...

StarWind V2V Version: 9.0.1.848 (also observed in 9.0.1.772) Environment: Source: VMware ESXi 7.0.3 Destination: Windows Server 2022 Hyper-V Cluster with CSV (Cluster Shared Volumes) Storage: Pure Storage FlashArray presenting 20TB LUNs Conversion Method: StarWind V2V GUI (Console/CLI not yet tested...

ok thanks for the update. By the way, is the bug fix I requested actually on their timeline and/or is it low priority? Sorry to push you, it has been three months since I reported this issue. I am just trying to determine if it is worth for me to wait for them to fix it. Otherwise I could do somethi...

Any update?
Is there a newer version now?
I am running version 9.0.1.772

Greetings!
Some time has passed, I was wondering if there has been any progress/update on fixing this issue?

We really need this feature to be fixed.
Thank you!

-Raj

Greetings!

Is there any possibility of getting this issue fixed soon?

-Raj

Do we have any update or feedback from the dev team about this?

Just looking to set my own expectations of timeline on a fix.

Additional observation:

I just tried doing a multi disk VM conversion using the GUI version of V2V.
It made all the disks thin and the VM boots fine too in HV.

So if the GUI can do it, the CLI probably can do it too. Just its code needs to be fixed.

ok thanks for reporting to the devs. Of course, this will take time, and we are under pressure to migrate lots of VMs ASAP.

What would you suggest, as an alternative strategy for the CLI scripts or tool?

oh right. Sure: They are all thin.

We make all VM's disks thin here. That is why the VMs after conversion by SW need to be all thin also.

Thanks for responding.

The source VMs are running on VMware 7
Hypervisor: VMware ESXi, 7.0.3, 24585291
VM OS: Windows Server 2019 and above.

We have lots of VMs with multiple drives but here is an example of a config

https://imgur.com/a/UEJuLo5

Hello StarWind Team, I've discovered an inconsistent behavior with the V2V Converter CLI (version 772) when converting VMs with multiple disks from VMware ESXi to Hyper-V. Problem Description: When converting a VM with multiple disks using out_file_type=ft_vhdx_growable, the conversion creates incon...