1
UPGRADING
Choose the product:
Release Notes

Here, at StarWind, we don’t have broken things. But perfection has no limits, which is why we continue to build upon our existing solutions and develop them to be up-to-date. We listen to customer feedback, conduct periodic tests, and follow trends in business and technology to keep delivering what hyperconvergence can offer best.

You can find the latest updates regarding the product of your interest below.

V2V Converter
2
ANNALS OF DEVELOPMENT

V2V Converter Release Notes

Download
Version 9 (build 554)
01 October 2024
  • Added qcow2 V3 format support
  • Added CLI support for the disk conversions to and from Proxmox
  • Added support for conversion of RAW disk images (.raw)
  • Improved performance for conversions from Hyper-V to ESXi.
  • Fixed a performance issue with conversions to and from Proxmox using the qcow2 format.
  • Resolved issues with hot VM conversions from Hyper-V.
Version 9 (build 509)
17 June 2024
  • Added support for converting VMs to and from Proxmox
  • Improved oVirt (OLVM and RHV) functionality

Known issues:

  • Conversion to and from Proxmox using qcow2 format can be extremely slow
  • qcow2 version 3 virtual disks are not supported. Support will be added in the upcoming releases.
Version 9 (build 444)
11 April 2024
  • Added support for converting live VMs from ESXi to Hyper-V.
  • Added support for converting live VMs from Hyper-V to Hyper-V.
  • Added support for migrating VMs directly from oVirt hosts.
Version 9 (build 413)
31 January 2024
  • Added support for converting VMs to and from Oracle VirtualBox.
Version 9 (build 369)
08 November 2023
  • Fixed the Physical to Virtual (P2V) conversion of physical hosts to Hyper-V VMs.
  • Resolved issues related to the Virtual to Virtual (V2V) migration of VMs to oVirt hosts.
Version 9 (build 364)
23 October 2023
  • Added support for converting Oracle VM VirtualBox VDI disks (both growable and pre-allocated).
  • Introduced the ability to migrate VMs directly to oVirt hosts.
  • Upgraded the AWS SDK to the new Amazon API version.
  • Added support for "hot" VM migration from Microsoft Hyper-V to VMware ESXi hosts. (Please note that “hot” VM migration between Hyper-V hosts is not supported in this release and will be addressed in the next one).
  • Modified command-line parameters to maintain consistency in disk parameter standards.
Version 9 (build 268)
16 November 2021
  • New implementation of VHD/VHDX container operations for better portability and compatibility.
  • Azure: added support for Generation 2 Virtual Machines.
  • Added support for converting 4kn disks to VHDX format.
  • Fix for command-line mode: in some cases, the utility was not setting a correct exit code. Now, it returns an exit code for all scenarios.
  • Added processing of Hyper-V virtual disks with checkpoints.
  • Added support for operations with virtual disk files located on SMB shares.
  • Fixed creation of VHDX virtual disks with a size greater than 64TB. There is still a known issue with the P2V scenario for machines with disks larger than 64TB, which will be fixed in later updates.
Version 9 (build 242)
15 February 2021
  • Added operation using hypervisor snapshots to have a consistent state of the virtual machine when converting a running VM from VMware ESXi server and/or Microsoft Hyper-V Server.
  • Added support for VMs operation using VMware vCenter access.
  • Added check for the system boot type (BIOS-MBR or UEFI-GPT) to block incorrect conversion types.
  • Fixed the operation of the progress bar for the process of conversion to a VMDK Workstation pre-allocated image.
Version 9 (build 202)
12 February 2020
  • Added functionality for converting virtual machines in the Amazon Web Services cloud. The Converter now processes only the system disk of the machine. When moving a virtual or physical machine to AWS, please, consider the following requirements: https://docs.aws.amazon.com/vm-import/latest/userguide/vmie_prereqs.html. It is planned to automate some of these procedures in the later updates.
  • Added support for VMware vSphere 6.7 update 3. Also, successfully tested with the vSphere 7.0 release candidate.
  • The Windows Repair Mode feature has been re-enabled for the conversion of Windows machines in VMDK and VHD/VHDX containers, except for the case when UEFI boot is configured in the system.
  • The UI for setting the conversion options has been made more accurate and more nuanced for each type of hypervisor.
  • V2V Converter now checks the state of the virtual machine to ensure that the VM selected for the conversion is not running.
  • Fixed the processing of the QCOW virtual disk format when it is selected as a source image. It could produce a broken image in some circumstances in the past.
  • Improvements and fixes in the UI.
