On 8/17/20 11:54 PM, jdd@dodin.org wrote:
Le 17/08/2020 à 21:30, Tom a écrit :
On 8/15/20 3:52 PM, Tom wrote:
Hi-- I lost vmlinuz's for kernels in /usr/src/ so I can't boot the previous 5.7.11 kernel hence no VMware.
this is the *source* path, necessary to compile vmware modules, not to boot the system (except if you compile your kernel yourself)
boot kernels are in /boot
- VMware will not run on kernel 5.8; as it connects it spontaneously re- boots the entire machine with no warning.
odd...
JDD-- From http://rglinuxtech.com/?p=2774 VMware – Kernel 5.8 is a Serious Problem? Posted on July 19, 2020 by RG 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. Tom -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org