Cannot compile module with kernel kernel-6.16.7

[xvzhnang]

Unable to install all modules. See log /tmp/vmware-xvzhang/vmware-6217.log for details. (Exit code 1)
kernel-6.16.7
VMware Workstation 17.6.2 build-24409262
under Fedora42
May I ask if there are any solutions?

[Neo2SHYAlien]

The patch from here #319 (comment) works fine for 17.6.4 and kernel 6.16.7-1 Debian Sid :)

update - there is also PR #320

[FortisVoluntas]

The patch from here #319 (comment) works fine for 17.6.4 and kernel 6.16.7-1 Debian Sid :)

update - there is also PR #320

i dont know what ive done, but it worked, sadly there is no Linux beginner friendly "how to" on the mainpage.

Worked for me on:

OS: Nobara Linux 42 (KDE Plasma Desktop Edition) x86_64
Kernel: Linux 6.16.7-200.nobara.fc42.x86_64
Workstation 17.6.4 build-24832109

[leeuwtjex]

Meanwhile, I moved along to kernel 6.16.7 from 6.16.3, unfortunaly my problem keeps going on equal as in the module issue in: #319
(Cannot compile module with kernel kernel-6.16.3)

The issue: Fedora 42 host is getting unresponsive after running a vm machine.
Only opening the VMware GUI is no problem. But as soon a VM machine runs, things go wrong.

Rebooting the host is impossible in that situation and after closing VMware workstation.
When trying to reboot the laptop, this error was listed , I took it out , it looked weird.

"info rsu_prompt detected expedited stalls on CPU tasks blocking rcu_node"

Since I got desperated in options, and help seems to be nowhere, I tried a new option to handle deep technical related issues: AI....
So, i used: https://chatgpt.com/

And searched:
" fedora 42 vmware workstation host unresponsive after shutdown guest info rsu_prompt detected expedited stalls on CPU tasks blocking rcu_node "

---

INFO: rcu_sched detected expedited stalls on CPUs/tasks: ...
Blocking rcu_node structures ...

This usually indicates that a CPU or task is not responding to RCU callbacks, likely due to:

High CPU load

Task stuck in an uninterruptible state (e.g. I/O)

Guest kernel or hypervisor interaction issues

VMware Workstation kernel module or compatibility problems

The strange part: When I look in shell top, there doesn't seem to be any high cpu or processes.
There is no CPU fan noise coming from the latop, in fact it is quiet.
Nothing seems to clear indicate that the laptop is working hard or there is a vm machine stucked in a hanging process.
How can that be?

---

I tried all possibilities in the vm settings.

-switched off/on
virtualise intel /amd ....
virtualise CPU performance

-pnly 2 cpu's of 32 (32 cores in linux terms)

• I use only 8 gb of 32 available gb's on this laptop for the windows vm.

I need to give up here on my own.

Conclusion:

kernel-6.16.7
VMware Workstation 17.6.2 build-24409262
under Fedora42

Yes, using the set of vmware kernel modules and the patch mentioned earlier are working on kernel-6.16.3 / kernel-6.16.7.
That means, vmware is starting and the vmware machine can be started ( The client works great and smooth....)
However, the fedora 42 host OS freaks out and gets unusable while running the VM and after shutting it down again.
No process can be killed to stop that problem. Neither can I find what is happening to the laptop.

In short terms, the laptop gets unusable running vmware.

[Tomurisk]

Use the following if you're on Fedora:
https://github.com/Tomurisk/fedora-vmware

[Tomurisk]

Only opening the VMware GUI is no problem. But as soon a VM machine runs, things go wrong.

Disable "Accelerate 3D graphics" on VMs – Mesa is too new on Fedora to work with VMware.

[leeuwtjex]

Only opening the VMware GUI is no problem. But as soon a VM machine runs, things go wrong.

Disable "Accelerate 3D graphics" on VMs – Mesa is too new on Fedora to work with VMware.

Tried out. I can confirm this doesn't work ....for me.
Yes, I am a bit tired of vmware products, but does Qemu run vmware .vmx machines?
I don't feel like setting up a client from start again. ..it seems tough this road is dead end.

