Thursday, October 4, 2012

OVM 3.0 to vSphere 5 migration

I just came back from a successful migration of Windows guests to vSphere 5.

Windows migration was a no brainer to migrate. Following were the steps followed.


  • Perform a Windows Server backup with the system state.
  • Created a virtual machine with more disk space than configured.
  • Created an additional hard disk to store the backup taken.
  • And did a system restore with the backup.
  • Voila! the machine is created. Only the IP settings was not propogated.
There were some linux guests running on the OVM platform that has to be migrated. There are some concerns on relying on the converter to do this migration.

  • When converting a Linux operating system, vCenter Converter does not maintain Logical Volumes (LVMs) on the resulting virtual machine.

  • When using vCenter Converter Standalone 4.x to convert a supported Linux guest operating system that has LVMs, the resulting virtual machine does not contain the LVM setup.

  • During conversion of powered-on Linux machines, Converter Standalone does not recognize Linux source volumes if they are mapped directly on a hard disk 
  • Workaround: Linux source volumes that are not managed by LVM must be located in a partition so that Converter Standalone can recognize them during cloning of powered-on Linux sources.

No comments:

Post a Comment