kumarnirmal
asked on
P2V Conversion using VMware Cold Cloning
I have migrated a Red Hat Enterprise Linux ES release 3 (Taroon) Physical Machine to VMware ESX Server 3.5 using Cold Clone ISO.
The migration to the ESX Host was successful, however powering on the VM lead to Kernel Panic Error (please see attachment)
The physical machine had this configuration with respect to the mount points
fdisk -l
Disk /dev/hda: 40.0 GB, 40016019456 bytes
255 heads, 63 sectors/track, 4865 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 13 104391 83 Linux
/dev/hda2 14 4611 36933435 83 Linux
/dev/hda3 4612 4865 2040255 82 Linux swap
The VM has the following mount points (please see attachment - VM.jpg)
What should be done to bring this Virtual Machine up ?
Kernel-Panic-Error.jpg
VM.jpg
The migration to the ESX Host was successful, however powering on the VM lead to Kernel Panic Error (please see attachment)
The physical machine had this configuration with respect to the mount points
fdisk -l
Disk /dev/hda: 40.0 GB, 40016019456 bytes
255 heads, 63 sectors/track, 4865 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 13 104391 83 Linux
/dev/hda2 14 4611 36933435 83 Linux
/dev/hda3 4612 4865 2040255 82 Linux swap
The VM has the following mount points (please see attachment - VM.jpg)
What should be done to bring this Virtual Machine up ?
Kernel-Panic-Error.jpg
VM.jpg
ASKER
I have already made that change to the config.
The VM had Other Linux (32-Bit) selected by default.
I selected RHEL 3.
Regarding the grub reinitialization, I will try it and update you.
The VM had Other Linux (32-Bit) selected by default.
I selected RHEL 3.
Regarding the grub reinitialization, I will try it and update you.
ASKER
I changed the device map configuration from hd0 - hda to hd0-sda and reinstalled GRUB.
Still I am facing the same Kernel Panic Issue
Still I am facing the same Kernel Panic Issue
From the grub boot prompt, did you use the find command to locate the right location?
Have you tried booting your system by the help of sysresccd?
Lars
Have you tried booting your system by the help of sysresccd?
Lars
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Have you tried reinitializing grub inside the VM?
Also make sure you choose "RedHat Enterprise Linux 3" on the ESX side as target OS and not just a general setting.
Lars