Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

17.6.1 Released.. #287

Open
rgadsdon opened this issue Oct 10, 2024 · 11 comments
Open

17.6.1 Released.. #287

rgadsdon opened this issue Oct 10, 2024 · 11 comments

Comments

@rgadsdon
Copy link

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
Copy link

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
Copy link
Author

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
Copy link

rbruce10966 commented Oct 15, 2024

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
Copy link

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

@edrozenberg
Copy link

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
Copy link

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
Copy link

gazhay commented Oct 26, 2024

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
Copy link
Author

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
Copy link

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
Copy link

alairon commented Oct 30, 2024

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.

@dekernel0
Copy link

@drodiger I would agree about the multi-monitor support being an issue. Basically the second monitor does not handle any mouse clicks at all for Windows 10 clients. I can't speak for other OS's.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants