ISBRendererComm : Lost connection to mksSandbox and MKS -RendererMain : Failed to start the renderer

[StefanoK]

Hi all,

I just started using a new virtual machine on my VMware Workstation. Its worth to mention that i have other VM on the station and they are working fine but for some reason on this one i got those two errors and some warnings. I tryed to google it but i didnt find any specific answer. I hope you can somehow help me. I posted down below in the attachment sector photos of the errors with logs.

Thank you in advance 🙂

[lytzen]

Thanks

[montge]

Confirming issue still exists  with 16.2.1 build-18811642

I wish that VMware's help messages were more helpful.

[hsaqallah]

I encountered the problem while trying to edit videos with Lightwork. I haven't tried the proposed solution of disabling 3D acceleration but my guess is that it'll work. Although it hurts to disable it!. I hope VMWare addresses it soon.

[lytzen]

I might depend on which version of VMware you have installed. Version 16.2.1 does not work for me, even with 3D disabled. I have to run 16.1.2. I have not yet tried version 16.2.2 though..

[gregoliver]

mks is crashing from a panic and says it is creating a coredump, but it does not actually create one:

2022-02-10T20:40:32.460Z Cr(01) mks  PANIC: VERIFY bora/mks/renderers/vulkan/vkrSwapchain.c:415
2022-02-10T20:40:32.460Z Cr(01)+ mks  
2022-02-10T20:40:32.460Z Wa(03) mks  
2022-02-10T20:40:32.460Z Wa(03)+ mks  Attempting a core dump using an unlimited size limit
2022-02-10T20:40:32.673Z Wa(03) mks  Core dumped.
2022-02-10T20:40:32.673Z In(05) mks  Core dump pipes to process /usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h, core file unreliable
2022-02-10T20:40:32.673Z Wa(03) mks  A core file is available in "/home/greg/Virtuals/Windows10-Pro/mksSandbox/core.9042"

ls -la /home/greg/Virtuals/Windows10-Pro/mksSandbox/core.9042
ls: cannot access '/home/greg/Virtuals/Windows10-Pro/mksSandbox/core.9042': No such file or directory

Systemd was intercepting it:

Process 9476 (vmx-svga) of user 1000 dumped core.
                                                  
                                                  Found module linux-vdso.so.1 with build-id: f01a5289def9bee2abdf28b4671e1f155f5f1cb8
                                                  Found module libpcsclite.so.1 with build-id: 2a59c60b46b91dbc5e4035a9e7e7a9929b8d642f
                                                  Found module libgpg-error.so.0 with build-id: 081975d0a3416374b4883b2f1639fd3c9df42390
                                                  Found module libresolv.so.2 with build-id: 0fbe5191a8f9212dd09bf0f85b08fcec995d543a
                                                  Found module libgcrypt.so.20 with build-id: 711d41580c5a8649a79a8430a985dac3e25b5ba2
                                                  Found module libcap.so.2 with build-id: 0214aa9cc6a8646eb9ec27ab7dda6a2219da6500
                                                  Found module liblz4.so.1 with build-id: fd02c4542a1ce1ad6c503b958447be1c37a4afee
                                                  Found module libzstd.so.1 with build-id: 7984add4b0ab24869c30e19cfba3637ca295dd7b
                                                  Found module liblzma.so.5 with build-id: 7fec53ce7cba9489f130c99cfd3ace82e9dde0ee
                                                  Found module libogg.so.0 with build-id: 714c2b8484f85a852e216c4fc4bb2cf92872f37e
                                                  Found module libopus.so.0 with build-id: 0717c4aa935190f889e12134adcb95f1173896e6
                                                  Found module libvorbisenc.so.2 with build-id: 68b1fdf0007c752a46482443a9b599bb6cf5a64e
                                                  Found module libvorbis.so.0 with build-id: d3aece982a2dfdf9f412b5fc8a4dc88722bde200
                                                  Found module libFLAC.so.8 with build-id: 34324bdfee454c456c4e08456152fe5b86ba331f
                                                  Found module libgsm.so.1 with build-id: f84c8103f3f95ee09f2c2888e21ff13c870ee056
                                                  Found module libasyncns.so.0 with build-id: 648745a2e1c2a0a990336ca37d634b817a6861c5
                                                  Found module libsystemd.so.0 with build-id: b61753e8440ecf39624b3e37f855941c18a69e9b
                                                  Found module libsndfile.so.1 with build-id: cd7eb73b7b9313a890809eb349ff6322a79d9191
                                                  Found module libdbus-1.so.3 with build-id: 58e800f0865bde326c5c9ce510062d5b19902f67
                                                  Found module libpulsecommon-15.0.so with build-id: 610784314edf8434b1e341c44c97a92afab2a37e
                                                  Found module libpulse.so.0 with build-id: dae2a9442ffad84ff9620bb7cb2ea33517dea455
                                                  Found module libaio.so.1 with build-id: 10d0b58965f676c6d82d836326436912cfa81b7e
                                                  Found module libnuma.so.1 with build-id: 24b3826eb785d8e4dfec3a9b8e5fe37117269d57
                                                  Found module libnss_myhostname.so.2 with build-id: 884539c682a7226ebe838279cb382c786e469e12
                                                  Found module libXau.so.6 with build-id: b6a2d4859848c28bf0a4fc8744d04b1935879af6
                                                  Found module libXfixes.so.3 with build-id: e8020da14577d275b75ed0c4cb18b1050fc33595
                                                  Found module libXrender.so.1 with build-id: 45e135fd2ee2393b7eb0c94f964542b8326582e1
                                                  Found module libxcb.so.1 with build-id: 1352e33391b3079347f320218799d6e531bd42f1
                                                  Found module ld-linux-x86-64.so.2 with build-id: 524f5518285687402d801b9c3b1e61d435e6780b
                                                  Found module libc.so.6 with build-id: d7e3e120ff5fafc298666927c6475567348588ef
                                                  Found module libpthread.so.0 with build-id: ef966cfe5a73990033e35779603c0d78401013e6
                                                  Found module libgcc_s.so.1 with build-id: 88564abce789aa42536da1247a57ff6062d61dcb
                                                  Found module libm.so.6 with build-id: 47343f97c29c4e91c841e2bfd344329a264075ad
                                                  Found module libstdc++.so.6 with build-id: 64dc8524cb0109c7f3d3c0ef3d4d6ec9979db75c
                                                  Found module libXtst.so.6 with build-id: 97ddda29c72fa18b2cae1274026730a04f8b0ae2
                                                  Found module libXcursor.so.1 with build-id: fb3d6eb4c582d4761eab821bc0ceb77fc7c2654f
                                                  Found module libXinerama.so.1 with build-id: 72d169302fe5696536345d6da1605baeb6e3bc01
                                                  Found module libXi.so.6 with build-id: e1d4fcbcab03948da50a0e175ac2459c335e7939
                                                  Found module libXext.so.6 with build-id: 08e82aa07cb7910a08d8386fb16de7896ce290f4
                                                  Found module libX11.so.6 with build-id: b63e8f330442522b1d5872d1b2ccf32702767d80
                                                  Found module libdl.so.2 with build-id: 01afa92b2c758f2702ff6bdc0f6cadeac64456f7
                                                  Found module librt.so.1 with build-id: 7942627f54693fdeb840897c0b959b7fd909f5b3
                                                  Found module vmware-vmx with build-id: 64720c96cb791ce35d5320f4c40ec9ef892bcb34
                                                  Stack trace of thread 9476:
                                                  #0  0x00007fd6c1a87ecd syscall (libc.so.6 + 0x10aecd)
                                                  #1  0x000055b0ad29a88a n/a (vmware-vmx + 0x89a88a)
                                                  #2  0x000055b0ad29aba9 n/a (vmware-vmx + 0x89aba9)
                                                  #3  0x000055b0acb3dab3 n/a (vmware-vmx + 0x13dab3)
                                                  #4  0x000055b0acb237b5 n/a (vmware-vmx + 0x1237b5)
                                                  #5  0x000055b0acefeaea n/a (vmware-vmx + 0x4feaea)
                                                  #6  0x000055b0aceff266 n/a (vmware-vmx + 0x4ff266)
                                                  #7  0x000055b0aceff818 n/a (vmware-vmx + 0x4ff818)
                                                  #8  0x000055b0acf03e0f n/a (vmware-vmx + 0x503e0f)
                                                  #9  0x000055b0acd70349 n/a (vmware-vmx + 0x370349)
                                                  #10 0x000055b0acd714c5 n/a (vmware-vmx + 0x3714c5)
                                                  #11 0x000055b0acd71a34 n/a (vmware-vmx + 0x371a34)
                                                  #12 0x000055b0acd71af0 n/a (vmware-vmx + 0x371af0)
                                                  #13 0x000055b0acd71e2a n/a (vmware-vmx + 0x371e2a)
                                                  #14 0x000055b0accee6ee n/a (vmware-vmx + 0x2ee6ee)
                                                  #15 0x000055b0acdb80be n/a (vmware-vmx + 0x3b80be)
                                                  #16 0x000055b0acdb6431 n/a (vmware-vmx + 0x3b6431)
                                                  #17 0x000055b0acd9c465 n/a (vmware-vmx + 0x39c465)
                                                  #18 0x000055b0accc41e2 n/a (vmware-vmx + 0x2c41e2)
                                                  #19 0x000055b0accc4655 n/a (vmware-vmx + 0x2c4655)
                                                  #20 0x000055b0acdb088d n/a (vmware-vmx + 0x3b088d)
                                                  #21 0x000055b0ad0ee515 n/a (vmware-vmx + 0x6ee515)
                                                  #22 0x00007fd6c1a0ab1a start_thread (libc.so.6 + 0x8db1a)
                                                  #23 0x00007fd6c1a8f650 __clone3 (libc.so.6 + 0x112650)

[gregoliver]

It is a Wayland.  When switching back to Xorg, all works as expected.

[Sylvain-French]

Same issue with 16.2.2 and Debian 11. Crash (even with 3D option disabled) and corrupt the VMDK file. Need to reinstall all.

I've waste 1 day with VMWare and I need to progress in my work. I will switch to another solution.

Previously I used v15 and Debian 10 without problem.

Good luck, but v16x seems to be an important regression.

[Thorsten200]

Hi all,

In our Company we are useing Siemens Field PG 5 for Programming Software like Simatic Manager and Tia Portal.

We have the same Laptops, but at some colleagues the VM crashes and at some clleagues it doesn't crash.

Workstation 16 Pro

VM Software Version 16.2.2 build-19200509

The VM Tools are up to date.

I read a lot about downgrading to 16.1 / or even 15.5

Could this be really the case?

In mksSandbox these following logs are posted.

2022-02-24T12:46:39.782Z In(05) svga ReplayFifo: mksReplay format version=18
2022-02-24T12:46:39.782Z In(05) svga MKSRoleReplay: MKSRoleReplay_Run: Starting.
2022-02-24T12:47:17.348Z Wa(03) svga DX11ShimOps: Intel doesn't support zeroing UAVs with other bind flags
2022-02-24T13:19:52.053Z Wa(03) svga The mksSandbox lost its connection to the main mks.
2022-02-24T13:19:52.053Z Wa(03) svga The main mks process may have crashed or hung.
2022-02-24T13:19:52.053Z Wa(03) svga Check the mksSandbox.log and vmware.log for more details.
2022-02-24T13:19:52.053Z Cr(01) svga PANIC: MKSSandboxComm: Lost connection to isbRenderer (1408)
2022-02-24T13:19:52.053Z In(05) svga CoreDump_CoreDump: faking exception to get context
2022-02-24T13:19:52.059Z In(05) svga CoreDump: Minidump file C:\Users\PC-FDE~1\AppData\Local\Temp\vmware-PC-FDE1-SC11\mkssandbox.dmp exists. Rotating ...
2022-02-24T13:19:52.059Z In(05) svga CoreDump: Current max dump count is 5.
2022-02-24T13:19:52.062Z Wa(03) svga CoreDump: Writing minidump to C:\Users\PC-FDE~1\AppData\Local\Temp\vmware-PC-FDE1-SC11\mkssandbox.dmp
2022-02-24T13:19:52.213Z In(05) svga CoreDump: including module base 0x0x7ff611980000 size 0x0x00d40000

