-
Notifications
You must be signed in to change notification settings - Fork 392
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
Kernel 6.9-rc1 vmnet compile fails #239
Comments
Maybe the following will help (untested):
|
I'm aware if this build failure but unfortunatley I haven't found time to look into it yet. I'll have to check what exactly does the code need to take |
Applied this, and vmnet compiled successfully with 6.9-rc1, and brief test with Win10 Guest (F40/Plasma/X11 host) showed everything appears to be working as it should.. Thanks.. |
@rgadsdon Maybe I'm too much of a n00b, but where did you apply this? |
Have you been able to figure out where to apply this change? Thanks. |
If I understand correctly, The /vmnet-only/vmnetInt.h file must be edited and some lines commented out but the problem is that in vmware-host-modules-w17.5.1/vmnet-only/vmnetInt.h there aren't such lines, which makes it impossible to follow the tasks. So in my case
I end up with a bunch of problems:
|
I applied the patch mentioned in #239 (comment) but sadly with no luck :( vmware-host-modules-w17.5.1 with kernel 6.8.7-300 (FC40). Am seeing a few warnings and then failure with this error:
|
Salut, I had the same issue and fixed it by changing the line in error (vmware-host-modules-w17.5.1/vmmon-only/common/vmx86.c:52) from |
Yes - that did the trick - thank you! |
I made it, vmmon is fully loaded and working as expected, however, vmnet is loaded but It's not working very well: This is the output of vmware.service:
When I try to load vmnet module I get this:
It keeps trying to load the module kernel but no expires. It's freaky, because the module seems loaded:
It's ClearLinux 6.8.8-1430.native kernel with VMware workstation 17.5.1 |
Yeah, while the compile works, and my VM seems to run ok, there's a pile of errors in syslog. The module seems to break the host system as it refuses to shutdown cleanly after modules are loaded |
dmesg output
|
same on 6.9rc7, asm/timex.h to linux/timex.h seems haven't done the trick I see now the line 52 comes already modified |
any news? this is my output on this morning compilation:
|
I'm sorry, I was quite busy last few weeks. I hope to get to fixing this within next few days. |
Thanks, looking forward to a fix. |
That worked as far as I can tell, nothing complaining in dmesg, and vmware seems to be working. |
@rgadsdon perfect thank you a lot
|
it works @LightJack05 :: thanks tried on Kernel 6.9 :: I'm gonna compile 6.9.1 |
nan0desu's patch works for me (VMware Workstation Pro 17.5.2 and kernel 6.9.1-1 on openSUSE Tumbleweed) |
Please, I need help on this
|
There's no point in using vmware-modconfig, it will not work. |
Hi @Cris70, please how did you apply the patch. I am having trouble getting mine to work and apply the patch. |
If you want to use vmware-modconfig, you have to use the second install method under point 0 (This is also what I do) to replace the original source files with the patched ones. |
Oh my, I feel like screaming @Cris70, it worked, thanks a lot. Do have and enjoy the rest of your day. God bless you. |
This works for me Fedora 40, 6.9.4-200.fc40.x86_64 + VMware Workstation Pro 15.5.7 build-17171714 |
Me too on Pop!_OS 22.04 LTS - 6.9.3-76060903-generic - VMware Workstation 17.5.2 build-23775571 |
After the recent takeover of VMware, I'm hoping this issue is not proving too much of a challenge to fix 'completely', now? |
Probably the opposite. Broadcom doesn't take over companies in order to improve anything. They're raising prices on their enterprise stuff 2-10x or more, they made VMWare Fusion free which means it's probably dead, and who knows about Workstation, a cheap prosumer product that's likely low or 0 priority for them. |
This code change worked for me with Kernel version 6.9.5 |
Thank you! This is very useful. |
Has anyone managed to get vmware-network (sudo vmware-networks --start) working on their system? |
For future reference and anyone who is not able to apply this. The most simple process would be:
|
Getting different errors now
the patch did fix that one error. Running Fedora Linux 40 6.9.6-200.fc40.x86_64 |
I actually have no clue what error this is, but why is the working directory here /tmp/vmware-host-modules/ Shouldnt it be something like /vmware-host-modules-workstation-17.5.1 depending on your version? Did you grab the correct one for your version? |
@naviafra I cloned the repo and set the branch to the workstation 17.5.1. Do I need to copy it over? |
With I applied patch from #239 (comment) and #239 (comment). It's working (tested with a Windows 11 VM) |
I have minimal C knowledge, so I asked claude.ai and perplexity.ai ;-) They suggested both to use Anyone know which one is better? I tested it also with rtnl and it's working (and I don't have to modify includes). BTW: perplexity suggested both (rcu* and rtnl*) |
@mkubecek I'm guessing you have reservations about nan0desu's patch? Do you recommend we just use it for now until you figure out a long term fix? EDIT: I ended up just using @nan0desu's patch for now and will replace with @mkubecek's later. |
See here for source: mkubecek#239 (comment) Signed-off-by: Nahuel Gómez <[email protected]>
Similar to mkubecek#214, add akmod configuration/support to vmware-host-modules. This will ensure Fedora users are able to get a fresh build of vmware-host-modules each time the kernel updates. Spec configuration and installation based on https://github.com/Fred78290/nct6687d. Installation for RPM: ``` make akmod ``` Test/Dev flow: ``` make clean make akmod/clean && make akmod && sudo akmods sudo systemctl start vmware.service ``` Applied fix for newer kernel: mkubecek#239
I'm new to this and I didn't fully grasp the instructions posted here. Thanks to this post on Reddit (https://www.reddit.com/r/vmware/comments/1csic8w/problems_upgrading_to_workstation_pro_1752/), I was able to resolve this issue. If anyone else is facing similar issue, following instructions might be helpful. Thanks to the community. Steps that worked for me:
|
Worked Great!. |
Adding a note, if this worked but then you get the error "Could not open /dev/vmmon:" when you try to run the VM, the solution is (after applying the patch) to just build it using the second install method from https://github.com/mkubecek/vmware-host-modules/blob/master/INSTALL instead of the first
as opposed to
|
this one works |
By hand, patch->make->install worked on player-12.5.9, able to boot and web-browse DSL2024 Linux VM on Debian 6.10.11-1~bpo12+1 host. Thanks! |
Similar to mkubecek#214, add akmod configuration/support to vmware-host-modules. This will ensure Fedora users are able to get a fresh build of vmware-host-modules each time the kernel updates. Spec configuration and installation based on https://github.com/Fred78290/nct6687d. Installation for RPM: ``` make akmod ``` Test/Dev flow: ``` make clean make akmod/clean && make akmod && sudo akmods sudo systemctl start vmware.service ``` Applied fix for newer kernel: mkubecek#239 Applied another fix for newer kernel: mkubecek#243 (comment)
It's working(Linux kali 6.11.2-amd64) |
vmmon compiles OK, but vmnet:
The text was updated successfully, but these errors were encountered: