VMware – Kernel 5.8 is a Serious Problem?
Since the release of Kernel 5.8-rc1, any attempt I made to run a VMware client on that host system has failed catastrophically. ( see http://rglinuxtech.com/?p=2753 ) and the problem still persists, with 5.8-rc6.
I had posted brief details of the issue on the VMware forum some weeks ago, but there has been no useful response. https://communities.vmware.com/thread/638457
I have recently looked at the issue with other VM technologies, and found some rather alarming comments on the VirtualBox defect tracking site: https://www.virtualbox.org/ticket/19644
It is not encouraging, when their only solution seems to be to actually patch the Linux Kernel… One of the comments states”…From what I see, the kernel developers have effectively blocked all access to allocation of executable memory other than through the KVM mechanism. ”
So… It appears that the current situation, is that both VMware and VirtualBox hosts are incompatible with Kernel 5.8….?
I am now reading up on KVM etc, just in case…!
Robert Gadsdon. July 19th 2020.
“I am now reading up on KVM etc, just in case…!”
That is exactly what I have been doing the last few days.
😀
After upgrading Arch and finding kernel 5.8 running, any attempt to run existing or create new vms in VB 5.2 caused the entire system to hang, and hard. So I uninstalled VB and installed VB 6.x and this worked on my X240 but not my Optiplex. VB manager wouldn’t start, complaining about missing kernel modules. I rebooted after every change. Even tried pacman -U on kernel 5.8 to get back to the earlier kernel version
which didn’t change the missing modules issue. So I guess I get to learn KVM & libvirt again to run Windows 10 on my Arch desktop. Amazing that Arch maintainers didn’t send out an email alert on this one…