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?
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.