PlateSpin Migrate 12.0 Release Notes

932115: CLI specified virtual network is used during conversion and server sync instead of the default.

926863: Unable to load DLL 'ZLibWrapper' during workload conversion with compression enabled.

912802: Target VM does not boot "Volume with serial number 00000000".

892472: When source workload has multipath enabled, the boot device /dev/mapper/mp_root-part1 does not get replaced by /dev/sda1/ in /etc/fstab on the target.

907078: Windows workload remote registry discovery using named pipes crashing.

927976: Windows file server disk quota settings and templates are not set on target post migration.

925595: Error when sending files: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.

930166: CPUID SDK library update to prevent crash on Korean Windows 2012 workload.

930486: Creating 4.9 TB volume partition fails.

933726: Windows Source OFX connection not established post upgrade.

933162: CLI handling network name case insensitive or extra space in it.

930355 - Mapping volumes not supported when migrating Linux workloads: When you use the PlateSpin Migrate Client to migrate Linux workloads, the following are not supported:

937071 - Unable to migrate Linux workloads that have volumes created on raw disks without partitions: PlateSpin Migrate does not support migrating Linux workloads that have volumes created on raw disks without partitions.

902489 - Unable to migrate a workload to Hitachi LPAR that has an operating system running on it: When you migrate a workload to Hitachi LPAR that has an operating system running on it, the migration might not complete. This is because the migration job waits for user intervention during the Configure Target Machine step of migration.

917209 - Warning message displayed when you migrate a workload to Hitachi LPAR: When you migrate a workload to Hitachi LPAR, a warning message similar to the following might get displayed:

929511 - Unable to install PlateSpin Migrate on Windows Server 2012 and Windows Server 2012 R2 computer: On a Windows Server 2012 or Windows Server 2012 R2 computer, if you disable UAC through the Control Panel and then install PlateSpin Migrate on the computer, the prerequisites check utility displays an error that the UAC is still enabled. This is because when we disable UAC from the Control Panel, the change is not reflected in the corresponding registry key.

929978 - Discovered Hyper-V container displays as a workload in the PlateSpin Migrate Web Interface: If you use the PlateSpin Migrate Web Interface to discover a Hyper-V container, the Hyper-V container is listed as a workload in the interface. You must not migrate this Hyper-V container.

937070 - Unable to migrate a Linux workload to a container that does not support the source workload firmware: The migration of a Linux workload fails in the following scenarios because UEFI to BIOS conversion and vice versa is not supported:

895957- Unable to execute post-migration scripts on a Linux workload: Post-migration scripts fail to execute on a Linux workload.

Requirements for VMware DRS Cluster support: PlateSpin Migrate supports VMware Clusters with and without DRS enabled, and with any level of DRS (Manual, Partially Automated, or Fully Automated). However, to be a valid migration target, your VMware Cluster must be discovered via vCenter and not by directly inventorying individual ESX servers.

493589 - (Windows sources) Non-default per-volume VSS settings are not preserved after migration: This issue is under consideration for an upcoming fix.

505426 - (ESX4) No warning or error on wrong vCPU selection: If the number of the requested vCPUs exceeds the number of physical CPUs on the ESX 4 host, the requested number is ignored and the target VM is created with a single vCPU without a warning. This issue is under consideration for an upcoming fix.

506154 - Special character in datastore name causing migration problems: Migration operations might fail when they are attempted on ESX datastores that have the “+” or other special characters in the datastore name.

595490 - Preserving boot partition causes migration problems: In some migration scenarios, the system improperly allows you to preserve your boot partition on the target, preventing the proper workload from booting. This issue is under investigation.

604320 - (Linux to ESX 4) Problem completing migration if the source OS has autologin or CD automount features enabled: The migration is also affected if you log in to the target during the job’s Configuration step.

619942 - Failure to execute a post-migration script with Unicode characters in the filename: If you use Unicode characters in the filename of your post-migration script, the script fails to execute.

655828 - Failure to mount NSS volumes: After a migration is completed, NSS volumes with snapshots enabled are not automatically mounted as expected.

680259 - (VMware 4.1) Poor networking performance by traffic-forwarding VMs: In some scenarios, the replica of a workload that is forwarding network traffic (for example, if the workload’s purpose is to serve as a network bridge for NAT, VPN, or a firewall) might show significant network performance degradation. This is related to a problem with VMXNET 2 and VMXNET 3 adapters that have LRO (large receive offload) enabled.

685509 - Failure with Access Denied error during replication to an image stored on a network share: The Controller service on Image servers that use network shares for storage does not preserve the service Log On As credentials after an upgrade. Image operations fail with an Access Denied message until the controller service is updated with the correct Log On As credentials.

692680 - VSS snapshots are not preserved: VSS snapshots taken by third-party applications on the source workload are not replicated to the target upon migration.

