3.0.12 not playing nice with Centos 5.4?

Discussions related to using VirtualBox on Linux hosts.

3.0.12 not playing nice with Centos 5.4?

Postby dc41 » 19. Nov 2009, 21:28

I have a VM I built yesterday using VB 3.0.10 and Centos 5.4 64 bit on a Ubuntu 9.04 64 bit host. Everything worked fine.

This morning I upgraded to 3.0.12 on the host machine, and the Centos VB now won't start. The error message is:

NMI Watchdog detected LOCKUP on CPU 0

Two other VB machines (one host with Ubuntu and one with Debian) on the same host built seem to work fine. Has anyone else run into this problem? I searched the forum for the error message, but found no results. A google search found a blog entry for one person who has the same problem, but no solution was posted.

Any suggestions? Should I just downgrade to 3.0.10?

Thanks!
dc41
 
Posts: 7
Joined: 15. Jul 2009, 22:01
Primary OS: Ubuntu other
VBox Version: OSE Debian
Guest OSses: Ubuntu 9.04

Re: 3.0.12 not playing nice with Centos 5.4?

Postby Exillis » 20. Nov 2009, 06:02

You can add "nmi_watchdog=0" to the kernel boot parameters. That worked for me. Maybe this will be fixed for 3.1.0.
Exillis
 
Posts: 13
Joined: 26. Mar 2009, 06:28
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: Windows Vista, OpenSolaris, Ubuntu Linux, CentOS, Haiku, PC-BSD

Re: 3.0.12 not playing nice with Centos 5.4?

Postby dc41 » 20. Nov 2009, 18:27

Exillis wrote:You can add "nmi_watchdog=0" to the kernel boot parameters. That worked for me. Maybe this will be fixed for 3.1.0.


That's a little over my head. How do I access the kernal boot parameters if I can't get the VM to start? Or is that a setting for the virtual machine itself, and I just add that with a command line on the host?

In the meantime, I uninstalled 3.0.12 and reinstalled 3.0.10. The Centos VM works fine.

Thanks!
dc41
 
Posts: 7
Joined: 15. Jul 2009, 22:01
Primary OS: Ubuntu other
VBox Version: OSE Debian
Guest OSses: Ubuntu 9.04

Re: 3.0.12 not playing nice with Centos 5.4?

Postby Exillis » 20. Nov 2009, 18:52

At the boot screen for CentOS 5.4, press 'a' to append to the kernel boot line. This occurs very early in the boot sequence and you only have a few seconds to do this.

Then type "nmi_watchdog=0" and press RETURN to resume the boot sequence.
Exillis
 
Posts: 13
Joined: 26. Mar 2009, 06:28
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: Windows Vista, OpenSolaris, Ubuntu Linux, CentOS, Haiku, PC-BSD

Re: 3.0.12 not playing nice with Centos 5.4?

Postby XK31 » 30. Nov 2009, 21:59

I had this same problem, I'm on a Win 7 host running a CentOS 5.4 guest.
I have used the Kernel Parameter method, which worked perfectly, thank you Exillis :D

I also have XP and Fedora 11 guests, none of which have had any problems after the upgrade.
:mrgreen:
XK31
 
Posts: 1
Joined: 30. Nov 2009, 21:48
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: Fedora, CentOS

Re: 3.0.12 not playing nice with Centos 5.4?

Postby zosorock » 2. Dec 2009, 06:15

Exillis, thanks a million, this did fix it for me too. The problem started after my first boot since I upgraded from 2.2.2 to 3.0.2. Until I rebooted it was running fine.
zosorock
 
Posts: 5
Joined: 2. Dec 2009, 05:05
Location: Philadelphia
Primary OS: Debian Lenny
VBox Version: PUEL
Guest OSses: Debian Lenny, CentOS 5.5, WinXP64 & Win7


Return to VirtualBox on Linux Hosts

Who is online

Users browsing this forum: jjalocha and 14 guests