12.2.0 High CPU vmnet-natd

[Bigdave1357]

Looks like this old bug is back in 12.2.0

After upgrading a couple of days ago I see vmnet-natd process sitting at 100% even when there are no guest OS running. Shutting down Fusion completely and starting it up clears the problem. But I'm not sure what triggers it.

Anyone else seeing this? Anyone have a better workaround or fix?

[Bigdave1357]

Hi Michael,

Thanks for taking the time to give an update. It's much appreciated.

[nwrk101]

Hi team, 

any ETA on a fix or a possible workaround?

Every windows guest I have, upon shutdown, peggs vmware-natd process at 100% CPU. 

Killing the process makes me unable to re-start the guest until either complete machine reboot, or manually restarting the process through CLI

Thanks!

-igor

[Bigdave1357]

Hi Michael,

We're all still quietly suffering with this one. Any further news on progress with a fix that you can share?

[Bigdave1357]

Just updated to macOS Ventura. Still happening.

Getting VERY old, now.

[Technogeezer]

I would not have expected any change under Ventura. The issue is with Fusion. 

I am awaiting the next Fusion version to see if they've finally addressed this. I ran into this issue constantly in earlier spins of the Tech Preview, and at that time switched over all of my VMs to using bridged networking because this problem was so annoying.

@Mikero , is there any update on this issue?

[Bigdave1357]

Claimed as fixed in Fusion 13.0 Pro.

I've just upgraded - lets see....

[Bigdave1357]

So I've updated to VMware Fusion 13.0 Pro - a paid upgrade - and despite what the release notes say this is NOT fixed.

I've already seen natd process hanging at 99.0% just as before.

I'm now going to initiate a support request since I just paid for the damned thing.

[Bigdave1357]

Seems that there is now no complimentary support available - even for new purchases.

I just paid £100 to upgrade from Fusion 12 Pro to Fusion 13 JUST to get rid of this bug.

And it isn't fixed, and I have no way to create an official support request to get this issue dealt with.

Shame on you vmWare, for removing complimentary 30 day support for new purchases.

And shame on you for not testing this properly.

BE WARNED - THIS IS NOT FIXED IN FUSION 13 PRO SO DO NOT WASTE YOUR MONEY

[sjordi]

I followed recommendations and trashed all my RealTek RTL8153 and moved to a Ethernet port using RTL8156B and I don't have that problem anymore, including in VMware Fusion 12.x...

But this is not a solution, it should be fixed once and for all by VMware. 

[Bigdave1357]

If anything, I'd say the situation is now much worse.

This afternoon I've had one of my VM's cause the vmnet-natd process to go to 99% four times.

Normally it would be about once every few days.

And the real bad news - I've had to upgrade mv VM in order to use Fusion 13, so unless I choose to revert to a backup, there isn't a way to downgrade back to Fusion 12.

YOU HAVE BEEN WARNED!

[Bigdave1357]

@Mikero please take a look at this again and urge your team to attend to the problem.

It is most definitely not fixed - it's worse.

[ColoradoMarmot]

You can downgrade.  Just uninstall tools, shut down, set the virtual hardware back one version.  Remove 13, install 12, boot the VM, and install those tools.

[gringley]

A general observation for everyone - The new versions of Fusion have had the option to install as a 30 day trial for years now.  I never buy on "opening day" but rather give it a few days in the trial mode.  Something for folks to try and remember for the future.

[Bigdave1357]

I've managed to obtain some official support for this issue.

A support case is now open and I'm awaiting feedback.

[Technogeezer]

I just started seeing this with Fusion 13 on my Intel Mac mini 2014. Still not fixed. I too have a support request opened with VMware. I’m asking what they need to collect as I’m sure the only way to get to resolution is to catch it as it’s happening. And I can’t keep vmnet-natd at 100% cpu and try to get other work done. 

[lvmwary2]

It's been months and still Fusion 13 shows the same bug - do Vmware know or care?

[Bigdave1357]

They do care, and they do know about it.

I have a support case open with them about this issue, and they have asked for the usual diagnostic information.

Strangely, my machines seems to have stopped showing the bug, but I'm sure it's only a matter of time. As soon as I see it again, I'll provide the necessary information to vmWare, and hopefully we can get a resolution.

[zhenyuzhao]

Hi, I am seeing the high CPU usage problem as well. I run VMware Fusion 12.2.5 on macOS 12.6.2 Monterey. I notice that this problem only appears in mornings after waking my laptop from sleep. For now, I simply forcefully kill the vmnet-natd process to get around for the day. A fix would be much appreciated it. 

[zhenyuzhao]

Just would like to check in if there is any bug fix to the issue. I do have a workaround but am annoyed to repeat the same process very so often and it makes me feel stupid about this. I am using the latest 12.2.5 and don't want to downgrade to earlier release. I also don't want to pay for another upgrade. It is unfortunate that I just bought this version last year right before 13 is released. And it seems that VMware has moved on to 13 but they could release a hotfix or sth like that. This is definitely a priority issue. 

[Bigdave1357]

Having purchased V13 I obtained a limited period technical support facility so I opened a support case on this issue.

VMWare have responded and initiated a case.

However, for some strange reason my installation has stopped showing the problem. It's supposed to have been fixed in V13. When it was released the release notes explained that this problem had been resolved. However, later on those release notes were changed to show that it has not been fixed. I don't know if this is as a result of my case being opened or not.

Anyway, for me, it does seem to have been fixed - or at least it has gone away. I definitely had recurrences of this problem having upgraded to V13 for about a week. And then it's stopped. I've not had any occurrences for weeks, now. I've had no hot-fix from vmWare, and the only thing that has changed on my machine is the patch from Apple to bring my up to 13.1 on Ventura. Maybe the latter has sorted it.

I've informed VMware of my change in circumstances and they have kept the case open in case it re-occurs.

Maybe others can do the same as me: upgrade to paid version of 13, open a support case, and then catch the bug and send the necessary files.