P2V migration to Azure is very slow

[soontshirt]

Hello,
I have a physical Windows 10 system that I'd like to convert to run on an ESXi 7 host, but I'd like to have the two disks created as thin provisioned. I recently used the StarWind V2V convertor to migrate a laptop to the same host, but don't remember seeing an option that allowed me to specify thin provisioning for the target volumes.

I noticed in another forum post that thin provisioning is possible, and I was hoping someone could tell me where I should specify it throughout the conversion procedure. Thank you in advance for your assistance with this!

[yaroslav (staff)]

Hi,

I think the post contents are little bit different from what the title for the topic says.
Welcome to StarWind forum. While converting, there is an option for thin disks.
P.S. i'd rather not use thin disks due to performance hit and risk of overprovisioning.

[miltonbwilliam]

Hi,

From what you’ve described, this usually comes down to how the storage is being presented and synchronized between the nodes.

A couple of things I would suggest checking:

Make sure both nodes have proper network connectivity for the sync channel. Even small latency or packet loss can cause unexpected behavior.
Verify that the StarWind service is running properly on both sides and there are no replication errors in the logs.
Check disk configuration on both nodes — especially if one side is using different storage performance (SSD vs HDD), it can create inconsistencies.
If you’re using synchronous replication, ensure the network is stable and fast enough, otherwise try testing with async just to isolate the issue.
Also confirm that the devices are correctly added and connected on both hosts and not in a degraded or resync state.

If possible, share logs from both nodes — that would help pinpoint whether it’s a sync issue, network problem, or storage bottleneck.

Hope this helps.

[yaroslav (staff)]

Wrong product.