PlateSpin Migrate 9.1.1 Release Notes

April 23, 2012

1.0 About this Release

Version 9.1.1 introduces support for ESXi 5, the hypervisor component of the VMware vSphere 5 platform.


  • This release should not be used for workload migrations to any target other than VMware ESXi 5.0.

  • You should install a separate PlateSpin Migrate server for workload migrations to VMware ESXi 5.0. Do not collocate PlateSpin Migrate 9.1.1 with other versions of the product.

  • Upgrading is supported only from version 9.1.

For documentation that accompanied versions 9.1 and earlier, visit the PlateSpin Migrate 9 Documentation Web Site.

2.0 In Version 9.1.1

  • Support for ESXi 5: This release supports workload migrations to VMware ESXi 5 hosts. Full vSphere 5 vCenter Server support will follow in a subsequent release.

  • Localization: Product and documentation localization is scheduled to accompany a subsequent release of PlateSpin Migrate.

3.0 Bugs Fixed in Version 9.1.1

  • 756351: Wrong network component type in the target VM’s machine property when creating a VMware e1000 adapter.

  • 707490: Failure to create VM replica in the vCenter container if the VM display name had more than 32 characters.

  • 752798: Unable to connect to port 3725 on SUSE Linux Enterprise Server (SLES) 11 with 2 NICs.

  • 721801: SLES 11 SP1 ISO: NIC driver bnx2x.ko could not be loaded because libcrc32c.ko failed to load.

  • 756377: Wrong Intel PRO/1000 gigabit adapter driver included in the driver database.

  • 752800: The OFX controller on a workload did not create the IP list correctly on startup.

4.0 Known Issues in Version 9.1.1

  • 754537: Migrating a SLES 11 SP1 VM from ESX 4.1 to ESXi 5 might get stuck with a recoverable error just after the Release control of target VM step of the conversion job.

    Cause: The source VM on ESX 4.1 has an e1000 network adapter and VMware tools are not installed on the source VM. By default, PlateSpin Migrate creates a VMXNET network adapter for target VMs, for which network drivers are not initialized properly.

    Workaround: 1. Install VMware tools in the target VM by using the VMware vSphere Client, allowing the migration to continue. 2. Detach the VMXNET adapter and attach an a1000 adapter to target VM by using the vSphere Client.