"ERROR:  xlog flush request 0/13C8E2A0 is not satisfied"

This looks like corrupted data, perhaps caused by the storage problem that you have mentioned before. Restoring a backup may be the best way to go forward here, but you can run a REINDEX on whatever table equates to "base/16396/2619":

You should open an SR with VMware Technical Support.

Damn, that’s annoying. Personally I would uninstall / reinstall Fusion in such circumstance.

Hello Team,

We are planning to extend management to an additional data center through Layer 2, but does not want to add additional NSX-T licensing, What will be the better option

Deploy a standalone Edge as the IPSec VPN. OR Deploy a standalone Edge as the L2 VPN client.

Please help me with better option.

Hello- This issue comes when user has exceed draft emails in his/her mailbox. Please ask user to clear all draft mails from the mailbox and check if it works.

In all the years we install/upgrade with the Dell Custom ISO and than apply the latest Patches from VMware by using VUM or from Command line. 

If your Support comes directly from VMware rather than Dell that GSS often doent like the Vendor ISOs... but it was never a big deal in our cases

If you have vxRAIL than everything comes from Dell and we never install directly stuff from VMware

Regards,
Joerg

Hi Bayu,

Thank you very much for your response.

We contacted vmware. This is a bug in NSX-T version 3.0 and will be fixed in the next release.

Best regards,

Milos

Hi everyone,

