2/29/2024 0 Comments Virtualbox kernel not installed![]() ![]() Yes of course it IS a local screwup, and somebody ages ago, I don't remember if here in this thread or in the forum, confirmed it was caused by some garbage left behind by previous versions OF VIRTUALBOX. I have no doubt a fresh install works pretty well, but you cannot expect users to always wipe out their hard drive and reinstall everything from scratch every time they need to upgrade VB. Have you ever tried on a distribution that has been upgraded several times, and where you have upgraded VirtualBox several times? I already said that DKMS works very well for us on various distributions It's only a nuisance bug, but it's been a nuisance for a long time. Thanks for your attention to this old bug. If you can suggest some debugging steps, I'll be glad to perform them on the next kernel update. Plainly shows that a parameter that's supposed to hold the name of the vbox nf file is unexpectedly empty, and so of course the file isn't found or processed. I haven't tried to do any debugging of the vbox install scripts, but to me, the error It just happened again with the versions I cited above. I've done that many times, and each time the problem has come back on the next kernel update. ![]() Or uninstall dkms, remove /var/lib/dkms, reinstall dkms, and try again, which amounts to the same thing. The standard advice is to remove old directories in /var/lib/dkms/vboxhost, and try again. After reboot, you have to run /etc/init.d/vboxhost setup or dpkg-reconfigure virtualbox-4.3 to rebuild them, before you can run any virtual guests, as the OP reported. At each kernel update, the infamous error messageĪppears, and the vbox kernel drivers (vboxhost, etc.) don't get rebuilt. This problem has existed for years, and still does with Virtualbox 4.3.20 and the latest kernels (currently 3.13.0.40.47 in Ubuntu).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |