Kernel Failure on Debian 5.0

[Alexandre_27]

Before my doubt I would like to say that Virtualbox is a great software and very useful to me, so thank you guys and keep up with the good work.

My problem is that when i install Debian 5.0 Lenny on virtualbox, everytime i log in it gives a kernel failure and some functionalities just don't seem to work. I'm configuring a server to ldap and i would like to test on virtualbox before starting on the "real server" and i cannot figure out what is causing the kernel failure if it is a problem of the configuration or of it's the way of install.
The virtualbox version is 3.2.0.
Here is the screen of the virtual machine details:

debian.gif (21.65 KiB) Viewed 3640 times

And here's the error:

debian2.gif (23.28 KiB) Viewed 3637 times

Hope that you can help me.

[Perryg]

Please post the guest log (as an attachment)
Also does this prevent the OS from starting, or does it appear and then go ahead and load?

[Alexandre_27]

Please post the guest log (as an attachment)

Where is that file?

Also does this prevent the OS from starting, or does it appear and then go ahead and load?

No, The OS starts but i can't install the guest additions because it "can't read all the content" in the cd and when I'm using the shell even as root it gives many errors in commands.
I have already saw this doubt in some forum but nobody can find a solution.

[Perryg]

Start the VBox main program and click on Machine (at the top left) and then at the bottom show log. Then click save and post (as an attachment).

[Alexandre_27]

Here are the log files:

Debian-2010-05-30-00-08-19.log

(78.96 KiB) Downloaded 212 times

Debian-2010-05-29-20-12-12.log

(71.38 KiB) Downloaded 194 times

[Perryg]

Debian-2010-05-29-20-12-12.log
C:\Users\Alexandre\Desktop\Red Hat Linux.vmdk (This one seems to be an import)

Debian-2010-05-30-00-08-19.log
C:\Users\Alexandre\.VirtualBox\HardDisks\Debian.vdi (This one seems to have too much RAM allocated to it and looks like you are trying to boot it with PXE).
00:00:00.627 Host RAM: 3070MB RAM, available: 1991MB
00:00:00.740 RamSize <integer> = 0x0000000040000000 (1073741824)

So un-confuse me please. I'm guessing the first one (second log file) is not the one that is giving you problems. First thing to try it dropping the RAM to 512 on the Debian lenny one and see what happens. Are you really using PXE or not?

[Alexandre_27]

Debian-2010-05-29-20-12-12.log
C:\Users\Alexandre\Desktop\Red Hat Linux.vmdk (This one seems to be an import)

That is a disk that a friend has and works on vmware but i tried it on virtualbox and it gives the same kernel failure.

So un-confuse me please. I'm guessing the first one (second log file) is not the one that is giving you problems. First thing to try it dropping the RAM to 512 on the Debian lenny one and see what happens. Are you really using PXE or not?

The one that has the Debian.vdi still gives the error even after reducing the RAM and I'm trying to make a boot from the hard drive not from network.
There are differences in the boot and maybe there's the answer.
This is the boot in VMware:

Vmware.gif (11.91 KiB) Viewed 3585 times

This is the boot in Virtualbox:

Virtualbox.gif (10.29 KiB) Viewed 3588 times

And in the rest of the boot i notice that there are some things done on vmware that are not made in Virtualbox. I don't know if it is of the permission on the disk that not allow to write everything that's necessary to not crash.
And i forgot to tell that i created the same virtual machine on virtualbox but in the Linux Caixa Mágica host and it worked but i don't know which version of virtualbox were in use.

[SicoBulo]

Hello! I had that problem with my Debian Guest, the kernel failure manifested when I booted it after a basic installation, plus the installation of the Graphic environment, from the Image of the Disc # 1, So If the failure with your Debian guest happened as you installed it, An upgrade of your guest kernel-image (using the repositories) may solve your problem, it did with mine... Regards.

[Eck]

And an easy way to upgrade that guest kernel is to use backports.org. Check out their website for instructions. Better if you'd like to easily install a debianized kernel upgrade without compiling one yourself. That said, I didn't need a kernel upgrade for my Lenny guests in previous VirtualBox versions to get Debian working but I haven't tried it with the latest versions. I only encountered a time zone glitch after the initial install that fsck fixed (I think due to some UTC/local mismatch).

One advantage of a kernel upgrade will be the use of opengl. The guest additions require 2.6.27 for that and Lenny comes with 2.6.26.