Page 1 of 1

[Debian squeeze]guest OS won't boot

Posted: 1. May 2010, 23:54
by Lupuss
Hello

I currently have two PCs with virtualbox 3.1.6, one has a P8400 cpu (mobile version of the Core 2 Duo series I think), the other one an Athlon X2 4200+ (socket 939).

The first one can boot a squeeze guest OS without troubles (with the current kernel). With the other one I always get a "soft lockup, cpu stuck..." error message. It's been that way since the "trunk" kernels.
I've tried fresh installs (cd install and net install), I've tried to export the working VM from the first PC to the second, ... I always get the bug. I should also mention I can create 64 bits or 32 bits VMs on the first PC but only 32 bits VMs on the second, it could be the 4200+ cpu hasn't got any kind of virtualization technology (both PCs are running a 64 bits host OS).

It's already been reported I think, I wanted to know if anyone has found a workaround?!

Re: [Debian squeeze]guest OS won't boot

Posted: 5. May 2010, 22:04
by AndreFelipeMachado
There is, at the moment, an unelegant workaround :oops: for booting Debian Squeeze kernel as a guest OS.

Configure your VM memory for maximum 640 MB ram (or even less). :cry:

I hope a virtualbox patch could be developed soon.
Regards.
Andre Felipe Machado
http://www.techforce.com.br

Re: [Debian squeeze]guest OS won't boot

Posted: 5. May 2010, 22:15
by fixedwheel
this is an AMD-CPU issue?
my Squeeze guest is happily running with 3GB and more on intel (Debian Lenny 64bit host)

Re: [Debian squeeze]guest OS won't boot

Posted: 5. May 2010, 22:39
by AndreFelipeMachado
Hello,
This not seems an AMD cpu issue. But the machine i am trying now is an Intel quad core one running 32 bit big mem kernel.
It "seems" a Debian SQUEEZE 2.6.32 kernel related issue. :(
I also run Debian LENNY 2.6.26 kernel guests without problems. 8)
Regards.
Andre Felipe Machado
http://www.techforce.com.br

Re: [Debian squeeze]guest OS won't boot

Posted: 14. May 2010, 17:08
by Lupuss
Curious... I just did a fresh netinstall on the desktop and now it works even with 1 GB of RAM allocated to the VM. My best guess is the problem has been solved in the new 3.1.8 version, but the changelog doesn't mention a fix.