Novell Home

My Favorites

Close

Please to see your favorites.

Target VM does not boot after migration from VMware ESX to Citrix Xen if boot files are located in second disk

This document (7012906) is provided subject to the disclaimer at the end of this document.

Environment

NetIQ PlateSpin Migrate 11
NetIQ PlateSpin Migrate 9.3
Source is a VM hosted on VMware ESX server
Target host is a Citrix Xen server

Situation

Migration of a source VM (hosted on ESX) to a VM on Citrix Xen target host results in non-bootable target VM.
 
Note: As only semi-automated migrations to Citrix Xen are supported, the VM needs to be manually created and registered with Platespin Migrate as fake physical. Here are the steps to follow:
 
1. Boot target VM created manually on Citrix Xen with take control ISO and register it with Migrate server

2. Discover the Source VM hosted on VMware ESX server.

3. Configure the job to migrate source VM to the VM (on Citrix) registered as fake physical.

4. In the job, view the job settings for Hard drives. Note that system volume(s) of source workload are assigned to second disk.
 
5. During the "8.1.1 Configure Operating system" step, the Citrix XEN VM fails to boot and manual intervention is requested.
 
Note: This is due to Citrix Xen VM trying to boot from disk 0 while boot files are allocated on disk 2.

Resolution

To resolve this problem, rearrange the virtual-disk position in XenCenter so that the virtual machine boots from the virtual
disk that contains the operating system. Below are the steps to change the position of the virtual disk:
 
1. In the XenCenter resource pane, select the powered off guest virtual machine.
2. Select the Storage tab. In the Virtual Disks screen, select the virtual disk containing the operating system and click Properties.
4. In the <<operatingsystem>> Properties dialog, select the final tab to display device options.
5. From the Device Position drop-down menu, select 0. Click OK and exit the dialog box.

Cause

If a VMware VM boots from a SCSI disk but also contains one or more IDE hard disks, the VM might not boot when you convert it to XenServer. The reason is that the migration process assigns the IDE hard disks lower device numbers than SCSI disks. However, Citrix Xen VMs boot from the hard disk assigned to device 0.
 
Below is a link to the document from Citrix which discusses this behavior (Page 21).
 

Additional Information

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7012906
  • Creation Date:19-JUL-13
  • Modified Date:10-MAR-14
    • NetIQPlateSpin Migrate

Did this document solve your problem? Provide Feedback