All Workstation 2023 Tech Preview Discussion posts

Re: BUG: VMware NAT Service high CPU usage build-22060606

jen2 — Fri, 10 Nov 2023 16:52:24 GMT

@pstoric wrote:
I'm having the same issue as well. Where can I get that file?

https://communities.vmware.com/t5/VMware-Workstation-Pro/High-CPU-usage-by-vmnat-exe-after-upgrade-to-VMware-Workstation/m-p/2992080/highlight/true#M183202

Re: BUG: VMware NAT Service high CPU usage build-22060606

pstoric — Fri, 10 Nov 2023 16:31:12 GMT

I'm having the same issue as well. Where can I get that file?

Re: BUG: VMware NAT Service high CPU usage build-22060606

lowbi — Fri, 10 Nov 2023 07:56:02 GMT

same here. 17.5.0 build-22583795

Re: BUG: VMware NAT Service high CPU usage build-22060606

MPKLLC — Wed, 08 Nov 2023 23:42:18 GMT

Agreed. Restarting the NAT Service does not solve the high CPU usage issue. Rather, it suppresses it for a seemingly random amount of time, but it always returns.

Re: BUG: VMware NAT Service high CPU usage build-22060606

scampbell999 — Wed, 08 Nov 2023 18:32:38 GMT

Restarting the VMWare NAT Service did not solve the issue for me. I have to stop the service altogether. This means that VMs don't have network access, can't get OS updates, etc. which are often needed. Also, my company does not want to elevate privileges unnecessarily, nor allow us to do certain things on our host machines. That is why we have to use VMs! So we have to contact IT or request extra privileges to be able to stop the VMWare NAT Service.

Re: BUG: VMware NAT Service high CPU usage build-22060606

MPKLLC — Wed, 08 Nov 2023 10:55:21 GMT

Mine is the same. High CPU usage continues even after closing VMware Workstation Pro. The only way to stop it without restarting the computer is to restart the VMware NAT service.

Re: BUG: VMware NAT Service high CPU usage build-22060606

Hein_de_Lange — Wed, 08 Nov 2023 10:12:26 GMT

Mine also continues to consume high CPU even after VMWare workstation is closed

Do we still need tech preview?

spartan_n00b — Tue, 07 Nov 2023 17:16:34 GMT

I have the tech preview 2023 (Player Version e.x.p (22068932)). Will I lose any features if I download the new non-tech preview fusion? I want to stay up to date with the latest features but I don't know if I still "need" the tech preview. I'd like full 3d acceleration on my Apple silicon.

Re: Linux Kernel 6.5-rc - vmmon compile fails..

andreaplanet — Mon, 06 Nov 2023 16:32:58 GMT

In your case the error is "Skipping BTF generation xxx. due to unavailability of vmlinux". If you search for that error you find some answers. In the meantime 17.5 is out so you may try that too.

Re: BUG: VMware NAT Service high CPU usage build-22060606

scampbell999 — Wed, 01 Nov 2023 16:28:45 GMT

I am having the same problem. My computer fan is constantly running now, even when VMWare Workstation is closed.

Re: BUG: VMware NAT Service high CPU usage build-22060606

MPKLLC — Thu, 02 Nov 2023 17:07:13 GMT

I have what appears to be the same bug with a possible slight variation. In my case when the VMware NAT Service is in the high-cpu-usage state, my VMs that are configured to use NAT will not connect to the internet. Restarting the VM NAT service appears to restore network access. However, after a short while, the high CPU usage returns, brings both the VM and its host to a relative crawl. If I don't restart the VM NAT service, eventually internet connectivity for the VMs is lost until the VM NAT service is restarted again,

Re: BUG: VMware NAT Service high CPU usage build-22060606

julianranz — Thu, 26 Oct 2023 02:12:28 GMT

A very serious bug. I noticed it a week ago, when I updated to 17.5.0. Suddenly the vmnat.exe process started consuming 10% of the host cpu (no matter which guest I was running). After restarting the vmnat process (after a random time) the bug appeared again. The same solution worked for me: I replaced the vmnat.exe by the 17.0.0 version. Thanks!!!

PS: it's a very serious bug... it should be corrected !!!

Re: Linux Kernel 6.5-rc - vmmon compile fails..

bithack3r — Sun, 22 Oct 2023 15:27:21 GMT