[hsaqallah]

So I encountered this MKS during upgrading my guest Windows 10 to Windows 11 (although 3D HW Acceleration was turned off.) But the error was happening on a specific VmwarePlayer instance (I have the latest 16 version). Other instances were fine. For the faulty instance, I tried defragmenting and compacting the main vmdk hard drive (from the VMWare Hardware -> Hard Disk screen.) Then I did chkdsk /f /r on the host windows machine on the drive that has my vmdk files. Interestingly, chkdsk found some free space related errors and fixed them. After that, my guest upgrade to windows 11 worked. Not sure what step fixed it. 

[baneeishaque]

Workaround is working...

[Loren_Pechtel]

Count me amongst those for whom this is a solution.  I'm not normally doing anything in the VMs that would use 3D graphics, the loss is unimportant.

I noticed a strong pattern--it would blow up when the system was otherwise heavily loaded or otherwise not responding well.  (When a program wanted to update itself--I think it did a restore point before updating, took out a VM.)

[lytzen]

It seems to be a problem with VMware on windows only. I am running VMware Workstation 16.2.3 om my Mac at home, with 3D graphics and all enabled, with no problems at all.

If I run the exact same virtual machine on my windows 10 PC at work, any VMware Workstation installation newer than 16.1.2 will crash - even with 3D graphics disabled, and it only works on 16.1.2 because I have 3D graphics disabled.

I am considering moving to Virtual Box or qemu, to see if I can get better stability than VMware can provide.

[strudels]

tl;dr for anyone looking for a better/different workaround than disabling 3d acceleration: try switching from Nvidia to Intel integrated graphics. Doing this allowed me to continue using 3d acceleration.

I stumbled upon this issue while upgrading my ubuntu 20.04 kernel from 5.13 to 5.15 via the linux-generic-hwe-20.04 package (i.e. the package that provides the ubuntu 22.04 kernel to ubuntu 20.04). After upgrading, I ran into an issue where vmmon was not compiling correctly with the new kernel 5.15 headers. That issue was described here: https://communities.vmware.com/t5/VMware-Workstation-Pro/VMware-16-2-3-not-working-on-Ubuntu-22-04-L...

Instead of installing the kernel modules built from the vmware-host-modules github repo linked in that issue, I decided to upgrade my vmware workstation version from 16.1.2 to 16.2.4 and see if the error went away. To my relief, vmmon was able to compile, and I was able to start VMs again.

However, after starting a VM, it would hang for a while, and then eventually show this same `MKS -RendererMain` error. Indeed, disabling 3d acceleration would allow for the VM to work as normal.

Given that I started having these issues originally from my kernel 5.13 to 5.15 upgrade, and that I know ubuntu 22.04 uses both kernel 5.15 and wayland by default, I guessed that the issue of 3d acceleration not working was related to this. In ubuntu 22.04 the stack would be kernel5.15+nvidia+wayland, where my stack was kernel5.15+nvidia+x11. I used `prime-select intel` to switch from my nvidia GPU to my intel integrated graphics, and was able to start my VMs again successfully.

