[SOLVED] nmi_watchdog / virtualbox issue

~sHyLoCk~ · 12-11-2009, 10:04 AM

At first I though while using localmodconfig I must have selected / deselected some thing while building 2.6.32.1 kernel, so I used the generic config this time and rebuilt the 2.6.32.1 kernel, still the issue arises:

Code:

/etc/rc.d/rc.vboxdrv start
Starting VirtualBox kernel module ...failed!
  (modprobe vboxdrv failed. Please use 'dmesg' to find out why)

dmesg shows:

Code:

vboxdrv: Trying to deactivate the NMI watchdog permanently...
vboxdrv: NMI watchdog either active or at least initialized. Please disable the NMI
vboxdrv: watchdog by specifying 'nmi_watchdog=0' at kernel command line.

However I passed at kernel parameter:

append = "nmi_watchdog=0"

Code:

$ cat /proc/interrupts | grep NMI
 NMI:          0          0   Non-maskable interrupts

I'm using the virtualbox 3.1.0

slackass · 12-11-2009, 11:23 AM

A few days ago I ran across this on the vbox forum
http://forums.virtualbox.org/viewtop...71d3d508392525

~sHyLoCk~ · 12-11-2009, 04:58 PM

Ah so it's not supported yet for 2.6.32? Anyone else tried using vbox [puel] with this new kernel?

Bruce Hill · 12-15-2009, 06:13 PM

Just got through installing VirtualBox-3.1.0-55467-Linux_amd64.run with
Linux silas64 2.6.32.1 #2 SMP Tue Dec 15 22:22:20 CST 2009 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 5000+ AuthenticAMD GNU/Linux
Everything working fine here.

~sHyLoCk~ · 12-15-2009, 08:08 PM

Now it works for me after the first try, weird.

Code:

/etc/rc.d/rc.vboxdrv start
Password:
Starting VirtualBox kernel module ...failed!
  (modprobe vboxdrv failed. Please use 'dmesg' to find out why)
/etc/rc.d/rc.vboxdrv start
Starting VirtualBox kernel module ...done.

Bruce Hill · 12-15-2009, 09:07 PM

Quote:

Originally Posted by ~sHyLoCk~

Now it works for me after the first try, weird.

Code:

/etc/rc.d/rc.vboxdrv start
Password:
Starting VirtualBox kernel module ...failed!
  (modprobe vboxdrv failed. Please use 'dmesg' to find out why)
/etc/rc.d/rc.vboxdrv start
Starting VirtualBox kernel module ...done.

My command was different:

Code:

root@silas64:~# /etc/rc.d/rc.vboxdrv setup

~sHyLoCk~ · 12-15-2009, 09:23 PM

Well the setup command is run once to compile the virtualbox modules, and then usually you add

Code:

if [ -x /etc/rc.d/rc.vboxdrv ]; then
    /etc/rc.d/rc.vboxdrv start
fi

in rc.local to load the modules.

Bruce Hill · 12-15-2009, 10:06 PM

I've always run setup once and never anything else.
I assume installing VirtualBox takes care of that,
because it's there and I didn't manually add it.

~sHyLoCk~ · 12-15-2009, 10:11 PM

Hmm, but are the modules "vboxdrv, vboxnetflt and vboxnetadp" loded automatically for you? It doesn't for me unless I insmod or modprobe them manually.

Regards

Didier Spaier · 12-15-2009, 10:44 PM

Did you (re)install VirtualBox after having upgraded to 2.6.32 ?

Whenever you make a new kernel, afterwards you need to make and install again VirtualBox modules for it. I removed VB now but as far as I remember just do this as root:

Code:

cd /opt/VirtualBox-<version>/src
make all
make install
make load

Then VirtualBox should work.

Bruce Hill · 12-15-2009, 11:02 PM

Code:

mingdao@silas64:~$ lsmod | grep vbox
vboxdrv              1705748  1

I didn't need or build the modules "vboxnetflt" and "vboxnetadp".

~sHyLoCk~ · 12-15-2009, 11:09 PM

Didier Spaier

Hi, I have indeed done that. Here let me post snaps instead so that people can get a clear picture of what's happening and tell me why it's happening.
http://omploader.org/vMzA2Yw/snapshot2.png

Then I try to manually load them using rc.vboxdrv:

http://omploader.org/vMzA2ZA/snapshot3.png

Then it works obviously, but why isn't it working at startup?

Bruce Hill

Hi, can you please check your /etc/rc.d/rc.local to see if the rc.vboxdrv is started for you?

Regards

Bruce Hill · 12-15-2009, 11:22 PM

I did this fellers:

1 - aria2c http://www.jp.kernel.org/pub/linux/kernel/v2.6/linux-2.6.32.1.tar.bz2{,,,,,,,,,,}
2 - aria2c ftp://download.nvidia.com/XFree86/Linux-x86_64/190.42/NVIDIA-Linux-x86_64-190.42-pkg0.run{,,,,,,,,,,}
3 - aria2c http://download.virtualbox.org/virtualbox/3.1.0/VirtualBox-3.1.0-55467-Linux_amd64.run{,,,,,,,,,,}
4 - build and install new kernel
5 - sudo sh VirtualBox-3.1.0-55467-Linux_amd64.run (had version 3.0.8)
6 - reboot
7 - sh /server2/Linux-apps/NVIDIA-Linux-x86_64-190.42-pkg0.run
8 - /etc/rc.d/rc.vboxdrv setup

Yes, Didier Spaier, you must build VirtualBox modules for new kernels.

Here's a copy and paste from "acroread /opt/VirtualBox/UserManual.pdf"

Quote:

2. The kernel of your Linux host got updated. In that case, the kernel module will
need to be reinstalled by executing (as root):
/etc/init.d/vboxdrv setup

Only thing is, Slackware has a different $PATH:

Code:

mingdao@silas64:~$ ls -l /etc/init.d/vboxdrv
ls: cannot access /etc/init.d/vboxdrv: No such file or directory
mingdao@silas64:~$ ls -l /etc/rc.d/rc.vboxdrv
-rwxr-xr-x 1 root root 11147 2009-12-16 07:42 /etc/rc.d/rc.vboxdrv

Maybe I did it wrong, but the manual is usually helpful.

That's all, folks!

Bruce Hill · 12-15-2009, 11:30 PM

Quote:

Originally Posted by ~sHyLoCk~

Bruce Hill

Hi, can you please check your /etc/rc.d/rc.local to see if the rc.vboxdrv is started for you?

Regards

See your post #8 and my post #9. That was obviously added by
VirtualBox because (a) I didn't do it, (b) it's not in my .bash_history,
and (c) it has no comments by me, which it would if I entered it.

Code:

mingdao@silas64:~$ cat /etc/rc.d/rc.local
#!/bin/sh
#
# /etc/rc.d/rc.local:  Local system initialization script.
#
# Put any local startup commands in here.  Also, if you have
# anything that needs to be run at shutdown time you can
# make an /etc/rc.d/rc.local_shutdown script and put those
# commands in there.

# Start vboxdrv
# If you do not wish this to be executed here then comment it out,
# and the installer will skip it next time.
if [ -x /etc/rc.d/rc.vboxdrv ]; then
    /etc/rc.d/rc.vboxdrv start
fi

~sHyLoCk~ · 12-15-2009, 11:39 PM

Bug: http://www.virtualbox.org/ticket/4529
Patches: http://www.virtualbox.org/changeset/25365
http://www.virtualbox.org/changeset/25366

Will make the changes and see if it works for me.

Thanks again everyone.

Regards