Conversion fails with kernel error.

[dalecexelate]

Hello,

In trying to do a P2V conversion I am getting a very weird kernel error. I am using the 5.1 standalone converter. The error is:

FAILED: An error occurred during the conversion: ' * got kernel major revision as ERROR:
kernel version has to be in format 2.6.*, version 2.6.32-358.6.1.el6.x86_64 is not supported (return code 1)'

I have searched and found no information on this error. I have added a screenshot, any help would be appreciated.

Thanks

[CarelvanHeerden]

I had the exact same problem last night, just on a different kernel version.

From the log file:

2013-05-08T18:34:15.288+02:00 [04496 info 'Default'] [task,379] [task-5] -- ERROR -- Convert: converter.fault.CloneFault

--> (converter.fault.CloneFault) {

-->    dynamicType = <unset>,

-->    faultCause = (vmodl.MethodFault) null,

-->    description = " * got kernel major revision as

--> ERROR: kernel version has to be in format 2.6.*, version 2.6.18-194.8.1.el5 is not supported

-->  (return code 1)",

-->    msg = "",

--> }

Running Vmware VCenter Converter  Standalone 5.1 build 1087880.

Linux Server:

[root@SLAVE1 ~]# uname -a

Linux SLAVE1 2.6.18-308.1.1.el5 #1 SMP Wed Mar 7 04:16:51 EST 2012 x86_64 x86_64 x86_64 GNU/Linux

[root@SLAVE1 ~]# cat /etc/redhat-release

CentOS release 5.8 (Final)

Any ideas?

[dalecexelate]

I downgraded to version 5.0.1 and all is well. Obviously a bug in the latest version of the standalone converter.

Thanks

[scrumi]

I'm having the same issue.  Unfortunately downgrading to 5.0.1 didn't help me that version didn't properly recognize the source partitions.  Not really sure what to do here.  The odd thing is that machine will boot once it fails, but when you try to login it will kick me right back out.

[dalecexelate]

I also had that issue (which is why i upgraded originally). That is fixed by running the following...

yum remove lvm2

yum remove lvm2-libs

Then I grabbed the lvm2 rpms for version 2.02.87

rpm -ivh lvm2-libs-2.02.87-6.el6.x86_64.rpm

rpm -ivh lvm2-2.02.87-6.el6.x86_64.rpm

It works fine after that, and when done just run yum update lvm2 to go back to the latest lvm2. Found this solution after looking all over the web.

[scrumi]

oh so close.  I made it to the last step and this:

rpm -ivh lvm2-2.02.87-6.el6.x86_64.rpm

warning: lvm2-2.02.87-6.el6.x86_64.rpm: Header V4 DSA/SHA1 Signature, key ID 192a7d7d: NOKEY

error: Failed dependencies:

        lvm2 < 2.02.97-2 conflicts with initscripts-9.03.38-1.el6.centos.1.x86_64

[dalecexelate]

I have initscripts-9.03.31-2.el6.centos.1.x86_64. That's probably why I didn't get that error. I will see if I can dig anything up to help.

[scrumi]

Ok I made it past that last error with:

rpm -ivh lvm2-2.02.87-6.el6.x86_64.rpm --nodeps

I'll post what the final result is when I'm done here.

[scrumi]

Well the machine converted just fine, but when I try to boot it then it fails by not being able to mount critical paths.  I've attached an image.  This is a little beyond me, but I'm guessing it has something to do with LVM, and not correctly interpreting the volumes.

[dalecexelate]

Sorry for the late reply. I fixed that by changing the drives from lvm to basic under advanced in the conversion.

Thanks

[kvman]

i downgraded to converter 5.0 and choose virtual machine version 7 and the conversion works fine. but now i'm having trouble when the VM starts got the message "kernel panic"

any ideas

[kvman]

I fixed that by changing the drives from lvm to basic under advanced in the conversion. thanks to dalecexelate

[Federico Valiente]

Hello, y have the same problem with a CentOS and Converter 5.1, error: version 2.6.18-238.12.1.el5 is not supported (return code 1)

So, in resume after all the posts:

Step 1 on the source machine:

yum remove lvm2

yum remove lvm2-libs

Then I grabbed the lvm2 rpms for version 2.02.87

rpm -ivh lvm2-libs-2.02.87-6.el6.x86_64.rpm

rpm -ivh lvm2-2.02.87-6.el6.x86_64.rpm

Step 2: Remove Converter 5.1 and install 5.0.1