Version 9 (build 167)
27 August 2019
  • Added functionality for converting virtual machines in the Microsoft Azure cloud.
  • Added option for converting physical and virtual disks to thin-provisioned VMDK on remote VMware ESXi server.
  • Fix for operation with remote Microsoft Windows 2012 R2 - check for available management interfaces added.
  • Added connection restore functionality for operations with a remote Hyper-V server.
  • Changed output for the V2V_ConverterConsole.exe console application. The result is returned as an error code, 0 for success. Text output is directed to stderr and stdout streams.
Version 9 (build 110)
21 January 2019
  • Added logging to text files allowing to track application operations and simplify issue analysis.
  • Changed vSphere management client implementation for better handling of API call errors and connectivity issues.
  • Added support for vSphere VM RDM disks.
  • Added details about the bootloader type and VM generation for Hyper-V VMs to VM descriptions.
  • Fixed processing of vSphere VMs with more than one virtual disk.
Version 9 (build 75)
12 November 2018
  • Added functionality for converting virtual machines between hypervisors: migrate a Hyper-V VM to an ESXi server or an ESXi VM to a Hyper-V host. Conversion does not alter the basic VM settings: the number of CPU sockets, amount of RAM, the number of network adapters, and the number of disks. Note that network adapters must still be configured in hypervisor after conversion. vCenter Server will be supported starting with the next release.
  • Added functionality for converting physical machines to virtual ones on Hyper-V and ESXi servers. Just start the utility on the physical machine and convert it to the virtual one located on the remote hypervisor server. The utility uses VSS snapshots while reading disk data from the live machine to preserve data consistency. Physical-to-virtual machine conversion is possible for the following OS: client Windows – from Vista through Windows 10; Windows Server– from Windows Server 2008 R2 through Windows Server 2016.
  • Added functionality for converting a physical disk or volume to a virtual disk container. It is possible to convert volumes selectively to save disk space (thin provisioned containers) and time (thick provisioned containers).
  • Added support for ESXi servers up to the 6.7 version. Remote server access functionality works for ESXi servers from version 5.5 through 6.7. VMDK containers of older ESXi versions are supported too.
  • The utility has been refactored and is built on x64 architecture, so it requires an x64 OS for operation starting from this version.
  • Fix for processing KVM QCOW2 containers: cluster size changed to 4k, the operation for large disks fixed.
Version 8 (build 170)
19 April 2018
  • Fix for an error that occurred when trying to convert a file of a running Hyper-V virtual machine.
  • Fix for the "Internal error (8) [997]" error: a conversion error occurred when VHDX was a destination format and the source image size exceeded 2TB.
  • Fix for Image Format page skipping in the wizard, in case of a remote Hyper-V Server serving as a source. It required a step back to select the destination image format.
  • Fix for moving back in the wizard since it skipped pages in some cases.
  • Fix for an error that occurred in the wizard for incorrect Hyper-V hostnames.
  • The ability to create a new folder on an ESX server when selecting the destination location has been added.
  • The option to convert a new file without restarting the wizard has been added.
Version 8 (build 166)
31 October 2016
  • Added functionality for converting VMDK files directly to VMware ESXi Server.
  • Now it is not necessary to use local machine as a destination for VMDK file and copy it to ESXi server after conversion.
  • Added functionality for converting VHD/VHDX files directly from MS Windows Hyper-V Server.
  • Now it is not necessary to copy source VHD/VHDX file to local machine to convert it.
  • Added functionality for converting VHD/VHDX files directly to MS Windows Hyper-V Server.
  • Now it is not necessary to use local machine as a destination for VHD/VHDX file and copy it to MS Windows Hyper-V Server after conversion.
Version 8 (build 165)
22 July 2016
  • Added functionality for converting VMDK files directly from VMware ESXi Server.
  • Now it is not necessary to copy source VMDK file to local machine to convert it.
Version 8 (build 162)
23 June 2015
  • Added support for vmdk stream-optimized format. This file format is used for storing virtual disk images with OVF templates for ESX.
  • Added support for QCOW2 image format for QEMU hypervisor.
Version 8 (build 161)
17 February 2015
  • Added support for MS VHDX container format. It requires running on Windows 8/2012 or higher version of Windows.
  • Windows Repair Mode may be activated for converted image, allowing virtual machines to adapt to hardware environment of new hypervisor automatically.
  • Command-line utility extended to support VHDX format and repair mode option. New style of GUI in V2V Converter Wizard.
  • Help file added to installation.
WOW NEWS
Achieve true business agility with StarWind.

Our products are now available at flexible subscription payments simply as part of your OpEx.

Request Terms