Chapter 1. Migration Toolkit for Virtualization 2.8

MTV overwrites firstboot.bat with its own copy

In previous versions of MTV, MTV overwrote the firstboot.bat script in Windows. Consequently, user experience was degraded. With this release, the redundant firstboot script is no longer overwritten. (MTV-3218)

Installing drivers on firstboot sometimes fail with PnP service not available

In earlier releases of MTV, Plug and Play (PnP) service unavailability caused virtio driver installation failure while booting guest virtual machines that run Windows. As a consequence, users experienced boot failures of guest VMs. With this release, the driver package import issue has been resolved, allowing successful driver installation with the PnP service. As a result, users can now start guest VMs. (MTV-3042)

No IP address for Windows Server 2008 R2 VMware VMs after migration

VMware only: In earlier releases of MTV, the IP addresses of Windows Server 2008 R2 VMware VMs were not included in the migration data. This issue has been resolved in MTV 2.8.5 by packing the relevant virtio-win ISO in the virt-v2v container used for the migration. (MTV-1700)

VMs whose names contain uppercase letters not found by the search function on the Plan details page

In earlier releases of MTV, the search function of the Plans details page did not return VM names that contained uppercase letters. This issue has been resolved in MTV 2.8.4. (MTV-2348)

VMware disks named by using a PVC template are not sorted correctly

In earlier releases of MTV, VMware disks with names generated by using a PVC template were not sorted using the same method as the VM builder. This issue has been resolved in MTV 2.8.3. (MTV-2303)

Post-migration hooks do not run

In earlier releases of MTV, post-migration hooks failed to mount a ConfigMap API object. As a result, post-migration hooks did not run. This issue has been resolved in MTV 2.8.3. (MTV-2421)

MTV does not add a separator after the name of a PVC when a custom name template is used

In earlier releases of MTV, when a custom PVC template was used, the name of the PVC was followed immediately by the random alphanumeric characters that MTV generates to ensure that PVC names are unique. As a result, it was difficult to distinguish between the name the template generated and the random characters. This issue has been resolved in MTV 2.8.2 by MTV adding a hyphen (-) as a separator between the name generated by the template and the random characters added by MTV. (MTV-2257)

The static route gateway of Windows VMs is passed as the default gateway during migration

In earlier releases of MTV, the static route gateway of Windows virtual machines (VMs) was passed as the default gateway during migration instead of the actual default gateway. This caused VMs to be incorrectly configured. This issue has been resolved in MTV 2.8.2. (MTV-2408)

MTV does not list any VM that is part of a vApp

In earlier releases of MTV, any VM that was part of a VMware vApp was not listed. This issue has been resolved in MTV 2.8.2. (MTV-1153)

VMs with mutually exclusive spec values as source VM and destination VM cannot be migrated

In earlier releases of MTV, it was possible for a VM to have the spec value Running as a source VM with the spec value runStrategy as a destination VM. This caused migrations to fail because Running and runStrategy are mutually exclusive. This issue has been resolved in MTV 2.8.1. (MTV-2092)

The code base of MTV contains a deprecated value for a parameter

In earlier releases of MTV, the code base contained the deprecated value vm.Spec.Running, which caused some migrations to fail. This issue has been resolved in MTV 2.8.1. (MTV-2105)

Migrations using custom templates fail if a user-supplied name is too long

In earlier releases of MTV, migrations that used custom templates failed if a user-supplied was too long because it exceeded 63 characters. This issue has been resolved in MTV 2.8.1. Now MTV automatically truncates names that are too long. (MTV-2244)

User supplied template names are not validated against the RFC DNS1123 standard

In earlier releases of MTV, user-supplied template names were not validated against the RFC DNS1123 standard. This caused migrations of VMs with template names that did not conform to RFC DNS1123 to fail. This issue has been resolved in MTV 2.8.1. (MTV-2249)

Canceling the migration of a virtual machine causes the Plan controller to loop forever

In earlier releases of MTV, if the migration of a virtual machine (VM) was canceled, the scheduler of the Plan controller would endlessly reschedule it for migration. This issue has been resolved in MTV 2.8.1. (MTV-2287)

MTV fails to migrate VMs with template names that contain multiple periods

In earlier releases of MTV, a VM whose name contained multiple periods (for example, vm...) could not be migrated because its name did not comply with the application and support protocol RFC DNS1123. This issue has been resolved in MTV 2.8.1. Now, MTV automatically changes multiple periods in a VM name to a single period, making it compliant with RFC DNS1123. (MTV-2308)

UI displays an incorrect "Invalid VM Name" message for a VM name containing a period

In earlier releases of MTV, the UI displayed an "Invalid VM Name" message for a VM name containing a period, even though MTV supports such names. This issue has been resolved in MTV 2.8.1. (MTV-2309)

MTV does not preserve the gateway IP address of an NIC from a different subnet

In earlier releases of MTV, the gateway IP address of the virtual machine was not copied after migration if the IP address was out of the network interface subnet range. This issue affected migrations even if you enabled the Preserve static IPs setting. This issue has been resolved in MTV 2.8.0. (MTV-2018)

MTV displays an error in the migration plan for VMs without a static IP address

In earlier releases of MTV, for migration plans in which Preserve static IPs is enabled, MTV displayed an error message if you did not configure a static IP address for the guest VM. This issue has been resolved in MTV 2.8.0. (MTV-1458)

Disk counter does not update progress while migrating VMs with multiple disks

In earlier releases of MTV, the Disk Counter did not show real-time progress of disk transfer when migrating a VM with multiple disks. This issue has been resolved in MTV 2.8.0. (MTV-1718)

Incomplete migration plan error for VMs with shared disks before cold migration

In earlier releases of MTV, the migration plan for a VM with shared disks showed an error that did not list all VMs to be powered off before the cold migration. This issue has been resolved in MTV 2.8.0. (MTV-2206)

MTV runs a migration plan after a VMware VM in the plan is canceled

In earlier releases of MTV, during warm migrations of multiple VMware VMs, MTV continued to run the migration plan after you canceled a VM in the plan. The initial plan was run after you successfully migrated the canceled VM through a second migration plan. This issue has been resolved in MTV 2.8.0. (MTV-1796)

Static IP address is not preserved for VMs with manual MAC address configuration

In earlier releases of MTV, the static IP address of a VMware VM was not preserved if you configured a MAC address with uppercase for the virtual network adapter of the VM. This issue affected migrations where the Preserve static IPs setting was enabled and has been resolved in MTV 2.8.0. (MTV-2285)