mkubecek / vmware-host-modules

Patches needed to build VMware (Player and Workstation) host modules against recent kernels
GNU General Public License v2.0
2.31k stars 381 forks source link

17.6.1 Released.. #287

Open rgadsdon opened 1 month ago

rgadsdon commented 1 month ago

Not tested yet, but release notes are here: (https://docs.vmware.com/en/VMware-Workstation-Pro/17.6.1/rn/vmware-workstation-1761-pro-release-notes/index.html) Download from the usual place..

drodiger commented 1 month ago

Known issues already: The multi-monitor feature might not work correctly in specific topologies

In specific situations, based on different hardware and topologies, the multi-monitor feature does not work as expected. You might see issues like reverting the topology to a single screen, or not cycling through monitors.

rgadsdon commented 1 month ago

Managed to get the (latest??) patchset (64kramsystem) to compile OK, but running VMware fails... VMNET seems to throw a tombstone (kernel 11.3) and there is no ethernet connection available to the client (Win10)... Reverting to 17.6 for the time being... More testing needed!

rbruce10966 commented 1 month ago

I downloaded and install latest branch and seeing error launching Window 10 virtual servers. Windows 11 work just fine.

Error: Unable to change virtual machine power state: Transport (VMDB) error -14: Pipe connection has been broken.

Debian GNU/Linux 12 (bookworm) VMWARE Workstation 17.6.1

Looks like this help fix my issue: mks.vk.allowUnsupportedDevices = "TRUE"

nastyblackrose commented 1 month ago

I install 17.6.1 on Kali Linux with kernel 6.10.11, working with 17.5.1 patch

edrozenberg commented 1 month ago

Running vmww 17.6.1 and out-of-the-box modules appear to be working fine under Slackware64 -current kernel 6.11.5. Just used the standard vmware-modconfig --console --install-all without any module patches at all, saw some warnings during module source building but appear to work fine. And the gui app "Virtual Network Editor" launches fine (did not make any changes with it yet, didn't need to yet).

nastyblackrose commented 1 month ago

Running vmww 17.6.1 and out-of-the-box modules appear to be working fine under Slackware64 -current kernel 6.11.5. Just used the standard vmware-modconfig --console --install-all without any module patches at all, saw some warnings during module source building but appear to work fine. And the gui app "Virtual Network Editor" launches fine (did not make any changes with it yet, didn't need to yet).

Running 17.6.1 working fine also under Kali Linux kernel 6.11.2 without any module patches.

gazhay commented 1 month ago

Ubuntu 24.04LTS vmware-modconfig --console --install-all fails with 17.6.1 :-(

pahole: unrecognized option '--btf_features=encode_force,var,float,enum64,decl_tag,type_tag,optimized_func,consistent_func,decl_tag_kfuncs' Try `pahole --help' or `pahole --usage' for more information.

Have the latest dwarves installed from apt.

rgadsdon commented 1 month ago

After further testing, I have reverted to 17.5.2... I found that both 17.6.0 and 17.6.1 were unstable on my laptop (2023 HP Envy 17, Intel i7) and the install hung, and vmnet threw a tombstone... Fortunately 17.5.2 with the 6.9 patchset works fine on Kernel 6.11.x (tested with 6.11.5) and 6.12-rc (tested with 6.12-rc4)..

nastyblackrose commented 1 month ago

After further testing, I have reverted to 17.5.2... I found that both 17.6.0 and 17.6.1 were unstable on my laptop (2023 HP Envy 17, Intel i7) and the install hung, and vmnet threw a tombstone... Fortunately 17.5.2 with the 6.9 patchset works fine on Kernel 6.11.x (tested with 6.11.5) and 6.12-rc (tested with 6.12-rc4)..

after successful install 17.5.2 with patchset can you try to upgrade to 17.6.1 from 17.5.2?

alairon commented 3 weeks ago

17.6.1 also worked fine on my computer without the patched modules on Fedora 40/41.

I installed the header modules with the GUI. It complained about not being able to install everything, but the logs only complained about it not being able to start the vmware service because I'm using secure boot. It does work after getting the drivers signed.

Currently tested on a new install of Fedora 41 with kernel 6.11.5-300.fc41. Had a similar result with Fedora 40 with kernel 6.11.4-201.fc40.