Converting Centos 5.7 (Xen) with Converter 5

[timmehb]

Hi Guys,

I am testing out converting some of our Xen linux guests through to VMWare. The process actually worked yesterday multiple times - there is some manual stuff I have to do once it's been converted but the actual conversion works flawlessly.

Now however, whenever I try and convert the machine from Xen to VMWare I am getting a "Unable to create Virtual Machine" error. Logs show:

2012-04-26T14:20:35.288+01:00 [22716 info 'wizardController'] subpages = 1

2012-04-26T14:20:35.288+01:00 [22716 verbose 'wizardController'] Found data connection TaskSummaryDataConnection

2012-04-26T14:20:35.288+01:00 [22716 info 'wizardController'] FillPage()

2012-04-26T14:20:36.532+01:00 [26308 error 'wizardController'] Unable to submit job: converter.fault.VmCreationFault

2012-04-26T14:20:36.760+01:00 [25636 error 'ConversionState'] Submit job failed: Unable to create virtual machine 'Zabbix'.

2012-04-26T14:20:36.762+01:00 [25636 error 'ConverterWizardWindow'] Next/Finish failed: Unable to create virtual machine 'Zabbix'.

I have literally no idea why it is failing when it worked so well a couple of hours ago. Can anyone shed any light on the situation for me?

Many Thanks

Tim

[ivivanov]

You should look at Worker logs. They are on the machine where Converter Server is installed under All Users directory.

[timmehb]

I have exported the logs from the Converter of which I copied and pasted the contents in my original post - I can't see anything else helpful in the logs.

Or are there some other files that I can look into?

[ivivanov]

Yep, the ones you  have looked at are the GUI logs. There should be Worker logs as well. Worker is the component that actually creates the VM on the target and there should be the "root" error message about what has failed. GUI is reporting only an error creating VM.

[timmehb]

Fantastically pointed out! Thanks for that, I'm new to the converter. Here we go, this looks a bit more promising:

2012-04-26T15:54:20.181+01:00 [24224 info 'Default'] Cloning mode volumeBasedCloning

2012-04-26T15:54:20.181+01:00 [24224 warning 'Default'] Disk id fake-disk-from-vg(VolGroup00) does not identify an existing disk

2012-04-26T15:54:20.181+01:00 [24224 info 'Default'] found VolumesToClone list in TargetDiskParams

2012-04-26T15:54:20.182+01:00 [24224 warning 'Default'] Disk id fake-disk-from-vg(VolGroup00) does not identify an existing disk

2012-04-26T15:54:20.182+01:00 [24224 error 'Default'] VmTransformerImpl::SeparateBootDisk: Unable to find VirtualDisk for diskId=fake-disk-from-vg(VolGroup00)

2012-04-26T15:54:20.183+01:00 [24224 error 'Default'] TargetVmManagerImpl::CreateVM: Vm creation failed with error Invalid argument : VmTransformerImpl::SeparateBootDisk: Unable to find VirtualDisk for an active volume

2012-04-26T15:54:20.183+01:00 [24224 info 'Default'] Scheduled timer canceled, StopKeepAlive succeeds

I would think from that it has something to do with the LVM's on my centos box?

[ivivanov]

Yep, looks like. Earlier in the Worker's log there should be a section about vmware-sysinfo, an XML containing description of your source system, in particular the detected disks, volumes and LVM volumes. Can you look at it and see what is detected there?

[timmehb]

-->  <storage>

-->   <volume mountPoint="/" blockSizeInBytes="4096" capacityInBlocks="5316743" blocksFree="2764023" blocksUsed="2552720" devicePath="/dev/VolGroup00/LogVol00" fileSystemType="ext3" isBootVolume="true" label="">

-->    <extfsFeatures dirIndex="true" filetype="true" hasJournal="true" journalDev="false" resizeInode="true" sparseSuper="true"/>

-->   </volume>

-->   <volume mountPoint="" blockSizeInBytes="0" capacityInBlocks="0" blocksFree="0" blocksUsed="0" devicePath="/dev/VolGroup00/LogVol01" fileSystemType="linux-swap" isBootVolume="false" label=""/>

-->   <disk type="msdos" controllerType="scsi" bus="2147483647" deviceId="0" capacityInSectors="52428800">

-->    <device path="/dev/xvda" major="202" minor="0"/>

-->    <hwGeometry cylinders="3263" heads="255" sectors="63"/>

-->    <biosGeometry cylinders="3263" heads="255" sectors="63"/>

-->   </disk>

-->   <volumeGroup version="2" name="VolGroup00" capacityInBytes="26709327872" freeSpaceInBytes="0">

-->    <logicalVolume name="LogVol00" capacityInBytes="22481469440" numberOfStripes="1">

-->     <device path="/dev/VolGroup00/LogVol00" major="253" minor="0"/>

-->    </logicalVolume>

