kubuntu precise - virtualbox is crashing my real box
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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).
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).
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.