Luminatio
Contributor
Contributor

VM became extremely slow after upgraded to macOS 10.14.6 [Officially Solved]

Jump to solution

------------20190827--------------------------

This issue is officially solved with Apple’s macOS 10.14.6 supplemental update.

Thanks to all of you.

A thumb down to Apple’s software team...

————————

After I upgraded my 2 MBP to 10.14.6, all of the Windows VMs became extremely slow and stuck at the login screen...

The VMs are set to use TPM, I don't know if it's relevant.

Anyone came across the same situation?

Now I cannot continue my work...really frustrating...

—————20190727————-

I’m updating this for convenient reference.

Status: This issue has not been solved yet.

Many users encountered this issue which leads to completely unusable of VMs.

And we got some replies from Fusion developers, you could help developers identify issues by replying your hardware models/is disk encrypted or have the VM encrypted etc.

We have some reports that some users found out that if set the memory of VM to 2G could help.

Re: VM became extremely slow after upgraded to macOS 10.14.6

If you don’t need to use much memory and can work with it, you might try set the memory to 2G, or maybe less than 4G is also okay?

Still we are waiting for an official solution.

------------20190809--------------------------

Thanks to ksc

Re: VM became extremely slow after upgraded to macOS 10.14.6

I updated to Fusion 11.1.1, confirmed that I can login to the system, and desktop shows normally.

As ksc says, it is a workaround which I'm not quite sure if I can trust it to do my work in it....

At least, I'm able to get my works out and change to other options now.

I'll mark this issue as resolved for now, but keep the [Workaround Released] tag in the subject.

Looks like it would take quite some time for a real fix, I'll keep an eye on this.

消息编辑者为:Liam

226 Replies
emjay73
Contributor
Contributor

Will there also be a patch for Fusion 10?

It is also affected by the slowdowns and has become virtually unusable in 10.1.6.

Thank you

0 Kudos
needtothinkofan
Contributor
Contributor

11.1.1 does not fix the this issue with Win10 client for me:

VM is not encrypted

6GB RAM (16GB MBP15)

If VMWware is allow to use 3D Accelerated / Discrete graphics then running Citrix Receiver effectively halts the VM completely (beachball /unable to do anything)

0 Kudos
DaveP
Commander
Commander

Fusion 11.1.1 makes the VM responsive but CPU usage is still very high running any guest I have (macOS, Linux Windows and ESXi). None are encrypted.

Another question should we remove the 2 lines previosuly given as a workaround:

prefvmx.useRecommendedLockedMemorySize = "FALSE"

prefvmx.allVMMemoryLimit = "4096"

0 Kudos
Wegener22
Contributor
Contributor

Doesn't work!

The new Version has the same issue for me.

I have no encryption etc., expanding the RAM to

4 GB or more leads to a laggy or unusable VMachine.

0 Kudos
DaveP
Commander
Commander

Would using swap file make a difference instead of the vmem files? Using:

mainmem.backing = "swap"

0 Kudos
hkang
VMware Employee
VMware Employee

Could you try to disable 3D and see whether it makes VM faster?

0 Kudos
F_Ps
Contributor
Contributor

The new version helps for a little while but degradates *VERY* quickly if I try to install (and uninstall) a few things that are bigger.

It becomes unusable again.

0 Kudos
nike8270
Contributor
Contributor

still same problem

my VM machine don't work even i did the supplemental update 10.14.6

grrrr

0 Kudos
ksc
VMware Employee
VMware Employee

Another question should we remove the 2 lines previosuly given as a workaround:

prefvmx.useRecommendedLockedMemorySize = "FALSE"

prefvmx.allVMMemoryLimit = "4096"

Yes. Those were much less effective than the mitigation we shipped.

Fusion 11.1.1's change only affects encrypted VMs, which now match the behavior of non-encrypted VMs. We're aware that this hasn't restored parity.

