virtualbox kernel panic

[mimosa]

On the install disk boot screen the example says noacpi. I thought it was my glasses but apparently not!

[djemos]

I have a 64bit salix-13.37-kde system. I had installed the 64 bit version of virtual-box.
I boot the salix-kde-13.37.iso, 32bit edition, to install it in virtual-box, to be able to compile the 32bit packages versions of my slkbuilds.

And i got a kernel-panic.

I tried again but this time i typed

Code: Select all

hugesmp.s acpi=off 

to the prompt and salix-kde iso booted and i made the installation.

All versions of salix-13.37 need the parameter acpi=off to pass to the kernel to boot in virtual-box.

After installation same thing happened again, kernel panic.

So hit TAB and write

Code: Select all

Linux acpi=off

and when system boots edit /etc/lilo.conf as root and put this line before read-only

Code: Select all

append = "acpi=off"

save changes and run

Code: Select all

 lilo -v

reboot to check that system boots without kernel panic.

I use the latest virtual-box version 4.1.6

[gapan]

On the install disk boot screen the example says noacpi. I thought it was my glasses but apparently not!

Oops!

Anyway, this must be a regression with the latest versions of VirtualBox. I'm still using 4.0.10 and there are no such problems. That's also why you remember it working properly.

[mimosa]

Right and I found I do need it - I must have typed the parameter once for fun, and there was my trial-and-error scientific method out the window; because I was trying to choose between the hypotheses of hardware or user error, I didn't care about acpi, whatever it is.

VirtualBox provide downloads for earlier versions, and at some stage you do get to choose whether you want automatic updates. So it would be possible to downgrade.

Although the documentation looks thorough at first glance, I actually still found it hard to set everything up; and you really do need the "Additions" to make it usable for more than playing with. You now need the kernel source installed inside the guest to add the additions. Don't know if they are also still needed in the host. Anyway, I found the package somewhere in /var by doing

Code: Select all

find / -name kernel-source*txz

and even though the shared folder feature doesn't work yet without the Additions, you can get the guest to look at a usb stick (though I don't think it can be mounted by host and guest at the same time).

I am writing from a Ratpoison guest inside a Ratpoison host, and having different escape keys seems like a good idea. Well, for the moment the guest is still C-t, and the host's Menu escape key works wherever the cursor is. I don't know what would happen if host and guest used the same escape key. Menu is a good one, because pressing it twice gets you back where you were, and that didn't work for me with Super-L or -R.

But then, why would anyone want an identical guest and host?

[thenktor]

Anyway, this must be a regression with the latest versions of VirtualBox. I'm still using 4.0.10 and there are no such problems. That's also why you remember it working properly.

I can say:
Host Salix 13.37 (kernel 2.6.37.6), VirtalBox 4.0.x, Guest Salix 13.37: works fine
Host OpenSuse 11.3 (kernel 2.6.34.10), VirtalBox 4.1.4, Guest Salix 13.37: works fine