Before conversion you could rename your disks in VMware with unique prefixes or suffixes that ensure even if the last character is truncated, they remain distinct. For example renaming /vmmigtest.vmdk/ to /vmmigtestdisk1.vmdk/ and /vmmigtest_1.vmdk/ to /vmmigtestdisk2.vmdk/ After the conversion man...

When doing a conversion of a VM from VMware to Hyper-V, I've noticed that the current version (9.0.1.554) is cutting off the last character of the diskname. So if the disk in vmware is called "vmmigtest.vmdk" the converted VHDX is called "vmmigtes.vhdx". This isn't really an issu...

Makes sense…but I would have thought the same thing would happen to an offline conversion as well. I guess there’s something extra happening behind the scenes to make hot conversions work that is enough to cause issues with them

It would seem I owe an apology! My assumption that the VMware tools had no part in the issue was infact wrong. When I uninstalled the tools and then did a live migration, the VM booted just fine in Hyper-V I'm still not sure I understand why removing the tools wasn't necessary when doing an offline ...

I changed the disk to being thick provisioned in Vmware and did the migration again, with the same result. I have noticed in diskpart in the recovery environment that the main partition was marked as read only. I cleared that, but that hasn't helped. I suppose I could attempt to recreate the bootloa...

It's not possible to recreate it as a Gen 1 VM as it's setup with UEFI and GPT disks in VMware, which aren't compatible with Gen 1 VMs

I see the boot circle animation and then it jumps to a “inaccessible boot device” blue screen after a few moments. It’ll reboot into this a few time before ending up in the recovery console. This only happens with a Hot conversion - the same VMs will boot just fine if they were converted “offline” I...

Thanks for the reply, I included these details in the original post but here they are again VM Guest OS: Windows Server 2022 Source: VMware 7.0.3 Destination: Hyper-V (Server 2022) I didn’t uninstall the VMWare tools first, but the converted VM doesn’t boot into the OS so I don’t think that’s an iss...

I'm currently using V2V converter 9.0.1.554. I'm trying to use the hot conversion/synchronize option to migrate a VM from VCenter (v7.0.3)/ESX host (v7.0.3) to Hyper-V (Server 2022, 20348.2700). When I try a hot conversion, the process succeeds but when I try boot the VM it boots to a bluescreen wit...

If the VM is turned on, then a Synchronisation option appears with the GUI that lets you start the conversion while it's still powered on.


Is there a parameter when using the command line tool that enables this as well?

I'm just starting a Vmware to Hyper-V migration and looking to try out StarWind V2V to move the VMs across. I'd like to use the command line option so I can more easily do multiple conversions at once but the documentation doesn't look to have been updated since the latest release - is there a comma...

Thanks, that's done the trick! Maybe that needs to be added to the documentation/sample scripts in future updates to make that a little clearer?

My question then is, where do I specific the Storage Account Name like you can in the UI as this seems to be required based on the error I'm seeing in the logs? The comments I've put in this post next to the arguments are only in this post for the sake of explaining what I've done. They don't exist ...

Thanks for the reply, For the region name I also tried "australiasoutheast" which is the region name that it's located in. I did see that thread you've linked but it doesn't really help with my issue as I don't see where I enter the Storage Account Name? This is where I'm getting the Acces...

Hi there, I'm trying to configure VTL Free to replicate to Azure storage via the sample VTLReplicationSettings.ps1 file. I've configured the parameters as follows: param($addr="127.0.0.1", $port=3261, $user="root", $password="starwind", $deviceName="vtl", $tar...