-->    <logicalVolume name="LogVol01" capacityInBytes="4227858432" numberOfStripes="1">

-->     <device path="/dev/VolGroup00/LogVol01" major="253" minor="1"/>

-->    </logicalVolume>

-->   </volumeGroup>

-->  </storage>

Converter works with Volume groups doesn't it? It's funny how it worked earlier today and not now!

[ivivanov]

Looks normal, except that there are no partitions on the disk, only the disk device itself. The other strange thing is that the root filesystem is on a LVM volume and there is no separate /boot volume. It means the boot manager is loading from an LVM volume? What is it, is it GRUB2? This is something Converter wouldn't expect. Can you upload the whole Worker log?

[timmehb]

Uploaded the log file.

Many thanks for another pair of eyes on this. Is there something wrong with my Xen Linux setup?

[root@Zabbix ~]# fdisk -l

Disk /dev/xvdd: 4185 MB, 4185118720 bytes

255 heads, 63 sectors/track, 508 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/xvdd doesn't contain a valid partition table

Disk /dev/xvda: 26.8 GB, 26843545600 bytes

255 heads, 63 sectors/track, 3263 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

    Device Boot      Start         End      Blocks   Id  System

/dev/xvda1   *           1          13      104391   83  Linux

/dev/xvda2              14        3264    26113657+  8e  Linux LVM

[root@Zabbix ~]# more /etc/fstab

/dev/VolGroup00/LogVol00 /                       ext3    defaults        1 1

LABEL=/boot             /boot                   ext3    defaults        1 2

tmpfs                   /dev/shm                tmpfs   defaults        0 0

devpts                  /dev/pts                devpts  gid=5,mode=620  0 0

sysfs                   /sys                    sysfs   defaults        0 0

proc                    /proc                   proc    defaults        0 0

/dev/VolGroup00/LogVol01 swap                    swap    defaults        0 0

[timmehb]

Looks like two disks - xvda1 xvda2

xvda1 is the boot partition

xvda2 is the LVM

[root@Zabbix /]# df

Filesystem           1K-blocks      Used Available Use% Mounted on

/dev/mapper/VolGroup00-LogVol00

                      21266972  10206492   9962752  51% /

/dev/xvda1              101086     28972     66895  31% /boot

tmpfs                  1036380     72088    964292   7% /dev/shm

[root@Zabbix /]# pvdisplay

  --- Physical volume ---

  PV Name               /dev/xvda2

  VG Name               VolGroup00

  PV Size               24.90 GB / not usable 29.62 MB

  Allocatable           yes (but full)

  PE Size (KByte)       32768

  Total PE              796

  Free PE               0

  Allocated PE          796

  PV UUID               JhfOcz-yhPJ-JBd3-iXJt-RLN7-HZbh-hMRteD

[ivivanov]

Yep, however vmware-sysinfo did not recognize this configuration. It only recognizes /dev/xvda disk with no partitions within it. There is an error on the line before the XML:

2012-04-26T16:31:01.867+01:00 [23464 info 'Default'] [Converter Agent SysinfoQuery] successfully exec'ed vmware-sysinfo; result: Error: Can't have a partition outside the disk!

Converter cannot deal with Xen VMs very well. They have some strange storage volumes, but it is looking mostly for attached IDE and SCSI disks. You can try to manually execute vmware-sysinfo on the source. It is a .tar.gz file located in the Program Files directory where Converter is installed, you need to transfer it to the source, extract it in a directory and run the vmware-sysinfo-linXX.sh as root. It should generate a log file describing in more details what disks and partitions are recognized and what has been filtered out.

[timmehb]

It's pretty much given me the same info as the Worker log.

Right - does that mean I'd need to get the /boot partition into the LVM? Linux disks are not my strong point here unfortunately.

[ivivanov]

It's pretty much given me the same info as the Worker log.

For the XML - yes, however there should be a separate log file in the sysinfo directory. It says things like "Skipping device XXXXX"

[timmehb]

Yes it does! :

[2012-04-26 17:14:01,919 INFO storage ]: Skipping unsupported device with path: /dev/md0, type: 0

Didn't think I had software RAID on this box, infact - I don't..

[timmehb]

[2012-04-26 17:25:06,372 INFO storage ]: Parted returned device with path: /dev/md0, type: 0

[2012-04-26 17:25:06,372 INFO storage ]: Skipping unsupported device with path: /dev/md0, type: 0

[2012-04-26 17:25:06,372 INFO storage ]: Parted returned device with path: /dev/xvda, type: 13

[2012-04-26 17:25:06,388 INFO storage ]: Parted successfully probed device with path: /dev/xvda, type: 13, disk type: msdos

[2012-04-26 17:25:06,389 INFO storage.disk ]: Creating fake SCSI disk for controller type 13

[2012-04-26 17:25:06,697 INFO storage ]: Parted returned device with path: /dev/xvdd, type: 13

