• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2031
  • Last Modified:

Converting VMware ESXi Guest To XenServer

I'm having issues converting VMware ESXi guests over to XenServer.

The guest(s) that I'm trying to convert are CentOs boxes with up to date Kernels. I've removed VMware tools from the host that I'm trying to convert.

I've powered down the host inside ESXi and exported the box to an .OVF file from there I've tried to use XenConverter to convert and migrate the box to my new XenCenter. From XenConverter, it behaves as though as it's going to complete succesfully and then fails at the end.

I'm currently working against the clock since I only have a few days left on my ESXi host that I'm trying to migrate off of.

Any help on this timely matter is MUCH appreciated.

Thanks ahead of time!
0
mawk
Asked:
mawk
  • 3
  • 2
1 Solution
 
SysExpertCommented:
Are there any other formats that XenCOnverter has in common with Vconverter standalone ?

I hope this helps !
0
 
mawkAuthor Commented:
In my minds eye there are two trains of thought for Xen Converter. One to export an OVF file for conversion/migration and two, converting from a VMDK file.
0
 
mawkAuthor Commented:
The conversion from XenConverter completed succesfully with warnings. This is the log file:

Also, I tried to start the migrated VM in XenServer and it failed at boot (See Attached Pic)



Sunday, September 05, 2010 6:33:23 PM
XenConvert 2.2.1.2392 Copyright (c) 2001-2009 Citrix Systems, Inc.
Microsoft Windows XP  SP 3
Processor Architecture: x86
Number of processors: 2
OVF to XenServer started at Sunday, September 05, 2010 6:33:23 PM
Validating OVF Package...
FWD: Warning:2010.9.5.18.33.23,711: Version not set, applying 1.0.0
OVF Package is valid.
Source is C:\Documents and Settings\mark.green\Desktop\afweb20_OVF\afweb20\afweb20-disk1.vmdk.
Destination is C:\Documents and Settings\mark.green\Desktop\afweb20_OVF\afweb20.
VMDK to VHD started at Sunday, September 05, 2010 6:33:24 PM
Converting VMDK to VHD...
Dismounting VHD...
Failed to find device for VHD with Id 7639 Element not found. (0x00000490)
Failed to get the system directory.
Windows directory is WINDOWS
Scanning for BOOT volume...
*** Warning! ***
Failed to find the Windows Boot Volume.
VHD C:\Documents and Settings\mark.green\Desktop\afweb20_OVF\afweb20\afweb20-disk1.vhd was not configured for XenServer.
VM may not boot in XenServer.
Dismounting VHD...
VMDK to VHD stopped at Sunday, September 05, 2010 6:33:50 PM
Source is C:\Documents and Settings\mark.green\Desktop\afweb20_OVF\afweb20\afweb20-disk2.vmdk.
Destination is C:\Documents and Settings\mark.green\Desktop\afweb20_OVF\afweb20.
VMDK to VHD started at Sunday, September 05, 2010 6:33:50 PM
Converting VMDK to VHD...
Dismounting VHD...
Failed to find device for VHD with Id 7640 Element not found. (0x00000490)
Failed to get the system directory.
Windows directory is WINDOWS
Scanning for BOOT volume...
*** Warning! ***
Failed to find the Windows Boot Volume.
VHD C:\Documents and Settings\mark.green\Desktop\afweb20_OVF\afweb20\afweb20-disk2.vhd was not configured for XenServer.
VM may not boot in XenServer.
Dismounting VHD...
VMDK to VHD stopped at Sunday, September 05, 2010 7:07:20 PM
Importing OVF Package...
FWD: Debug:2010.9.5.19.7.21,333: OVF.FindSystemIds completed, 1 found
FWD: Debug:2010.9.5.19.7.21,880: OVF.FindRasdByType completed, 1 found
FWD: Debug:2010.9.5.19.7.21,927: OVF.FindRasdByType completed, 1 found
FWD: Debug:2010.9.5.19.7.22,927: Import.Process: DefineSystem completed (afweb20)
FWD: Debug:2010.9.5.19.7.23,598: Import.AddResourceSettingData: CD/DVD ROM Added
FWD: Debug:2010.9.5.19.7.23,692: Import.AddResourceSettingData: Network Added
FWD: Debug:2010.9.5.19.7.23,692: Import.SetIfDeviceIsBootable: Using HostResource to find Disk
FWD: Warning:2010.9.5.19.7.23,708: Import.FindRasdleName: VHD file exists, replacing VMDK with VHD: afweb20-disk1.vhd
FWD: Debug:2010.9.5.19.7.24,364: Found file afweb20-disk1.vhd using VhdStream
FWD: Debug:2010.9.5.19.7.24,630: Import.UploadRawVDI Enter
FWD: Debug:2010.9.5.19.7.24,661: Import.UpdoadRadVDI SRUUID: 10c3778d-0f4f-8816-8c23-f4880c4b30e1
FWD: Debug:2010.9.5.19.7.24,661: Import.UpdoadRadVDI Label: afweb20
FWD: Debug:2010.9.5.19.7.24,661: Import.UpdoadRadVDI Capacity: 132120576
FWD: Debug:2010.9.5.19.7.25,83: Import.UploadRawVDI::VDI Created
FWD: Debug:2010.9.5.19.7.25,98: Connect To: 10.1.50.77:80
FWD: Debug:2010.9.5.19.7.25,770: Request: PUT /import_raw_vdi?session_id=OpaqueRef:0a1fa37e-90ca-1729-1350-271200504f5f&task_id=OpaqueRef:8ee139d2-1c4f-fb48-aee7-f4451b8c09c3&vdi=OpaqueRef:6449c2da-f74b-47e8-5317-d569536826a6 http:/1.0

