P2V’ing a Suse Linux server
February 6th, 2008
I just P2V’ed a Suse Linux Server with the cold boot iso. When booting I was confronted with a kernel panic. This is caused by the fact that the modules for the LSI Logic or Bus Logic SCSI card aren’t available, which causes the root volume to be unmountable. I tried to boot from the installation CD with the “rescue” option but this did not provide me with a fast solution for the problem. But the following was a quick fix:
- Boot from Suse CD
- Select to setup a new system
- Select to boot from the currently installed OS
- Run Yast and configure the correct SCSI controller
- Remove all the NICS and configure a new NIC
- Install VMware tools
February 6th, 2008 at 14:15
I tired a p2v of a Suse server back in December and could not even get the Cold Clone CD to work. After attempting to use a Ghost image I got the same unmountable partition problem. We found a link from Novell explaining how to use the rescue cd but the process seemed involved and unclear. In my case the p2v was actually out of scope for the project so the customer decided to manually build and migrate a later time.
Booting from the currently installed OS and using Yast seems to be the best option for future p2v migrations. Thanks!
February 6th, 2008 at 18:57
[…] posted a quick article today about successfully p2v-ing a SLES server. (Yes, I know that’s redundant but it just doesn’t sound right saying “p2v a […]
April 6th, 2008 at 03:06
Be sure that you have not installed converter, workstation, server onto the same machine as VirtualCenter. If so, key .dll files get replaced. Not to mention 2 very confused p2v agents.