Sat Feb 28, 2015 11:30 pm
StarWind V2V converter is compatible with multiple hypervisor products. Here's the list of supported virtual disk formats:
· VMware growable image. Designed to run in VMware Workstation`s environments. Disk space for this image is allocated on demand, so disk size of this image grows over time. It has *.vmdk extension.
· VMware pre-allocated image. Designed to run in with VMware Workstation`s environments. Disk space for this image is allocated at the moment of its creation and is fixed. It has *.vmdk extension.
· VMware ESX server image. Designed to run in with VMware vSphere environments. Disk space for this image is allocated at the moment of creation and it is fixed. It has *.vmdk extension.
· Microsoft Virtual Hard Disk growable image. Designed to be used with Hyper-V virtual machines. Disk space for this image is allocated on demand, so disk size of this image grows over time. It has *.vhd extension.
· Microsoft Virtual Hard Disk pre-allocated image. Designed to be used with Hyper-V virtual machines. Disk space for this image is allocated at the moment of its creation and is fixed. It has *.vhd extension.
· Microsoft VHDX image. Designed to be used with Hyper-V 3.0 virtual machines. Disk space for this image is allocated on demand, so disk size of this image grows over time. It has *.vhdx extension.
· Raw Image (.img). This image is format is suitable for StarWind Virtual SAN™, Disk space for this image is allocated at the moment of its creation and is fixed. It has *.img extension
I hope that helped!
Best regards,
Anatoly Vilchinsky
Global Engineering and Support Manager
www.starwind.com
av@starwind.com