asked on

P2V for CentOS 4.7

I am trying to virtualize my CentOS 4.7 server into VMware. I am using an acronis linux boot disk to make a backup and then restore to a VM. When I boot the VM I get a kernel panic.

I am pretty sure that the problem is that CentOS 4.7 is not configured to use the correct SCSI driver which prevents it from finding the root drive which causes the kernel panic. I think I just need to use mkinitrd to compile a new kernel boot image with the VMware LSI SCSI driver.

The problem is that I am a linux novice and I need idiot proof instructions on how to do this. I was able to get the VM to boot if I put in a CentOS 5.2 install disc and upgrade, but then all my applications do not work, because they were compiled for CentOS 4.7. I also tried using a CentOs 4.8 install disc to do an upgrade, but it doesn't redetect my SCSI like the 5.2 install disc did.

Any help would be great.

ASKER CERTIFIED SOLUTION

Matt V

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Paul S

ASKER

Is that free? Can you provide a link?

Paul S

ASKER

I think I found it. Any articles that have VMware converter on Linux for Dummies ?

Matt V

http://www.vmware.com/products/converter/

Check out the FAQ, you can also convert Acronis images.

Matt V

The app is very easy to use, you pick the source machine or image and then pick the destination (ESX/ESXi host, VMware Workstation etc)

Paul S

ASKER

Do I install the client or server when asked?

Matt V

I forget which allows you to do remote machines, but it will tell you when you install it if you need server, there is a little info window that pops up.

Paul S

ASKER

So I should just start the install on my production CentOS box and see what happens?

Matt V

Unless you want to test it on a quick VM first.

Paul S

ASKER

This is the error I am getting:

tar -xvf VMware-converter-4.0.1-161434.tar.gz
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Archive contains obsolescent base-64 headers
tar: Error exit delayed from previous errors

Matt V

tar xzvf VMware-converter-xxxxxxx

xzvf to unzip and untar.

Paul S

ASKER

thanks, i just found that after a google search.

Paul S

ASKER

It is asking if I want to install client and/or server. The default is yes to both. use defaults?

Paul S

ASKER

It is installing now. I accepted all defaults accept for tcp port numbers which would conflict with the web app on the server.

Matt V

To convert the local machine I think you only need the client.

Paul S

ASKER

install done.

now I get this when I run it.

/usr/bin/vmware-converter-client now
/usr/lib/vmware-vcenter-converter-standalone/converter-gui: /usr/lib/libpng12.so.0: no version information available (required by /usr/lib/vmware-vcenter-converter-standalone/lib-client/libQtGui.so.4)
converter-gui: cannot connect to X server

Matt V

Are you running it from X Windows or a command line only boot?

Paul S

ASKER

putty ssh session.

Anyways, i skipped that and ran the converter on my windows pc and started the P2v task to one of our ESX boxes. so far so good.

I am hoping to copy the vmdk file from this new VM to use with VMware server 2.x. That should work right?

Matt V

Yes, it will work with all the current versions of VMware and quite a few older ones.

Paul S

ASKER

14 % done now. You may not here fro me until tomorrow. I will let you know how it goes. I assume the Converter will install all the needed SCSI drivers for me.

Matt V

It will make the machine bootable then you will want to install the vmware tools

Paul S

ASKER

I used vmware converter on my windows pc to connect to the vmware converter client on my linux box, then transfered to my ESX host, installed vmware tools, them shutdown VM and moved the vmdk file to my other server running VMware server 2.x and swapped in the new vmdk file. Worked like a charm.