[SOLVED] virtualbox-host-kmp-default mismatch with kernal uname version
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
virtualbox-host-kmp-default mismatch with kernal uname version
After a recent opensuse tumbleweed system update, virtualbox stopped running my virtual machines. I see error:
The virtual machine 'OpenSuse 13.1' has terminated unexpectedly during startup with exit code 1 (0x1).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
MachineWrap
Interface:
IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}
In yast when trying to update virtualbox-host-kmp:
nothing provides kernel-uname-r=4.18.14.1-default needed by virtualbox-host-kmp-default-5.2.18-k4.18.14_1-1.9.x86_64
My current kernel version is 4.18.15-1-default
Should I just wait for the virtualbox repository to get updated or is there a workaround to fix the mismatch?
Virtualbox remakes it's modules on every boot by default unless you stop it.
If you have kernel 4.18.15-1, you should be able to install the source from your distro. If yopu still have the 4.18.14 kernel, why not boot that when you want virtualbox?
It references Modules.symvers in the kernel directory, so you might need to copy in the config and run 'make.' I did. But I am far from being an authority on virtualbox. Plenty of documentation exists, as a google will show.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.