I’m using the free version of VMWare Player (ver : 15.5.6) on a Open Suse Linux Tumbleweed system.
A few days ago I have done an Update of my system anda new version of Kernel was installed (I mean 5.8-0.1, not so sure because I’m not on the computer now)
Usualy, after a Kernel update I have to re-compile the VMMON and VMNET files of VMWare… Sometimes VMWare do it automatically and sometime I have to do manually… But VMWare always start…
After update and reboot VMWare don’t start without error message… I try to start in console mode and I got this :
I don’t know if the problem is due to VMWare or Kernel, seems to be the Kernel because I try to uninstall and reinstall VMWare and the problem is still there.
I also try to re-compile the VMMON and VMNET files without success…
I have posted this demand on the French Suse forum (Alionet) and also on the VMWARE (French and english forum) and unfortunally no responses…
Seems I’m not alone because I have seen a post about this same error and Virtual Box
Hope someone have an idea about this annoying problem
Hi and welcome to the Forum
It’s a security change to the kernel that both VMware and VirtualBox need to fix (I think they are trying to work around [as in break security <shrug>]).
Is there a later version of VMware available, if so try that. Else boot to the old kernel until it’s fixed. The other option which some Forum users have done is (and suggested by the openSUSE VirtualBox maintainer as a second option) is switching to kvm/qemu.
Thank you very much to spend your time answer me.
I have checked this morning and there is no new version of VMWare (15.5.6) …
I know the workaround solution to boot on the old kernel, I have try and it’s running so if necessary I can use it waiting for the new version of VMWare.
Thank you again and I will come back when a solution or anything else fix the problem
Have nice day
Philippe
Thank you very much to spend your time answer me.
Like I wrote to malcolmlewis I understood that I have to wait for a news version of VMWare that will support, I hope, the 5.8 Kernel…
The good thing is that on this list I have had an answer … that’s really great!
I’m depending on a working virtual machine, so I also have to keep kernel 5.7.11; this means to lock the kernel packages against updates.
I saw that it is also possible to start the old kernel in Grub (Advanced options), but then I had to lock the package virtualbox-kmp-default so that it won’t build new modules for the 5.8 kernel on update.
How long are the old kernels available in Grub? If I cannot make sure that the 5.7 kernel is kept in my system until Virtualbox runs with 5.8, I will have to return to locking the complete kernel package set.
Oh my, this is one of the worst showstoppers that I ever had. >:(
I’m not using that software, so I cannot check. But I think the modules will go in “/lib/modules/‘kernel-version’”, so building a new kernel module should not wipe out the working one.
[/QUOTE]How long are the old kernels available in Grub? If I cannot make sure that the 5.7 kernel is kept in my system until Virtualbox runs with 5.8, I will have to return to locking the complete kernel package set.[/QUOTE]
You have some flexibility in configuring that.
On my Tumbleweed systems, the multiversion line in “/etc/zypp/zypp.conf” reads:
As you can see, I have inserted “oldest,” at the beginning of the list. And, at present, my oldest kernel is a 5.7 kernel. So that will stay available, until I manually remove that kernel (I use the “Versions” tab in Yast software management to manually remove kernels).
My current plan is to remove that 5.7 kernel when go to a 5.9 kernel, but only if everything is working on 5.8 kernels. After removal, a 5.8 kernel will be the oldest.
Coming back just to say that the problem is fixed with the VMware Workastation 16 …
New version of VMware issued this day.
I have installed on my Tumbleweed with the kernel 5.8 and it’s works perfectly