sudo vmware-modconfig --console --install-all [AppLoader] Use shipped Linux kernel AIO access library. An up-to-date "libaio" or "libaio1" package from your system is preferred. [AppLoader] GLib does not have GSettings support. Stopping VMware services: VMware Authentication Daemon done Virtual machine monitor done make: Entering directory '/tmp/modconfig-qiW8D9/vmmon-only' Using kernel build system. /usr/bin/make -C /lib/modules/6.5.0-9-generic/build/include/.. M=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1]: Entering directory '/usr/src/linux-headers-6.5.0-9-generic' warning: the compiler differs from the one used to build the kernel The kernel was built by: x86_64-linux-gnu-gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0 You are using: gcc (Ubuntu 13.2.0-4ubuntu3) 13.2.0 CC [M] /tmp/modconfig-qiW8D9/vmmon-only/linux/driver.o CC [M] /tmp/modconfig-qiW8D9/vmmon-only/linux/driverLog.o CC [M] /tmp/modconfig-qiW8D9/vmmon-only/linux/hostif.o CC [M] /tmp/modconfig-qiW8D9/vmmon-only/common/apic.o CC [M] /tmp/modconfig-qiW8D9/vmmon-only/common/comport.o CC [M] /tmp/modconfig-qiW8D9/vmmon-only/common/cpuid.o CC [M] /tmp/modconfig-qiW8D9/vmmon-only/common/crosspage.o CC [M] /tmp/modconfig-qiW8D9/vmmon-only/common/memtrack.o /tmp/modconfig-qiW8D9/vmmon-only/common/crosspage.o: warning: objtool: CrossPage_CodePage+0x207: 'naked' return found in RETHUNK build CC [M] /tmp/modconfig-qiW8D9/vmmon-only/common/moduleloop.o CC [M] /tmp/modconfig-qiW8D9/vmmon-only/common/phystrack.o CC [M] /tmp/modconfig-qiW8D9/vmmon-only/common/sharedAreaVmmon.o CC [M] /tmp/modconfig-qiW8D9/vmmon-only/common/statVarsVmmon.o CC [M] /tmp/modconfig-qiW8D9/vmmon-only/common/task.o In file included from /tmp/modconfig-qiW8D9/vmmon-only/./include/cpu_types.h:29, from /tmp/modconfig-qiW8D9/vmmon-only/./include/modulecall.h:33, from /tmp/modconfig-qiW8D9/vmmon-only/common/moduleloop.c:33: /tmp/modconfig-qiW8D9/vmmon-only/./include/vm_basic_defs.h:779: warning: "DO_ONCE" redefined 779 | #define DO_ONCE(code) \ | In file included from ./include/linux/prandom.h:12, from ./include/linux/random.h:153, from ./include/linux/nodemask.h:97, from ./include/linux/sched.h:23, from /tmp/modconfig-qiW8D9/vmmon-only/common/moduleloop.c:31: ./include/linux/once.h:46: note: this is the location of the previous definition 46 | #define DO_ONCE(func, ...) \ | CC [M] /tmp/modconfig-qiW8D9/vmmon-only/common/vmx86.o CC [M] /tmp/modconfig-qiW8D9/vmmon-only/bootstrap/bootstrap.o /tmp/modconfig-qiW8D9/vmmon-only/common/phystrack.o: warning: objtool: PhysTrack_Add() falls through to next function PhysTrack_Remove() /tmp/modconfig-qiW8D9/vmmon-only/common/phystrack.o: warning: objtool: PhysTrack_Remove() falls through to next function PhysTrack_Test() CC [M] /tmp/modconfig-qiW8D9/vmmon-only/bootstrap/monLoader.o In file included from /tmp/modconfig-qiW8D9/vmmon-only/./include/cpu_types.h:29, from /tmp/modconfig-qiW8D9/vmmon-only/./include/modulecall.h:33, from /tmp/modconfig-qiW8D9/vmmon-only/linux/hostif.c:58: /tmp/modconfig-qiW8D9/vmmon-only/./include/vm_basic_defs.h:779: warning: "DO_ONCE" redefined 779 | #define DO_ONCE(code) \ | In file included from ./include/linux/prandom.h:12, from ./include/linux/random.h:153, from ./include/linux/nodemask.h:97, from ./include/linux/sched.h:23, from ./include/linux/binfmts.h:5, from /tmp/modconfig-qiW8D9/vmmon-only/linux/hostif.c:31: ./include/linux/once.h:46: note: this is the location of the previous definition 46 | #define DO_ONCE(func, ...) \ | CC [M] /tmp/modconfig-qiW8D9/vmmon-only/bootstrap/monLoaderVmmon.o CC [M] /tmp/modconfig-qiW8D9/vmmon-only/bootstrap/vmmblob.o /tmp/modconfig-qiW8D9/vmmon-only/bootstrap/monLoader.c: In function ‘MonLoader_Process’: In file included from /tmp/modconfig-qiW8D9/vmmon-only/./include/cpu_types.h:29, from /tmp/modconfig-qiW8D9/vmmon-only/./include/modulecall.h:33, from /tmp/modconfig-qiW8D9/vmmon-only/./common/vmx86.h:33, from /tmp/modconfig-qiW8D9/vmmon-only/linux/driver.h:32, from /tmp/modconfig-qiW8D9/vmmon-only/linux/driver.c:47: /tmp/modconfig-qiW8D9/vmmon-only/./include/vm_basic_defs.h:779: warning: "DO_ONCE" redefined 779 | #define DO_ONCE(code) \ | In file included from ./include/linux/prandom.h:12, from ./include/linux/random.h:153, from ./include/linux/nodemask.h:97, from ./include/linux/list_lru.h:12, from ./include/linux/fs.h:13, from ./include/linux/highmem.h:5, from /tmp/modconfig-qiW8D9/vmmon-only/linux/driver.c:25: ./include/linux/once.h:46: note: this is the location of the previous definition 46 | #define DO_ONCE(func, ...) \ | /tmp/modconfig-qiW8D9/vmmon-only/bootstrap/monLoader.c:794:24: warning: the comparison will always evaluate as ‘false’ for the address of ‘entries’ will never be NULL [-Waddress] 794 | if (header->entries == 0 || header->count == 0) { | ^~ In file included from /tmp/modconfig-qiW8D9/vmmon-only/bootstrap/monLoader.c:57: /tmp/modconfig-qiW8D9/vmmon-only/./include/monLoader.h:239:19: note: ‘entries’ declared here 239 | MonLoaderEntry entries[]; | ^~~~~~~ In file included from /tmp/modconfig-qiW8D9/vmmon-only/./include/cpu_types.h:29, from /tmp/modconfig-qiW8D9/vmmon-only/./include/modulecall.h:33, from /tmp/modconfig-qiW8D9/vmmon-only/common/vmx86.h:33, from /tmp/modconfig-qiW8D9/vmmon-only/common/vmx86.c:38: /tmp/modconfig-qiW8D9/vmmon-only/./include/vm_basic_defs.h:779: warning: "DO_ONCE" redefined 779 | #define DO_ONCE(code) \ | In file included from ./include/linux/prandom.h:12, from ./include/linux/random.h:153, from ./include/linux/nodemask.h:97, from ./include/linux/sched.h:23, from /tmp/modconfig-qiW8D9/vmmon-only/common/vmx86.c:31: ./include/linux/once.h:46: note: this is the location of the previous definition 46 | #define DO_ONCE(func, ...) \ | /tmp/modconfig-qiW8D9/vmmon-only/common/task.o: warning: objtool: .text: unexpected end of section LD [M] /tmp/modconfig-qiW8D9/vmmon-only/vmmon.o MODPOST /tmp/modconfig-qiW8D9/vmmon-only/Module.symvers CC [M] /tmp/modconfig-qiW8D9/vmmon-only/vmmon.mod.o LD [M] /tmp/modconfig-qiW8D9/vmmon-only/vmmon.ko BTF [M] /tmp/modconfig-qiW8D9/vmmon-only/vmmon.ko Skipping BTF generation for /tmp/modconfig-qiW8D9/vmmon-only/vmmon.ko due to unavailability of vmlinux make[1]: Leaving directory '/usr/src/linux-headers-6.5.0-9-generic' /usr/bin/make -C $PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= postbuild make[1]: Entering directory '/tmp/modconfig-qiW8D9/vmmon-only' make[1]: 'postbuild' is up to date. make[1]: Leaving directory '/tmp/modconfig-qiW8D9/vmmon-only' cp -f vmmon.ko ./../vmmon.o make: Leaving directory '/tmp/modconfig-qiW8D9/vmmon-only' make: Entering directory '/tmp/modconfig-qiW8D9/vmnet-only' Using kernel build system. /usr/bin/make -C /lib/modules/6.5.0-9-generic/build/include/.. M=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1]: Entering directory '/usr/src/linux-headers-6.5.0-9-generic' warning: the compiler differs from the one used to build the kernel The kernel was built by: x86_64-linux-gnu-gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0 You are using: gcc (Ubuntu 13.2.0-4ubuntu3) 13.2.0 CC [M] /tmp/modconfig-qiW8D9/vmnet-only/driver.o CC [M] /tmp/modconfig-qiW8D9/vmnet-only/hub.o CC [M] /tmp/modconfig-qiW8D9/vmnet-only/userif.o CC [M] /tmp/modconfig-qiW8D9/vmnet-only/netif.o CC [M] /tmp/modconfig-qiW8D9/vmnet-only/bridge.o CC [M] /tmp/modconfig-qiW8D9/vmnet-only/procfs.o CC [M] /tmp/modconfig-qiW8D9/vmnet-only/smac_compat.o CC [M] /tmp/modconfig-qiW8D9/vmnet-only/smac.o CC [M] /tmp/modconfig-qiW8D9/vmnet-only/vnetEvent.o CC [M] /tmp/modconfig-qiW8D9/vmnet-only/vnetUserListener.o /tmp/modconfig-qiW8D9/vmnet-only/userif.o: warning: objtool: VNetCsumAndCopyToUser+0x2d: call to csum_partial_copy_nocheck() with UACCESS enabled LD [M] /tmp/modconfig-qiW8D9/vmnet-only/vmnet.o MODPOST /tmp/modconfig-qiW8D9/vmnet-only/Module.symvers CC [M] /tmp/modconfig-qiW8D9/vmnet-only/vmnet.mod.o LD [M] /tmp/modconfig-qiW8D9/vmnet-only/vmnet.ko BTF [M] /tmp/modconfig-qiW8D9/vmnet-only/vmnet.ko Skipping BTF generation for /tmp/modconfig-qiW8D9/vmnet-only/vmnet.ko due to unavailability of vmlinux make[1]: Leaving directory '/usr/src/linux-headers-6.5.0-9-generic' /usr/bin/make -C $PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= postbuild make[1]: Entering directory '/tmp/modconfig-qiW8D9/vmnet-only' make[1]: 'postbuild' is up to date. make[1]: Leaving directory '/tmp/modconfig-qiW8D9/vmnet-only' cp -f vmnet.ko ./../vmnet.o make: Leaving directory '/tmp/modconfig-qiW8D9/vmnet-only' Starting VMware services: Virtual machine monitor failed Virtual machine communication interface done VM communication interface socket family done Virtual ethernet failed VMware Authentication Daemon done Unable to start services