I am using VMware Fusion 11.5 on my MacBook Pro (15", 2018) and for a couple of weeks now, my whole system has become mostly unusable when the VM is running.

The issue emerged when using macOS Catalina 10.15.5, so I do not think it is related to the known issue relating to the memory leak. Since then I have updated to 10.15.6, but the issue remains. I have not yet encountered the memory leak as the system is crashing before. The problem exists in both VMware Fusion 11.5.5 and 11.5.6.

What is happening? When using the VM over time the whole system (both guest OS and host OS) hangs for some seconds every other minute. After some of these freezes (sometimes just a few minutes, sometimes after an hour), everything goes black, I am back at the macOS login screen. When logging in, the VMware is not visible anymore (but still running), so I have to suspend and restart the VM. Then, again, I have a couple of minutes running the VM until the same issue happens again.

• Using a freshly booted host and/or guest OS does not make any difference.
• The issue only occurs when the VM is running - absolutely no problems, when the VM is turned off or suspended.
• It seems to me the issue occurs more quickly when I have many windows open, but I haven't validated this systematically yet.
• Deactivating 3D acceleration does not solve this issue.

When looking at Console.app the culprit seems to be macOS' WindowServer (see attached crash report):

Process:               WindowServer [288]
Path:                  /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/Resources/WindowServer
Identifier:            WindowServer
Version:               600.00 (451.4)
Code Type:             X86-64 (Native)
Parent Process:        launchd [1]
Responsible:           WindowServer [288]
User ID:               88


Date/Time:             2020-08-08 13:01:17.161 +0200
OS Version:            Mac OS X 10.15.6 (19G73)
Report Version:        12
Bridge OS Version:     4.6 (17P6065)
Anonymous UUID:        083DF09A-B169-7F44-E3EB-1E021FF1CEDC




Time Awake Since Boot: 10000 seconds


System Integrity Protection: enabled


Crashed Thread:        0  Dispatch queue: com.apple.main-thread


Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

In system.log I see a couple of messages, but I have those mdworker-logs also when the system does not freeze:

Aug  8 12:55:39 MacBook-Pro-3 VTDecoderXPCService[74544]: DEPRECATED USE in libdispatch client: Changing the target of a source after it has been activated; set a breakpoint on _dispatch_bug_deprecated to debug
Aug  8 12:55:39 MacBook-Pro-3 VTDecoderXPCService[74544]: DEPRECATED USE in libdispatch client: Changing target queue hierarchy after xpc connection was activated; set a breakpoint on _dispatch_bug_deprecated to debug
Aug  8 12:55:39 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.mdmclient.74575): Failed to bootstrap path: path = /usr/libexec/mdmclient, error = 108: Invalid path
Aug  8 12:55:40 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.backupd.74579): Failed to bootstrap path: path = /System/Library/CoreServices/backupd.bundle/Contents/Resources/backupd, error = 2: No such file or directory
Aug  8 12:56:17 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.01000000-0700-0000-0000-000000000000[74580]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:56:17 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.10000000-0300-0000-0000-000000000000[74570]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:56:17 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.03000000-0700-0000-0000-000000000000[74583]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:56:19 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.05000000-0400-0000-0000-000000000000[74584]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:56:19 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.04000000-0200-0000-0000-000000000000[74586]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:56:19 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.07000000-0200-0000-0000-000000000000[74110]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:56:22 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0F000000-0400-0000-0000-000000000000[74582]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:56:44 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.02000000-0100-0000-0000-000000000000[74588]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:56:48 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.08000000-0700-0000-0000-000000000000[74587]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:57:17 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.09000000-0100-0000-0000-000000000000[74571]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:57:17 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0C000000-0200-0000-0000-000000000000[74581]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:57:17 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.06000000-0100-0000-0000-000000000000[74578]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:57:49 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.08000000-0000-0000-0000-000000000000[75390]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:57:49 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0F000000-0500-0000-0000-000000000000[75216]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:57:49 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.05000000-0500-0000-0000-000000000000[75295]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:57:57 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.06000000-0200-0000-0000-000000000000[75759]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:58:13 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.CloudDocs.MobileDocumentsFileProvider[74229]): Service exited due to SIGKILL | sent by launchd[1]
Aug  8 12:59:06 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0F000000-0600-0000-0000-000000000000[76153]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:59:39 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.07000000-0300-0000-0000-000000000000[75296]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:00:22 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.TouchBarServer.410): Failed to bootstrap path: path = /usr/libexec/TouchBarServer, error = 108: Invalid path
Aug  8 13:00:30 MacBook-Pro-3 Microsoft Edge[74537]: BUG in libdispatch client: mach_recv, monitored resource vanished before the source cancel handler was invoked { 0x7fa521424370[source], ident: 73275 / 0x11e3b, handler: 0x106ea92f0 }
Aug  8 13:01:07 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.08000000-0100-0000-0000-000000000000[77924]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:07 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0A000000-0200-0000-0000-000000000000[77980]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:07 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0D000000-0000-0000-0000-000000000000[77981]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:07 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0E000000-0700-0000-0000-000000000000[77979]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:08 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.02000000-0200-0000-0000-000000000000[77978]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:08 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.10000000-0400-0000-0000-000000000000[77976]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:08 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.03000000-0000-0000-0000-000000000000[77975]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:09 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.01000000-0000-0000-0000-000000000000[77977]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:09 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.06000000-0200-0000-0000-000000000000[77973]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:09 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.04000000-0300-0000-0000-000000000000[77974]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:09 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0C000000-0300-0000-0000-000000000000[77847]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:09 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.05000000-0600-0000-0000-000000000000[76560]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:09 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.09000000-0200-0000-0000-000000000000[77972]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:09 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.07000000-0400-0000-0000-000000000000[77637]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:09 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0F000000-0700-0000-0000-000000000000[77821]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:12 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0B000000-0200-0000-0000-000000000000[77982]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:17 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.WindowServer[288]): Service exited due to SIGABRT
Aug  8 13:01:17 MacBook-Pro-3 sessionlogoutd[78459]: DEAD_PROCESS: 252 console
Aug  8 13:01:17 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.ViewBridgeAuxiliary[78461]): Service exited with abnormal code: 2
Aug  8 13:01:17 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.imklaunchagent): This service is defined to be constantly running and is inherently inefficient.
Aug  8 13:01:17 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.coreservices.UASharedPasteboardProgressUI): Unknown key for Boolean: DrainMessagesAfterFailedInit
Aug  8 13:01:17 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.UserEventAgent-LoginWindow): This service is defined to be constantly running and is inherently inefficient.
Aug  8 13:01:17 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.user.loginwindow.78463.4294967295): com.apple.universalaccessd (lint): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.

I have attached the vmware-vmfusion.log file, but could not find any evident problem there as well.

Using Google or searching the communities did not reveal any issue that might be related except for the memory leak bug, but since the problem occured already in the previous version of Catalina I do not think it is related.

