cloning RedHat 3 VM brings up a kernel panic

[admin]

I am trying to clone my RedHat Enterprise 3 VM 32bit on DL365 to a BL480C server. The clone was successful but I gets a kernel panic when I boot the migrated VM.

"kernel panic fatal exception

in idle task not syncing"

What could be the problem here? Can someone tell me solution to resolve this?

thanx in advance

[Texiwill]

Hello,

A DL365 is a AMD processor and a BL480C is an Intel. Depending on how your VM is configured you may be using the wrong kernel for the new hardware.

Boot the VM using the rescue disk. Use chroot to gain access to the existing install and verify your kernel in /etc/grub.conf. And use 'rpm -q kernel' to determine what is being loaded. You may need to use a different kernel and initrd image.

Booting from the rescue disk is the first step in solving this problem.

Best regards,

Edward

[admin]

Thanx for your reply.. But when I tried cloning my RedHat Enterprise 4, it works perfect without any issues. What makes the difference between RH3 and RH4?

I tried creating the initrd image and still it didnt work. is there any other workaround that you can suggest?

thanx again..

[Texiwill]

Hello,

RHEL3 => 2.4 Kernel

RHEL4 => 2.6 Kernel

They are different beasts and behave differently. With RHEL3 there were a myriad of 'kernel' choices, with AMD being one of them. For RHEL4 there are not so many choices.

You should install the rhel3 i386 kernel or the i686 kernel. Either should work. If you already have the i386 kernel, then boot from it instead of the AMD kernel. If the 'rescue' cdrom worked then the i386 kernel will work.

You will need the appropriate network connection or CD in single user mode to fix this.

Best regards,

Edward