I've followed your steps but it still doesn't work. I'm on Ubuntu 23.10.

Failed install

louyo — Fri, 13 Oct 2023 11:54:44 GMT

King of the slow group here.

I am assuming that it only installs over V17? I tried to install over 16.2.5 and it kept saying invalid SN. I did the full uninstall.

Lou

Re: Linux Kernel 6.5-rc - vmmon compile fails..

AndreD — Thu, 12 Oct 2023 06:22:01 GMT

Thank you, at first glance, I thought those were the same - just referring to some other post.

Re: Linux Kernel 6.5-rc - vmmon compile fails..

andreaplanet — Thu, 12 Oct 2023 01:23:49 GMT

You need also the patch for Kernel 6.4:

# Cd to te dir where the vmware modules are.
cd /usr/lib/vmware/modules/source
# Unpack vmnet.
tar -xvf vmnet.tar
# Add the missing include (code is just there now)
sed -i '46 a#include <net/gso.h>' vmnet-only/bridge.c
# Backup original vmnet.tar
mv vmnet.tar vmnet.tar.original
# Pack the patched vmnet.
tar -cf vmnet.tar vmnet-only

Re: Linux Kernel 6.5-rc - vmmon compile fails..

AndreD — Wed, 11 Oct 2023 21:21:45 GMT