FWD: Debug:2010.9.5.19.7.25,942: 200 OK
FWD: Debug:2010.9.5.19.8.4,19: Import.UploadRawVDI::http.put complete
FWD: Debug:2010.9.5.19.8.9,50: Import.UploadRawVDI Leave
FWD: Debug:2010.9.5.19.8.9,50: OVF.Import.ImportFile leave
FWD: Debug:2010.9.5.19.8.9,50: Import.AddResourceSettingData, recevied autoevent, continuing
FWD: Debug:2010.9.5.19.8.9,50: Import.ImportFileProc (worker thread) completed
FWD: Debug:2010.9.5.19.8.9,50: Import.AddResourceSettingData VDI= OpaqueRef:6449c2da-f74b-47e8-5317-d569536826a6
FWD: Debug:2010.9.5.19.8.9,50: Import.VerifyUserDevice, checking device: 99
FWD: Debug:2010.9.5.19.8.9,128: Import.VerifyUserDevice, device [99] is not available, setting to: [0]
FWD: Debug:2010.9.5.19.8.9,128: Import.VerifyUserDevice, checking device: 0
FWD: Debug:2010.9.5.19.8.9,222: Import.VerifyUserDevice, device: 0 will be used.
FWD: Debug:2010.9.5.19.8.9,238: Import.AddResourceSettingData: Hard Disk Image Added
FWD: Debug:2010.9.5.19.8.9,238: Import.SetIfDeviceIsBootable: Using HostResource to find Disk
FWD: Warning:2010.9.5.19.8.9,238: Import.FindRasdleName: VHD file exists, replacing VMDK with VHD: afweb20-disk2.vhd
FWD: Debug:2010.9.5.19.8.9,316: Found file afweb20-disk2.vhd using VhdStream
FWD: Debug:2010.9.5.19.8.9,456: Import.UploadRawVDI Enter
FWD: Debug:2010.9.5.19.8.9,456: Import.UpdoadRadVDI SRUUID: 10c3778d-0f4f-8816-8c23-f4880c4b30e1
FWD: Debug:2010.9.5.19.8.9,456: Import.UpdoadRadVDI Label: afweb20
FWD: Debug:2010.9.5.19.8.9,456: Import.UpdoadRadVDI Capacity: 21369978880
FWD: Debug:2010.9.5.19.8.9,894: Import.UploadRawVDI::VDI Created
FWD: Debug:2010.9.5.19.8.9,894: Connect To: 10.1.50.77:80
FWD: Debug:2010.9.5.19.8.9,909: Request: PUT /import_raw_vdi?session_id=OpaqueRef:0a1fa37e-90ca-1729-1350-271200504f5f&task_id=OpaqueRef:f9db9479-c96e-d37a-2ef5-7e7d7050698e&vdi=OpaqueRef:41530983-dc86-8064-eed1-f07db0527b33 http:/1.0

FWD: Debug:2010.9.5.19.8.9,909: 200 OK
FWD: Debug:2010.9.5.19.40.22,160: Import.UploadRawVDI::http.put complete
FWD: Debug:2010.9.5.19.40.27,176: Import.UploadRawVDI Leave
FWD: Debug:2010.9.5.19.40.27,176: OVF.Import.ImportFile leave
FWD: Debug:2010.9.5.19.40.27,176: Import.ImportFileProc (worker thread) completed
FWD: Debug:2010.9.5.19.40.27,191: Import.AddResourceSettingData, recevied autoevent, continuing
FWD: Debug:2010.9.5.19.40.27,191: Import.AddResourceSettingData VDI= OpaqueRef:41530983-dc86-8064-eed1-f07db0527b33
FWD: Debug:2010.9.5.19.40.27,191: Import.VerifyUserDevice, checking device: 99
FWD: Debug:2010.9.5.19.40.27,238: Import.VerifyUserDevice, device [99] is not available, setting to: [1]
FWD: Debug:2010.9.5.19.40.27,238: Import.VerifyUserDevice, checking device: 1
FWD: Debug:2010.9.5.19.40.27,316: Import.VerifyUserDevice, device: 1 will be used.
FWD: Debug:2010.9.5.19.40.27,332: Import.AddResourceSettingData: Hard Disk Image Added
Conversion was successful!
OVF to XenServer stopped at Sunday, September 05, 2010 7:40:27 PM

VMboot.bmp
0
 
SysExpertCommented:
SOunds like the HD controller is not compatible.
What is the standard for your XP VM, and what does XEN use.

You may have to find a common controller and use that since you need to be able to read the virtual drive somehow.

IDE may be OK, but SCSI LSI may be much more compatible.

I hope this helps !
0
 
mawkAuthor Commented:
This VM is not any variation of Windows. The log show's Windows because the migration/conversion was made from a Windows box.

It had nothing to do with the controller. Did you even look at my screenshot or logfile? lol

I solved this issue by upgrading the kernel on the CentOS VM before migrating it over to Xen. Upgrading to 2.6.35 (latest stable) resolved the issue. VM is migrated and running on new XenServer.

Issue fixed.

0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now