Any ideas how to resolve this except for re-installing both guest and host OS?

Thanks

Christopher

We are running ESXi 6.7 and the decision to upgrade to 7.0 depends on several factors. We are running 50 VMs, 35 of them Windows 2019 and the rest various flavors of Linux. We also have a small VDI setup using Horizon to present 160 Windows 10 desktops that have GPUs via nVidia grid cards. In our situation, are there compelling reasons to upgrade to ESXi 7.0? Our hardware compliment of HPE DL380 Gen10s and Nimble Storage can be used with ESXi 7.

My name is Varun Shanbhag , a SEO freelancer in Bangalore providing services at an affordable price.

To be clear, your Windows 10 VM runs nested on Hyper-V, in a Windows Server VM which runs on Fusion?

Um, no, sorry... I have a macOS Catalina host system running Fusion in which the VM runs Windows 10. WindowServer was referring to the process on the host system that crashes according to the console. There is no nested VM - just plain an simple Windows 10 inside Fusion on macOS.

Best

Christopher

Seen the high-level of what was new?

Introducing vSphere 7: Features & Technology for the Hybrid Cloud - VMware vSphere Blog

Hi,

the Dl380 Gen 10 is compatible with Esxi 7.0

VMware Compatibility Guide - System Search

If there are no malfunctions that warrant an update, I would avoid the update. Like all newly released products, it is not a good rule to put them in the production environment immediately. Wait at least for the exit of the U1.

ARomeo

I see what you mean, the WindowServer component of MacOS - silly me!

When IO occurs in the disk connected by RDM, freeze occurs periodically (30 seconds).

When a problem occurs, the vmware.log displays something like the following.

I125: NVME-VMM: Controller level reset via CC.EN bit transition on nvme0

I125: NVME-CORE: Doing a partial reset of controller regs and queues.

There are no disk related errors in vmkernel or syslog.

[full log dump removed by moderator]

Moderator: Please use the Attach function in the bottom-right of the post editor to upload your full log, rather than doing a copy/paste of thousands of lines of text.

I did that, uninstalling Fusion, even finding and deleting all of the /Library and ~/Library files.  But when that was done and rebooted and then running the installer, the installer crashes the exact same way and error as running VMware Fusion itself!

What finally did work was:

TM restore back to 10.15.6 build 19G73

MacOS reinstall to 10.15.6 build 19G2006 (just released 2020-08-06)

Then VMware Fusion ran as normal

Then I thought, ok, let's go ahead and update VMware Fusion to 11.6 (with the "Do you want to update prompts?" when 11.5 starts).

BIG MISTAKE!

After the install for 11.6 completed and Fusion tried to restart itself as 11.6, it crashed with the same Termination code Namespace ...

So overnight I TM restored back to 10.15.6 build 19G73 and am not MacOS reinstalling to 10.15.6 build 19G2006 (i.e., repeating above that worked) to see if I get Fusion 11.5 back and working again....

I did see this article

• Not sure we will ever use Kubernetes but I may be wrong
• Improvements in DRS seem interesting
• We do have nVidia cards but even with the new assignable hardware feature I do not think that would change our current setup
• Our installation is fairly static, once in awhile we bring up a new VM and once in awhile we might retire a VM. The vSphere Lifecycle Manager seems to be aimed at larger installations that have more changes across time
• Improvements to vMotion are great if you have VMs that use a lot of CPU/RAM and are very busy like huge Oracle databases. vMotion in our situation works fine now. Better vMotion with VDI desktops that use nVidia grid would be nice, not sure the ESXi 7 improves anything in this area
• Two factor authentication would be nice to improve our security

I know there are a bunch of other improvements in ESXi 7. I guess what I am looking for are people who have made the jump and felt it was worth it

Yes good advice. If we do upgrade we will wait until the first major update is released

I used this vm yesterday, turned it off, tried restoring the saved session and I got this error message.

Could not open virtual machine "Windows 7 x64" (Y:\Virtual Machines\Windows 7 x64\Windows 7 x64.vmx):

 

 

Internal error.

I have the vmdk file and every other file so I Am not sure why I am getting this error, I would really appreciate some help here.