Unfortunately, even with this fix, with 6.5.0-9 kernel I get:

/tmp/modconfig-cRIzDl/vmnet-only/bridge.c:1413:11: error: implicit declaration of function ‘skb_gso_segment’; did you mean ‘tcp_gso_segment’? [-Werror=implicit-function-declaration]
1413 | segs = skb_gso_segment(skb, 0);

Sadly, there are small open source projects that are better at upgrading kernel modules in a timely fashion than VMWare. This mess happens now and then, and Vmware does not seem to care/learn, or provide a simple fix.

Re: Linux Kernel 6.5-rc - vmmon compile fails..

felicityspyder — Wed, 11 Oct 2023 17:05:17 GMT

VMware now works after updating kernel to 6.5.4 on Pop!_OS. Thank you!

Re: Is the 2023 Tech Preview Over?

wila — Tue, 10 Oct 2023 09:06:08 GMT

Hi,

I was hoping for VMware to clarify this, but as there's no answer...

From what I've understood, you can put in your Workstation 17 key and continue using the TP for now.
Haven't tried that myself yet, but will probably have to do so later this week too, once I get back to testing.

--
Wil

Re: Linux Kernel 6.5-rc - vmmon compile fails..

andreaplanet — Sun, 08 Oct 2023 16:23:47 GMT

Here the steps for a lazy fix for kernel 6.5.5 and VMWare 17.0.2 as described here for the kernel 6.4:

# Cd to the dir where the vmware modules are. cd /usr/lib/vmware/modules/source # Unpack vmmon. tar -xvf vmmon.tar # Fix by replacing replace pte_offset_map with pte_offset_kernel sed -i 's/pte_offset_map/pte_offset_kernel/g' vmmon-only/include/pgtbl.h # Backup original vmmon.tar mv vmmon.tar vmmon.tar.original # Pack the patched vmmon. tar -cf vmmon.tar vmmon-only

Then recompile

vmware-modconfig --console --install-all