Step 3: Convert using virtual machive version 7 and: "changing the drives from lvm to basic under advanced in the conversion",Y can´t find this option (help me), only can change the controller type LSI SAS, etc, etc.

Final:  run yum update lvm2 to go back to the latest lvm2 and install VMware Tools.

Thats is the correct procedure?

Tks all

[Brian_Wing]

Regarding the conversion to "basic" disk.

There's a button at the bottom of the wizard window, on the advanced screen, in the destination layout step.  It's somewhat inconspicuous.

[roccone]

me too can't see anything...

Is it in the Options page? Then I have Advanced options to "Edit" and I can see Post-convertion and similar..

Can you explain me step by step?

Thanks

[roccone]

Ups...sorry.. I found it..
Tomorrow I try.

[Magnus_Quadra]

Friend

I have the same problem, you could solve?

[ARDAvonWOOLF]

If you provide specific details of the problem, perhaps someone can help. There are several solutions in this thread:

1.     Try a different converter version

2.     Advanced options on the disk section to convert it from LVM to basic

3.     Kernel panic (see my post above)

cheers

-AvW

[tommylwlxx]

For your information..

My source is

[root@localhost ~]# uname -a

Linux localhost.localdomain 2.6.32-358.el6.x86_64 #1 SMP Fri Feb 22 00:31:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

[root@localhost ~]# cat /etc/issue

CentOS release 6.4 (Final)

Kernel \r on an \m

by using converter standalone 5.1, it fail with the

FAILED: An error occurred during the conversion: ' * got kernel major revision as ERROR:

kernel version has to be in format 2.6.*, version 2.6.32-358.6.1.el6.x86_64 is not supported (return code 1)'

Then i downgrade the converter to 5.0.1, it success without error.

There is no need to do any rpm remove.

[cjpike]

Has anyone had any luck with getting this to work? I am having the same issues using CentOS 6.4 and have tried both 5.01 and 5.1 with no luck.

[ARDAvonWOOLF]

I've P2V'd several linux's and only once has it worked flawlessly. Usually it is a matter of the build of the init ramdisk.

My most recent (yesterday) issue was this issue:

kernel version has to be in format 2.6.*, version 2.6.18-238.9.1.el5

Which is how I got to this thread. Some recommend going back to converter 5.0.1, which was the version used in the one case the P2V worked perfectly. However, 5.01 complained about a GPT disk and I could not even create the job.

Fortunately, the 5.1 failure did not remove the target VM and gave me something to work on.  Kernel panic. I can't take credit for the resolution, as I follow these two:

VMware KB: Virtual machine does not boot after being converted from a physical Red Hat machine

http://blog.edgoad.com/2010/03/vmware-no-volume-groups-found.html

The issue, I believe, is that the converter relies on command "uname -r" to provide the proper initrd file, but it does not in the cases we're looking at:

* the initrd file is: initrd-2.6.18-238.9.1.el5.img

* uname -r is: 2.6.18-238.el5

You may not even need to edit the modprobe.conf file as explained in the above, just check /etc/grub.conf for the initrd image it is booting to and then build the proper initrd file using mkinitrd

-AvW

"can't take credit"...Message was edited by: ARDAvonWOOLF

[lordengineer]

Step 1: Remove Converter 5.1 and install 5.0.1

Step 2: Convert using virtual machive version 7  on Advance Tab and: "changing the drives from lvm to basic under advanced in the conversion",

Then start the conversion setup. This will solve my problem. Everything is fine works great. If you left your harddrive as "to LVM", then it will hangs on mounting harddrive. Click on "to basic" under advanced in the conversion step.

Answer of this post.

[ajmorton]

The 5.0.1 only works w/ basic disks because it doesn't know how to correctly process the output of the newer 'lvs' command (the regex is too strict about what it looks for and the newer lvm2 adds two char's to one field - this breaks it), but it does know how to handle 'uname', apparently. At this point we're stuck between rescue mode to hand-build initrd's, or dumping LVM just to get the old converter to work? I really hope someone at VMWare is working on this. These are fundamental problems that should have been caught in test.

[roccone]

Hi,

I had the same problem with 5.1 but it seems that the VM works fine. Do you see the same behavior? Can I use it anyway?
After that with fear to find trouble in future I installed Converter 5.0.1 and when the VM boot I have the kernel panic error like someone in this post.

Anyone find some solution?

[patanassov]

That was a bug in Converter 5.1 - it could not recognize unsupported distros (i.e. different from RHEL, SLES, and Ubuntu). It is fixed in 5.5.