Captain_Clam Tracker

Re: 12.2.0 High CPU vmnet-natd

Captain_Clam — Thu, 09 Nov 2023 17:14:03 GMT

I'd say it happens to me almost every day. It's become more annoying in the last year.

Re: 12.2.0 High CPU vmnet-natd

Captain_Clam — Thu, 09 Nov 2023 16:47:38 GMT

@wb9tpg1 wrote:
I'm interested if v13 solves this issue. If it still persists I'm switching to Parallels.
Can anyone who's upgraded comment?

If you're on Apple Silicon (don't know about Intel), Parallels now looks to be a GUI wrapper around macOS's lightweight virtualisation framework. If you don't mind a little extra effort, this free app (also a wrapper around the built-in virtualisation) might be just as good: https://eclecticlight.co/virtualisation-on-apple-silicon/. It can even run two macOS VMs concurrently, unlike Parallels.

Re: 12.2.0 High CPU vmnet-natd

Captain_Clam — Thu, 09 Nov 2023 16:42:43 GMT

Been a problem for me for a while. Currently using Fusion 12.2.5 on macOS Ventura 13.6.1. Sometimes just launching Fusion results in this. Sometimes I wake up a sleeping VM (Windows or Linux) and find it has no network access. In these cases, I disconnect the network adapter and run:

sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --stop sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --start

It's an annoyance that at best wastes time. It drains my battery and impacts the performance of macOS.