I have a Dell Precision 5510 laptop, with a Nvidia Quadro T1000 Mobile discrete graphics card. My VM was running Windows 10. And as previously stated my host machine was Ubuntu 20.04 w/ linux-generic-hwe-20.04 installed.

[strudels]

Looks like my theory about my issue being related to the wayland upgrade was at least partially right. I ended up finding this article: https://wiki.vi-toolkit.com/index.php?title=Vmx_hacks&mobileaction=toggle_view_desktop#Linux_Host_-_...

I added this to my `~/.vmware/config` file, and was able to continue to use my Windows 10 VM with my nvidia GPU and 3d acceleration enabled:

```
mks.enableX11Presentation=TRUE
mks.enableVulkanPresentation=FALSE
mks.enableVulkanRenderer = "FALSE"
mks.enableGLRenderer = "TRUE"
mks.vk.allowUnsupportedDevices = "TRUE"
mks.forceDiscreteGPU = "TRUE"
```

[SHoldgaard]

FYI - version 16.2.4 still requires to disable 3D Accellerated graphics. 

[malvcr]

16.2.4 build 20089737 has the same behavior when running  Linux 5.15-46 on 5.15.0 ... both with Wayland (Ubuntu on Ubuntu-Studio) ... however

I noticed that the Virtual Machine had 4GB RAM but the Graphics Memory 8GB ...

Then, without disabling the 3D Graphics, I defined 8GB RAM and 2GB of Graphics Memory and it seems that works.  Just that a remote VNC connection freeze, but could be a different issue.

[omf2]

It's happening on Workstation 16.2.4 running on a Windows 10 host with Intel integrated graphics, so it's not likely to be an NVidia issue, at least not on Windows (which makes it unlikely on Linux, I think).

[tfuto]

For all the folks, who can reproduce this error: Are you sure this is not a Windows/graphics driver issue?

- There is a "feature" in Windows, that unresponsive GPUs are reset after a timeout. (TDR - Timeout Detection and Recovery, https://learn.microsoft.com/en-us/windows-hardware/drivers/display/timeout-detection-and-recovery)

- Shared GPU memory means that GPU memory can actually be paged out.

- During paging, GPU call latency is enormous.

- Observing a call not responding within a reasonable time, Windows can decide that GPU is frozen and resets it.

I have seen this many times, also during excessive (normal) process swapping, too. Then you get MKS disconnection, etc.

When you disable 3D acceleration, you are not using the GPU's resources as heavily.

Could you please try installing the latest graphic card driver, and also change the timeout value? Please see: https://answers.microsoft.com/en-us/windows/forum/all/increase-time-out-limit/e979e2ad-e15f-450b-981...

I saw this disconnect many times, and haunted me for awhile. It happened with Win10, RTX2070 and RTX3070Ti, when not using Workstation on Hyper-V. When using Workstation with Hyper-V, these errors got very rare. I cannot reproduce this error myself deterministically. My best way to crash VMware is having a large RAM Ubu22 guest VM (32 GB on a 64 GB machine), that starts with lots of I/O on NVMe, and starting Firefox with a page that uses a DRM video decoder (Netflix is the winner, but DisneyPlus works, too). I checked with the Firefox guys, reported bugs, etc. but it seems that although there is a correlation, the error seems to be an OS issue.

Could you also please look for any errors in Event Viewer after these disconnects? Thank you.

[acinsa]

Thanks strudels. I added these lines to my vmx on my Debian Buster host with Nvidia Quadro RTX4000 and Windows10 VM. This allowed me to launch the VM without hanging and with 3D acceleration on. Great result and the performance is on a par if not slightly better than with Virtualbox.

[josifh]

Thanks hsaqallah,

---

I encountered the problem while trying to edit videos with Lightwork. I haven't tried the proposed solution of disabling 3D acceleration but my guess is that it'll work. Although it hurts to disable it!. I hope VMWare addresses it soon.

---

worked for me too on VM Player 17. Thanks for sharing.