问题描述
我想在 Ubuntu 上运行 VirtualBox，它曾经工作过一段时间，但我不记得何时或为什么。但是，当我双击要运行的操作系统时，它会尝试启动 – 为虚拟操作系统打开一个窗口，给出 “host key” 消息，但 5 秒后关闭操作系统窗口并给出以下错误：
Failed to load VMMR0.ro (VERR_SUPLIB_OWNER_NOT_ROOT)
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Console
Interface:
IConsole {1968b7d3-e3bf-4ceb-99e0-cb7c913317bb}
如果我用 sudo virtualbox 运行它，我仍然会遇到同样的问题。我试过 sudo apt-get purge virtualbox 然后 sudo apt-get install virtualbox 。我注意到在 re-installation 期间，我在控制台上的所有其他输出中得到了这个：
Setting up virtualbox (4.1.12-dfsg-2ubuntu0.1) ...
* Stopping VirtualBox kernel modules [ OK ]
* Starting VirtualBox kernel modules
* No suitable module for running kernel found [fail]
有任何想法吗？
最佳答案
解决了我的 Ubuntu 12.04 安装问题
sudo apt-get purge virtualbox
sudo apt-get install build-essential linux-headers-`uname -r`
sudo dpkg -i ~/download_folder/virtualbox-4.2_4.2.12-84980~Ubuntu~precise_i386.deb
You can get the .deb files here
这几乎为我做到了！
次佳答案
我遇到了同样的问题，它有助于为当前内核安装 linux-headers 并重新安装 virtualbox-dkms 和 dkms 。
第三种答案
有相同/相似的问题：
* Starting VirtualBox kernel modules
* No suitable module for running kernel found [fail]
似乎我的问题与内核的构建有关。通过使用 dkms 进行动态构建解决：
sudo apt-get purge virtualbox
sudo apt-get install dkms build-essential linux-headers-`uname -r` linux-source
sudo apt-get install virtualbox-dkms
验证：
sudo service virtualbox status
sudo service virtualbox restart
第四种答案
已解决 here 。有一些严重的权限问题，需要进行全新安装。
编辑：报价
That listing of your /usr directory raises all sorts of red flags with the “2000 513” values for owner and group. Appearance of the numbers instead of user/group names indicates that the user and group do not exist in your system. Additionally, “2000” is a most unlikely user id for any flavor of Ubuntu. Non-system UIDs and GIDs start at 1000 and go up from there one at a time; to reach 2000 you would have to have added a thousand additional users! Similarly, system UID/GID numbering starts at 0 (which is “root”) and seldom goes as high as 200.
Does your system have any other users? If so, is it likely that one of them could have been doing unusual things without your knowledge?
When any of my systems show such unlikely happenings, my first thought is to back up all critical data, then nuke the box and reinstall everything from scratch. While all flavors of Linux are much less vulnerable than some more widely used systems, mischief is always a possibility — and gremlins can cause corruption of files without any human mischief being involved. You describe the system as “valuable” so a good backup needs to be available at all times anyway, before you make any attempt to fix things.