LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (http://www.linuxquestions.org/questions/linux-software-2/)
-   -   kubuntu precise - virtualbox is crashing my real box (http://www.linuxquestions.org/questions/linux-software-2/kubuntu-precise-virtualbox-is-crashing-my-real-box-4175416540/)

eantoranz 07-13-2012 10:41 AM

kubuntu precise - virtualbox is crashing my real box
 
Hi!

I have had problems starting a virtualbox with centos 6.3 (64 bits). When I start it the real machine (a normal plain 32-bit box with ubuntu precise (updated)) either crashes or continues working but I lose input completely (all mouse or keyboard). I've been able to use alt-sysrq key combinations to make the box restart safely but it doesn't happen all the times so I'm forced to shut the box down the hard way (power button pressed for some seconds).

What could be the problem?

eantoranz 07-13-2012 10:56 AM

Seems like I'm not the only one with this problem on 12.04.

https://forums.virtualbox.org/viewtopic.php?f=7&t=49515

I have set the virtual machine to use 1 CPU and disabled IO APIC.

This is from a previous crash (taken from /var/log/syslog):

Code:

Jul 13 10:30:13 linuxerio kernel: [  241.693372] warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
Jul 13 10:31:51 linuxerio kernel: [  339.571390] EXT4-fs (sda6): Unaligned AIO/DIO on inode 5377259 by VirtualBox; performance will be poor.

Thanks in advance.

eantoranz 07-13-2012 10:59 AM

I'm about to run the virtual box instance again. I just noticed that the first message I posted from /var/log/syslog is probably added when I start virtualbox. The second was added when I started the centos instance (which is still in grub so it's working like a charm.... the problem happens when I let the OS boot).

Let's see what happens this time.

eantoranz 07-13-2012 11:01 AM

It is starting... the only things I did _differently_ this time was:

- I made sure vbox was not in control of input when I let the OS boot.
- I had set the CPU limit to 50% for this vbox instance.

eantoranz 07-13-2012 11:04 AM

I just set the CPU to 100% and restarted the same vbox instance and it worked. Then again, I made sure vbox wasn't in charge of input. I'll try this same thing for a couple of more days to see how it goes.


All times are GMT -5. The time now is 01:28 PM.