Thanks for your post and welcome to StarWind forum. Could you please explain what kind of issues you ran into?

Hi,

Great to read that Good luck with migration.

Thanks for your feedback. sync_from_first is to be used and it is a known problem. It should be addressed in the next build. Typically the event you shared points to the storage issues, however, here there might be difficulties with header/image creation that explains why only sync_from_first works....

Yes, you can continue using the system that undergoes P2V.
The converter makes a shadow copy of the disk so that data will be up-to-date in the resulting VHDX.

HI,

Welcome to StarWind Forum. Check this thread viewtopic.php?f=15&t=6763&p=36723&hilit=google#p36723.

Thanks for your update.

Thanks for your update. Did the error go away now?

Try marking sync_status 1 only the first occurance. Set the latter to 0.
Make sure to edit the files while StarWindService is stopped.
Last but not least, remove write back cache: should make such incidents less frequent.

Stop the service on both nodes. Go to HA config files and ser sync status value in the config to 1 for the section that corresponds to the device. Do for each decice. That marks HAs as synchronized. Start the service on the node where you marked the devices as synchronized and check the data. If dat...

Hi,

Make sure you allowed ssh in the VM.

Can you please share the conversion logs with us here?

Welcome to StarWind Forum.
Both are correct. It all depends on what you are after. You converted a physical disk/volume into a VHDX that can be used either to create a new VM or connected to an existing one.

Anatolii, Sorry for the delay. I also decided to simulate my situation again. I created a 2TB virtual disk (vhdx) using Windows tools. I created a partition on it that takes up all the space, format this disk and assign letter X:. I created several empty folders on the disk. Then did all the things ...

Sorry for the delay. try out_file_type="ft_vmdk_esx_pre_allocated" instead of out_file_type=ft_vmdk_esx_thin The error ERROR: RunConsole: VM V2V-VMWARE-01 not found. describes the situation where the software converts the file and attaches it to the existing VM but fails as the VM does not...

Hi,

Sorry for the delay.
StarWind V2V converter makes only one snapshot.
It can convert live VMs. Let me know if you run into any trouble.