702152 - Migration over WAN taking a long time if target VM host has a high number of datastores: Under some circumstances, when your Migrate server is connected to the VM host over WAN, and if your VM host has a high number of datastores, the process of locating the appropriate ISO image required for booting the target might take longer than expected. This issue is under investigation.

779194 - Unmapped /home directory is disabled and unmounted after one time server sync: If you perform a server sync and then unman the /home partition to none, the partition /home directory should be mounted and enabled on the target server, instead it is disabled and unmounted.

810460 - VMware tools are not installed during a conversion of a Windows 20212 server core: VMware tools are not installed during a conversion of a Windows 2012 server core.

822601 - Network card is not initialized on SLES 11 target VM hosted on Windows 2008 Hyper-V host: If you perform a SLES 11 workload (cloned VM) migration using the semi-automated method to a target VM (faked physical) on a Windows 2008 Hyper-V host, the process freezes at the "Configuring OS" step.

824724 - Target VM does not boot after migration from VMware ESX to Citrix Xen if boot files are located in second disk: When a VM is converted from VMware ESX to Citrix Xen and its boot files are allocated in second disk, the VM does not boot and manual intervention is requested. This is because Citrix XEN VM tries to boot with disk 0 rather than with the bootfiles allocated to disk 2.

825016 - XenServer tools are not being removed after conversion: XenServer tools on a Windows VM in a Citrix XenServer hypervisor environment are not removed when the VM is converted to a VMware container or a physical container.

825434 - After migration, the primary partition (C:\) is converted to a logical partition on the target: Scenario: Moving or copying a Windows OS machine with more than three primary partitions to a physical machine where a Windows OS has been installed with minimum 3 primary partitions. At least one primary partition is preserved in the target machine.

826545 - When Migrate undiscovers a machine, the machine node shown on the ESX host is not undiscovered: When you undiscover a workload, it displays as such in the Migrate client, but the ESX host shows that the node is not undiscovered.

839329 - Attempt to retrieve data from VMware vCenter Server failed with the following exception: Permission to perform this operation was denied. This problem can be corrected by following the procedures to define VMware Roles with tools as described in Using Tools to Define VMware Roles in the PlateSpin Migrate 12.0 User Guide.

843431 - Attempting to boot from Hard Drive (C:) - Error loading operating System. MBR is corrupted. This problem can be corrected by running the ./BcdEditor /fixboot command in the LRD.

859440 - V2P conversion hangs at the configuringoperating system step. When there are multiple boot options in the firmware and the hard disk is not the first boot device in the boot options list, the target machine does not boot from hard disk and conversion hangs.

864325 - Windows 8.1 workloads converting UEFI to BIOS fail to convert at the “sending files” step. The default OEM installation of Windows 8.1 (UEFI) creates a recovery partition with insufficient free space, making it impossible to create a Volume Shadow Copy (VSS) for the partition.

864326 - Conversion fails while downgrading from UEFI to BIOS firmware: The conversion of a UEFI workload (Windows 6.2 and above kernel versions) to BIOS-based machine fails at the Preparing OS step because the active partition cannot be found to update boot parameters.

865570 - File-based transfer breaks for Windows 2012 R2 UEFI workload: X2P File-based transfer of Windows 6.2 and above kernel versions fails during the sending and receiving files stage.

866467 - Image capture of a Windows 32-bit OS fails: Migrate expects a folder named C:\Windows\Boot\EFI to be present in the source server for exporting content for future use. The folder is not present in Windows 32-bit operating systems earlier than Windows 2008/Vista, so when Migrate exports BCD information to the folder, the operation fails with the error:

875562 - Source machine stays in an “under control” state after offline conversion,: If you configure the End State setting of an offline conversion job as Restart, the source machine remains in an “under control” state after the job completes successfully.

878043 - Source machine boot configuration is not restored after offline conversion: The boot menu of windows source machine is not restored after offline conversion.

891690 - Creating and moving a VM under resource pool as a setting is not supported in the CLI tool: The command line interface (CLI) tool added as a new feature in this release does not currently support moving or creating a VM under resource pool as a setting in the conversion.ini file.

894623 - Partitions are not mounted to drive letters after conversion: Following a conversion to Hyper-V 2012 R2, only the "C" drive is visible. Other partitions are not mounted to drive letters.

896584 - Adding disk and volume mapping does not work properly for a conversion of a workload to Hyper-V2012 R2: Booting the Hyper-V VM with LRD returns randomly listed devices in Hard Disk Devices List, whether IDEs, SCSIs, or a mix of both.

Scenario 1-- IDE to SCSI Behavior

Scenario 2-- SCSI to IDE Behavior

896598 -Redundant disks present after a RHEL 6.2 x64 block migration to Hyper-V 2012 R2: After performing a successful RHEL 6.2 x64 block-based migration with the Install Integration Services option selected, running the fdisk -l command shows redundant disks. That is, a single disk is displayed twice as sda and sdb.