Opened 14 years ago
Closed 14 years ago
#7685 closed defect (invalid)
RedHat 5.5 Raises Kernel Panic after installing Virtual Box Guest Additions
Reported by: | Craig Coleman | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 3.2.10 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | Windows |
Description
Hi,
I've installed RedHat Enterprise Linux 5.5 into a new virtual machine using rhel-server-5.5-i386-dvd.iso from RedHat.
The vm is given 1GB RAM, 1CPU and 20GB storage. My host is a Dell M4300
RedHat installs fine with no errors and runs fine , however after install guest additions, the boot sequence raises a Kernel Panic. The VM restarts but then raises the same error thereby entering an infinite loop.
Attachments (3)
Change History (9)
by , 14 years ago
Attachment: | RedHat-KernelPanic-VBox_3_2_10.jpg added |
---|
comment:1 by , 14 years ago
My host is a Del M4300 with 4GB RAM, Windows 7-32bit, Dual-Core Centrino 2.6GHz with 100+GB freespace.
I have uploaded a screenshot plus a copy of the VM definition file.
comment:3 by , 14 years ago
Oh, and the module vboxguest.ko from the guest (must be located somewhere below /lib/modules/) as well please.
comment:4 by , 14 years ago
I cannot attach vboxguest.ko because I can't boot the virtual machine to get to /lib/modules.
Sorry.
comment:5 by , 14 years ago
Thanks for the log. As of booting that VM:
- Make sure to break into the grub menu during boot. Edit the command line with 'e' and remove the word quiet and append (to the end!) the words init=/bin/bash. Then press enter and boot with 'b'.
- The VM should now boot and you are at a bash prompt. Do
mount -o remount -w /
to mount the root file system writable. - Go to /lib/modules/ and into the directory of the currently running kernel. Move the vboxguest.ko module out there to another place (e.g. to /root). Then do
sync reboot
- This will reboot your guest and it should now boot without the additions active. Please attach the vboxguest.ko module to this ticket.
comment:6 by , 14 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Thanks for the module. Actually the problem seems to be that you are trying to execute a Xen kernel which is not possible with VBox. Just execute the standard kernel.
Screenshot