[2012-04-26 17:25:06,751 ERROR storage ]: Parted failed to probe device with path: /dev/xvdd, type: 13

[2012-04-26 17:25:06,751 INFO storage ]: LVM2 executables found

[2012-04-26 17:25:06,903 INFO storage ]: Got mount table entry: fsname: /dev/mapper/VolGroup00-LogVol00, dir: /, type: ext3

[2012-04-26 17:25:06,903 INFO storage ]: Looking for device with major 253 and minor 0

[2012-04-26 17:25:06,903 INFO storage ]: Found device /dev/VolGroup00/LogVol00

[2012-04-26 17:25:06,903 WARN storage.volume ]: Creating volume with mountPoint: /, device path: /dev/VolGroup00/LogVol00, fsType: ext3, _blockSizeInBytes: 4096, _capacityInBlocks: 5316743, _blocksFree: 2763990

[2012-04-26 17:25:06,903 INFO storage ]: Got mount table entry: fsname: proc, dir: /proc, type: proc

[2012-04-26 17:25:06,903 INFO storage ]: Got mount table entry: fsname: sysfs, dir: /sys, type: sysfs

[2012-04-26 17:25:06,903 INFO storage ]: Got mount table entry: fsname: devpts, dir: /dev/pts, type: devpts

[2012-04-26 17:25:06,903 INFO storage ]: Got mount table entry: fsname: /dev/xvda1, dir: /boot, type: ext3

[2012-04-26 17:25:06,903 INFO storage ]: Looking for device with major 202 and minor 1

[2012-04-26 17:25:06,903 INFO storage ]: Got mount table entry: fsname: tmpfs, dir: /dev/shm, type: tmpfs

[2012-04-26 17:25:06,903 INFO storage ]: Got mount table entry: fsname: none, dir: /proc/sys/fs/binfmt_misc, type: binfmt_misc

[2012-04-26 17:25:06,903 INFO storage ]: Got mount table entry: fsname: sunrpc, dir: /var/lib/nfs/rpc_pipefs, type: rpc_pipefs

[2012-04-26 17:25:06,904 INFO storage ]: Getting stats for swap device /dev/mapper/VolGroup00-LogVol01

[2012-04-26 17:25:06,904 INFO storage ]: Swap device /dev/mapper/VolGroup00-LogVol01 has block device number (major,minor): (253,1)

[2012-04-26 17:25:06,904 WARN storage.volume ]: Cannot use statvfs() for the swap volume with device path: /dev/VolGroup00/LogVol01, so the volume size statistics will not be set.

[2012-04-26 17:25:06,904 WARN storage.volume ]: Creating volume with mountPoint: , device path: /dev/VolGroup00/LogVol01, fsType: linux-swap, _blockSizeInBytes: 0, _capacityInBlocks: 0, _blocksFree: 0

[2012-04-26 17:25:06,904 WARN network ]: Ignoring interface 'lo' because it is not an ethernet interface

[2012-04-26 17:25:06,904 WARN network ]: Ignoring interface 'sit0' because it is not an ethernet interface

[2012-04-26 17:25:06,904 INFO distribution ]: /etc/redhat-release file line: 'CentOS release 5.7 (Final)'

[2012-04-26 17:25:06,916 WARN hardwareInfo ]: No "physical id" lines found in /proc/cpuinfo, defaulting to one socket with one core

[2012-04-26 17:25:06,916 INFO hardwareInfo ]: /proc/sys/kernel/bootloader_type has valie: '0'

[2012-04-26 17:25:06,916 INFO grub ]: Trying to create device map file /tmp/vmware-sysinfo-grub-device.map

[2012-04-26 17:25:06,916 INFO grub ]: Running command: grub --batch --no-floppy --device-map=/tmp/vmware-sysinfo-grub-device.map > /dev/null 2>&1

[ivivanov]

For some reason it does not find any partitions under /dev/xvda and /dev/xvdd. I guess that is why "boot" has been left out. I am not sure what exactly caused the Converter error, but it should be related to the missing info from the sysinfo XML.

Can you try to replace the libparted library in your sysinfo folder with the one that is native to your system (if you have one) and re-run vmware-sysinfo again and see if the output would be different? There is a chance that the version shipped by Converter does not recognize storage properly, but the one on your system is doing better.

[timmehb]

Still no joy, even after transferring the libparted from /usr.

I'm completely stumped...

[M2]

I have a xen vm Cent OS 5.7 that I  converted successfully from Xen 6.0 to VMware Esxi 4.1 using the latest  standalone converter 5.0

But after running the conversion I get the following error?

this was the orginal setup

How do i go about fixing this on the VM?

Thank you for your reply.

[ivivanov]

You may want to take a look at http://communities.vmware.com/message/1816296#1816296.

[rbernard84]

no have access