0 Kudos
zendnez
Contributor
Contributor

Appreciate the fix.

Can you please clarify if what you're now doing is storing unencrypted data in a temp file and then simply deleting that file when the VM quits? Perhaps that what you've always done and it's just the location of that file which has changed.

If that's the case, then what's the point of having an encrypted VM?

I continue to hope that you listen to the request I made earlier in this thread to allow for the use/encryption of a TPM without also forcing the encryption of the entire VHD. Even before this current regression, my Fusion VMs (encrypted or not) use more resources and cause more fan spin than the competition does. I have to use vmware in the cases where TPMs are required but the experience can be frustrating and anything you can do to reduce resource consumption will be greatly appreciated (including not requiring me to encrypt my VHDs on my already FileVault encrypted drive for the purpose of using a TPM).

Thanks.

0 Kudos
thorsten226
Contributor
Contributor

I have disabled encryption for the VM but it always restarts after about 2 min after I have logged in.

I have tried decreasing memory down to 1GB and up to 4 GB disabled and enabled accelerate 3D graphics nothing seems to make a difference. My Windows keeps on crashing. I have attached the vmware fusion log.

Starting in safe mode works.

In the event viewer I can seem some errors with

"The application-specific permission settings do not grant Local Activiation permission for the COM Server application with CLSID ... and APPID for the user NT Authority Location Serivce SID from address LocalHost (Using LRPC) running in the application container" (not full quote)

Not sure if this is related...

Update 10.08.19: I had an old backup of the encrypted VmWare image from May. I restored this and that one is running fine. I guess something broke in the newest image because of the decryption or the forceful shutdowns during the initial problems.

In Summary: ​Encrypted images seem to work again on Mac OS 10.14.6 with VmWare Fusion 11.1.1

0 Kudos
dlhotka
Champion
Champion

Ah, ok.  Thanks for the clarification.  Sounds like we need to wait for an Apple patch to really fix things?

0 Kudos
MichaelP001
Contributor
Contributor

Updated to Fusion Version 11.1.1 (14328561) and no change.  Fusion takes hours to load, with no other programs running on Mojave, and the Fusion program is unusable.  Are there other fixes coming through soon?

wila
Leadership
Leadership

Hi MichaelP001,

Depending on your host and VM configuration that might actually be another -but possibly related- issue.

Have a look at this post:

10.14.6 supplemental update hangs VMWare fusion after restart/reboot

For VMs to work reasonable on macOS 10.14.6 and Fusion 11.11.1 you still have to scale down the RAM to 2GB.

If that doesn't help then you might be hitting another issue and you could consider opening a ticket with VMware support.

--

Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva
0 Kudos
thrubovc
Enthusiast
Enthusiast

I can confirm that VMWare update 11.1.1 has fixed the problems for me.

I am running windows 10 with disk encryption and TPM. My host disk is also encrypted. My use of the VM is not heavy (particularly disk I/O heavy), so I can't tell if the problems would come back, but currently I'm seeing no lag at 3.5GB of RAM.

0 Kudos
daniele75vv
Contributor
Contributor

Resolved here too

0 Kudos
0f2g
Contributor
Contributor

So we are screwed if we cannot update to v11.1.1?  Nice, way to force an upgrade...

0 Kudos
dlhotka
Champion
Champion

The only supported version of Fusion on Mojave is 11, and 11.1.1 is a free upgrade from that.

0 Kudos
Patrick_Savary
Contributor
Contributor

Can not work on machines with more than 2gb of memory even without encryption with version 11.1.1.

I pass on Parralells trial with which it works because I can not work anymore.

I am super disappointed with the slowness of a patch

0 Kudos
dlhotka
Champion
Champion

Understand the frustration - from the root cause, Apple's bug has borked that whole thing.  Parallels probably uses a different path, so we just got 'lucky'.....I hope there is a workaround other than waiting for apple to fix their mistake.

0 Kudos