Kernel module problem?

[twilight7345]

I am trying to virtualize a physical server running Red Hat AS2 to ESXi and every method copying or imaging the data to the virtual server always generates the same error. When I boot up the new virtual machine, the normal grub menu comes up and then the server starts to boot into the kernel. It then crashes with the following output (starting at the first error):

/lib/megaraid2.o init_module:
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
ERROR: /bin/insmod exited abnormally!
loading jbd module
Journalled Block Device driver loaded 
Loading ext3 module
Mounting /proc filesystem
Creating root device
Mounting root filesystem
mount: error 19 mounting ext3
pivotroot: pivot_root(/sysroom,/sysroot/initrd) failed: 2
Freeing unused kernel memory: 244k freed
Kernel panic: No init found. Try passing init= option to kernel.

I am by no means a Linux expert and this problem a little over my head. If it is possible, I would like to be able to fix this problem. Failing that, I would like to find an alternative solution so that I can turn off this physical machine and start using the virtual machine.

[Rubberman]

Since you are moving a physical server to a VM, you need to make sure you configure the VM to emulate the original system exactly (CPU options, etc).

[twilight7345]

Since you are moving a physical server to a VM, you need to make sure you configure the VM to emulate the original system exactly (CPU options, etc).

Yeah, I have the VM settings the same as the original server (processor, memory, OS, etc.). It seems like it is crapping out because it is trying to load the RAID driver module from the old server but I am not really sure.

[Rubberman]

Yeah, I have the VM settings the same as the original server (processor, memory, OS, etc.). It seems like it is crapping out because it is trying to load the RAID driver module from the old server but I am not really sure.

That is a good possibility. You might want to remove the RAID driver module load from the source OS, or open the VM drive image and remove it from the system initialization scripts. Then try to reboot.

[twilight7345]

That is a good possibility. You might want to remove the RAID driver module load from the source OS, or open the VM drive image and remove it from the system initialization scripts. Then try to reboot.

Sorry, how do I remove a module from the initialization scripts? I don't really have much experience with Linux kernel stuff.

[Rubberman]

Sorry, but I'm also just getting up to speed on kernel details. I know enough to be dangerous and debug common problems, but I don't know all the details of what you would need to do to resolve this issue. As you surmise, your problem is likely related to the loading and initialization of the RAID device on the original system, but that doesn't exist in your VM. There may be other issues as well. You might want to contact VMware or post a query on their user forums to see what you should do.

[twilight7345]

Sorry, but I'm also just getting up to speed on kernel details. I know enough to be dangerous and debug common problems, but I don't know all the details of what you would need to do to resolve this issue. As you surmise, your problem is likely related to the loading and initialization of the RAID device on the original system, but that doesn't exist in your VM. There may be other issues as well. You might want to contact VMware or post a query on their user forums to see what you should do.

LOL I think we are in the same boat. I just found out that the new VMware converter supports Linux, so I think I will give that a shot.

[twilight7345]

vConverter 4 was able to convert the server to an ESXi image while the server was running. It actually worked great; it processed quickly, cleaned up all of the disused kernel entries and fixed (I am assuming) the module problem.l