Why is Qemu preffered over virtualbox technically what is the difference?
For Qemu, can I have 'copy and paste' between host and client in Qemu?
The biggest hold back I have against qemu, it is the idea that it is designed for server visualisation.
Sure, you can install a client vm machine.
With a complex 1 liner and an .iso os- installation file you can install and autorun
a vm client in no time. But you'll need a vnc client or remote desk client to log in to the vm client.
What I like about vmware workstation or player it offers the complete client gui.

Further, qemu is not as much as user friendly when it comes to change paths of vmware machines.
The default GUI that comes with the fedore 42 installation is very simple.
Yes, I know it is possible to use server like software like cockpit, eventually in combination with some addons
to administrate qemu vm boxes in a gui environment. But again the idea is for server purpose.

I am working on a laptop and that's why this scenario feels a bit as overkill.
Sure, I know it is possible to live without gui interfaces on linux. And do it by shell.
But for the comparison, it is also possible to send an email using a complex shell command.
How many people do that in real life, except an email server administrator to test out his new configuration?

[Hyphaed]

you can try my 6.17 branch
https://github.com/Hyphaed/vmware-vmmon-vmnet-linux-6.17.x

[leeuwtjex]

Outstanding,Thanks, the patches folder in this branch are empty, the script fails when trying. Trying it manually , let me find the 'patches' folder has only a readme file but no patch files. What is supposed to be happening than?
Is it not handy to add an english version?

[Hyphaed]

@leeuwtjex thanks for the feedback :: was empty before, you are right :: I've just made a push :: you can try and tell ;)

[leeuwtjex]

[✓] Kernel detectado: 6.16.9-200.fc42.x86_64
[!] Este script está diseñado para kernel 6.17.x
[!] Tu kernel es 6.16.9-200.fc42.x86_64
¿Deseas continuar de todos modos? (s/N): s
[✓] VMware Workstation detectado
[✓] Kernel headers encontrados
[✓] Herramientas de compilación verificadas
[i] Directorio de trabajo: /tmp/vmware_build_18072
[✓] Extrayendo módulos VMware...
[i] Descargando parches base...
[i] Aplicando parches base (6.16)...
[✓] Parches base aplicados

scripts/install-vmware-modules.sh: line 131: cd: scripts: No such file or directory

[leeuwtjex]

The installer script is simply not adapted to the kernel version of this branch. Why letting other people test your scripts before testing yourself?

ls -alh /tmp/vmware_build_18213/
✗] Script de parches no encontrado: /tmp/vmware_build_18466/apply-patches-6.17.sh

18213 does not match /vmware_build_18466/

a kernel modification has been done, but was not adapted in the installer script....

Aplicar parches específicos para 6.17

SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
info "Aplicando parches específicos para kernel 6.17..."

if [ -f "$SCRIPT_DIR/apply-patches-6.17.sh" ]; then
bash "$SCRIPT_DIR/apply-patches-6.17.sh" "$WORK_DIR/vmmon-only" "$WORK_DIR/vmnet-only"
else
error "Script de parches no encontrado: $SCRIPT_DIR/apply-patches-6.17.sh"
exit 1
fi

[leeuwtjex]

manually atetmpt:

