On Thu, Jan 11, 2024 at 4:06 AM ja <ja@xxxxxxxxxx> wrote: > > > I had host crashes with some kernels and just stayed with an older kernel. > The latest kernels are now working fine with WS 17.5.0 > It was really a kernel problem not a VMware problem. > See > https://github.com/mkubecek/vmware-host-modules/tree/master > That is not a kernel problem. That is a problem with a 3rd party module not working right with a new kernel. Note that 3rd party modules break all of the time because of kernel changes and as such are best to avoid unless absolutely necessary. And since vmware needs this 3rd party module to work I am going to suspect that vmware is somehow funding the module (since no one else would likely care), and since VMware needs this module to work then it is a VMWare problem. If there is any other way (KVM/QEMU) to work without a 3rd party module I will take it. 3rd party modules are typically a few weeks behind the current kernels (and sometimes never updated reliably) and as such will break with new kernels. -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
