nmi_watchdog / virtualbox issue
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 Code:
vboxdrv: Trying to deactivate the NMI watchdog permanently... append = "nmi_watchdog=0" Code:
$ cat /proc/interrupts | grep NMI |
A few days ago I ran across this on the vbox forum
http://forums.virtualbox.org/viewtop...71d3d508392525 |
Ah so it's not supported yet for 2.6.32? Anyone else tried using vbox [puel] with this new kernel?
|
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. |
Now it works for me after the first try, weird.
Code:
/etc/rc.d/rc.vboxdrv start |
Quote:
Code:
root@silas64:~# /etc/rc.d/rc.vboxdrv setup |
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 |
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. |
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 |
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 |
Code:
mingdao@silas64:~$ lsmod | grep vbox |
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 |
watch me copy from .bash_history
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:
Code:
mingdao@silas64:~$ ls -l /etc/init.d/vboxdrv That's all, folks! |
Quote:
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 |
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 |
All times are GMT -5. The time now is 06:03 AM. |