make
sudo make install
cd ../vmnet-only
make
sudo make install
bash: cd: vmmon-only: No such file or directory
Using kernel build system.
make -C /lib/modules/6.16.9-200.fc42.x86_64/build/include/.. M=$PWD SRCROOT=$PWD/.
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/kernels/6.16.9-200.fc42.x86_64'
make[2]: Entering directory '/tmp/vmnet-only'
CC [M] driver.o
CC [M] hub.o
CC [M] userif.o
CC [M] netif.o
CC [M] bridge.o
CC [M] procfs.o
CC [M] smac_compat.o
CC [M] smac.o
CC [M] vnetEvent.o
CC [M] vnetUserListener.o
LD [M] vmnet.o
vmnet.o: warning: objtool: VNetCsumAndCopyToUser+0x32: call to csum_partial_copy_nocheck() with UACCESS enabled
vmnet.o: error: objtool: init_module(): Magic init_module() function name is deprecated, use module_init(fn) instead
make[4]: *** [/usr/src/kernels/6.16.9-200.fc42.x86_64/scripts/Makefile.build:502: vmnet.o] Error 255
make[4]: *** Deleting file 'vmnet.o'
make[3]: *** [/usr/src/kernels/6.16.9-200.fc42.x86_64/Makefile:2033: .] Error 2
make[2]: *** [/usr/src/kernels/6.16.9-200.fc42.x86_64/Makefile:248: __sub-make] Error 2
make[2]: Leaving directory '/tmp/vmnet-only'
make[1]: *** [Makefile:248: __sub-make] Error 2
make[1]: Leaving directory '/usr/src/kernels/6.16.9-200.fc42.x86_64'
make: *** [Makefile:117: vmnet.ko] Error 2
[sudo] password for leeuwtje:
Using kernel build system.
make: *** No rule to make target 'install'. Stop.
Using kernel build system.
make -C /lib/modules/6.16.9-200.fc42.x86_64/build/include/.. M=$PWD SRCROOT=$PWD/.
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/kernels/6.16.9-200.fc42.x86_64'
make[2]: Entering directory '/tmp/vmnet-only'
LD [M] vmnet.o
vmnet.o: warning: objtool: VNetCsumAndCopyToUser+0x32: call to csum_partial_copy_nocheck() with UACCESS enabled
vmnet.o: error: objtool: init_module(): Magic init_module() function name is deprecated, use module_init(fn) instead
make[4]: *** [/usr/src/kernels/6.16.9-200.fc42.x86_64/scripts/Makefile.build:502: vmnet.o] Error 255
make[4]: *** Deleting file 'vmnet.o'
make[3]: *** [/usr/src/kernels/6.16.9-200.fc42.x86_64/Makefile:2033: .] Error 2
make[2]: *** [/usr/src/kernels/6.16.9-200.fc42.x86_64/Makefile:248: __sub-make] Error 2
make[2]: Leaving directory '/tmp/vmnet-only'
make[1]: *** [Makefile:248: __sub-make] Error 2
make[1]: Leaving directory '/usr/src/kernels/6.16.9-200.fc42.x86_64'
make: *** [Makefile:117: vmnet.ko] Error 2
Using kernel build system.
make: *** No rule to make target 'install'. Stop.

Great, got a corrupt vmware now.

[Hyphaed]

@leeuwtjex I'm checking

In response to "Why letting other people test your scripts before testing yourself?"

it worked on my system, yet I'm on 6.17

just be grateful instead...

I've just pushed new code to the repository

Now at the beginning will ask if you wanna install the modules for 6.16 or 6.17, since different patches are applied

If you are looking for culprits ask to broadcom why they do not update the modules according to actual main stable kernel,
I'm a community developer, no one is paying me for doing that job

Now scipt is in english (as it should had been at first time), to reach more people

Cannot do better by now, hope this updated version works or you

[leeuwtjex]

Hi Hyphaed,

Couldn't reply earlier. And had only yesterday time to test your new adds the repo.
To put it short. Metamorphose. I want to thank you. It worked 100%. I didn't expect this.
Not only did the installer scripts work full automatically, also the manual in the repo was adapted completely.
With one command the whole thing was done. Nice option in the begin to be able to select the kernel.

The most important, after compiling these modules and patches,( I would probably never found without your adds),
vmware appears now as a native app in my fedora host OS. Virtual machines runs smooth. And After exiting vmware.,
the host machine keeps running fine. No weird delays as mentioned earlier. Vmware.service keeps running and runs after booting up the host. No errors. I can reboot the host after running a VM, it takes 4 seconds. Wow!
Maybe consider a freelance job for Broadcom? They need you.

Thanks.

[Hyphaed]

@leeuwtjex would be nice getting some cash from broadcom indeed

Great to know it is working on your system