vmware
mksSandbox error on VMWare Workstation 17.0
Describe the bug
This is a "known bug which will be fixed in the next major VMWare Workstation version". The bug plagues VMWare Workstation since 16.x. Here we are. VMWare 17.0. The bug is still there.
Reproduction steps
- Start VM on a Linux host
- Switch to other app/window while VM is booting
- Few seconds later VM crashes with the mksSandbox error
Expected behavior
Starting VMs without mksSandbox errors.
Additional context
system
OS: Debian GNU/Linux 11 (bullseye) x86_64
Kernel: 5.19.0-0.deb11.2-amd64
Resolution: 2560x1440
DE: Plasma 5.20.5
WM: KWin
CPU: AMD Ryzen 9 5900HX with Radeon Graphics (16) @ 3.300GHz
GPU: AMD ATI 06:00.0 Cezanne
GPU: NVIDIA GeForce RTX 3080 Mobile / Max-Q 8GB/16GB
Memory: 3174MiB / 63732MiB
vmware.log
2022-11-22T12:24:53.855Z In(05) vmx Tools: Changing running status: 1 => 2.
2022-11-22T12:24:53.855Z In(05) vmx Tools: [RunningStatus] Last heartbeat value 2 (last received 0s ago)
2022-11-22T12:24:53.856Z In(05) vmx TOOLS Received tools.set.versiontype rpc call, version = 11360, type = 4
2022-11-22T12:24:53.856Z In(05) vmx TOOLS Setting toolsVersionStatus = TOOLS_STATUS_UNMANAGED
2022-11-22T12:24:53.856Z In(05) vmx Tools_SetVersionAndType did nothing; new tools version (11360) and type (4) match old Tools version and type
2022-11-22T12:24:53.856Z In(05) vmx Guest: Executing script for state change 'OS_PowerOn'.
2022-11-22T12:24:53.857Z In(05) vcpu-2 Tools: State change '3' progress: last event 0, event 1, success 1.
2022-11-22T12:24:53.905Z In(05) vmx Guest: Script exit code: 0, success = 1
2022-11-22T12:24:53.906Z In(05) vmx TOOLS state change 3 returned status 1
2022-11-22T12:24:53.906Z In(05) vmx Tools: State change '3' progress: last event 1, event 2, success 1.
2022-11-22T12:24:53.906Z In(05) vmx Tools: State change '3' progress: last event 1, event 4, success 1.
2022-11-22T12:24:53.906Z In(05) vmx Vix: [mainDispatch.c:4129]: VMAutomationReportPowerStateChange: Reporting power state change (opcode=2, err=0).
2022-11-22T12:24:53.906Z In(05) vmx Tools: Changing running status: 2 => 1.
2022-11-22T12:24:53.906Z In(05) vmx Tools: [RunningStatus] Last heartbeat value 2 (last received 0s ago)
2022-11-22T12:24:54.024Z In(05) vcpu-3 Guest: Mesa: SVGA3D; build: RELEASE; LLVM;
2022-11-22T12:24:54.024Z In(05) vcpu-3 Guest: Mesa: 21.2.6
2022-11-22T12:24:54.160Z In(05) vcpu-0 Guest: Mesa: SVGA3D; build: RELEASE; LLVM;
2022-11-22T12:24:54.160Z In(05) vcpu-0 Guest: Mesa: 21.2.6
2022-11-22T12:24:54.172Z In(05) vcpu-0 Guest: Mesa: SVGA3D; build: RELEASE; LLVM;
2022-11-22T12:24:54.172Z In(05) vcpu-0 Guest: Mesa: 21.2.6
2022-11-22T12:24:54.357Z In(05) vmx Tools_SetGuestResolution: Sending rpcMsg = Resolution_Set 2546 1259
2022-11-22T12:24:54.505Z In(05) svga SWBScreen: Screen 1 Destroyed: xywh(0, 0, 800, 600) flags=0x2
2022-11-22T12:24:54.521Z In(05) svga SWBScreen: Screen 1 Defined: xywh(0, 0, 2546, 1259) flags=0x2
2022-11-22T12:24:54.554Z In(05) mks SOCKET 2 (93) recv error 104: Connection reset by peer
2022-11-22T12:24:54.554Z In(05) mks ISBRendererComm: ISBRendererComm Socket Error: (1) Asyncsocket error.
2022-11-22T12:24:54.554Z Wa(03) mks The vmx lost its connection to the mksSandbox.
2022-11-22T12:24:54.554Z Wa(03) mks The mksSandbox process may have crashed or hung.
2022-11-22T12:24:54.554Z Wa(03) mks Check the mksSandbox.log and vmware.log for more details.
2022-11-22T12:24:54.554Z Cr(01) mks PANIC: ISBRendererComm: Lost connection to mksSandbox (3093)
mksSandbox.log
2022-11-22T12:24:33.341Z In(05) svga MKSRoleReplay: MKSRoleReplay_Run: Starting.
2022-11-22T12:24:33.713Z In(05) mks SWBWindow: Number of MKSWindows changed: 1 rendering MKSWindow(s) of total 1.
2022-11-22T12:24:33.713Z In(05) mks SWBWindow: Window 0 Defined: src screenId=-1, src xywh(0, 0, 640, 480) dest xywh(0, 0, 640, 480) pixelScale=1, flags=0xF
2022-11-22T12:24:33.713Z In(05) mks MKSXInput: XI major version 2, minor version 3
2022-11-22T12:24:33.713Z In(05) mks XINFO: X fd is 14
2022-11-22T12:24:33.713Z In(05) mks XINFO: depth 24 bpp 32 class 4
2022-11-22T12:24:33.713Z In(05) mks XINFO: ServerVendor: "The X.Org Foundation"
2022-11-22T12:24:33.714Z In(05) mks XINFO: VendorRelease: 12011000
2022-11-22T12:24:33.714Z In(05) mks XINFO: XKB available, version 1.0
2022-11-22T12:24:33.715Z In(05) mks XINFO: XTEST available, version 2.2
2022-11-22T12:24:33.715Z In(05) mks XINFO: Xinerama available
2022-11-22T12:24:33.715Z In(05) mks XKeymap_PowerOn: use evdev keycode mapping.
2022-11-22T12:24:33.718Z In(05) mks Vulkan Renderer: Supported presentation image usage flags: VK_IMAGE_USAGE_TRANSFER_SRC_BIT | VK_IMAGE_USAGE_TRANSFER_DST_BIT | VK_IMAGE_USAGE_SAMPLED_BIT | VK_IMAGE_USAGE_STORAGE_BIT | VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT | VK_IMAGE_USAGE_INPUT_ATTACHMENT_BIT
2022-11-22T12:24:33.718Z In(05) mks Vulkan Renderer: Presentation composite alpha flags = VK_COMPOSITE_ALPHA_OPAQUE_BIT_KHR
2022-11-22T12:24:33.718Z In(05) mks Vulkan Renderer: Supported swapchain length: 2..8
2022-11-22T12:24:33.733Z In(05) mks Vulkan Renderer: Using 2-image Vk swapchain
2022-11-22T12:24:33.736Z Wa(03) mks Vulkan Renderer: Using Vulkan presentation
2022-11-22T12:24:33.737Z In(05) mks MKS-HWinMux: Started VK presentation backend.
2022-11-22T12:24:33.747Z In(05) svga SWBScreen: Screen 0 Defined: xywh(0, 0, 640, 480) flags=0x0
2022-11-22T12:24:33.750Z In(05) mks SWBWindow: Number of MKSWindows changed: 1 rendering MKSWindow(s) of total 2.
2022-11-22T12:24:33.750Z In(05) mks SWBWindow: Window 1 Defined: src screenId=-1, src xywh(0, 0, 640, 480) dest xywh(0, 0, 1397, 1048) pixelScale=1, flags=0x12
2022-11-22T12:24:34.377Z In(05) svga SWBScreen: Screen 0 Resized: xywh(0, 0, 720, 400) flags=0x0
2022-11-22T12:24:34.642Z In(05) svga SWBScreen: Screen 0 Destroyed: xywh(0, 0, 720, 400) flags=0x0
2022-11-22T12:24:34.643Z In(05) svga SWBScreen: Screen 1 Defined: xywh(0, 0, 640, 480) flags=0x0
2022-11-22T12:24:48.693Z In(05) svga SWBScreen: Screen 1 Destroyed: xywh(0, 0, 640, 480) flags=0x0
2022-11-22T12:24:48.693Z In(05) svga SWBScreen: Screen 0 Defined: xywh(0, 0, 720, 400) flags=0x0
2022-11-22T12:24:51.373Z In(05) svga SWBScreen: Screen 0 Destroyed: xywh(0, 0, 720, 400) flags=0x0
2022-11-22T12:24:51.373Z In(05) svga SWBScreen: Screen 1 Defined: xywh(0, 0, 640, 480) flags=0x0
2022-11-22T12:24:51.373Z In(05) svga SWBScreen: Screen 1 Destroyed: xywh(0, 0, 640, 480) flags=0x0
2022-11-22T12:24:51.373Z In(05) svga SWBScreen: Screen 1 Defined: xywh(0, 0, 800, 600) flags=0x0
2022-11-22T12:24:54.512Z In(05) svga SWBScreen: Screen 1 Destroyed: xywh(0, 0, 800, 600) flags=0x0
2022-11-22T12:24:54.523Z In(05) svga SWBScreen: Screen 1 Defined: xywh(0, 0, 2546, 1259) flags=0x0
2022-11-22T12:24:54.544Z Wa(03) svga Vulkan Renderer: VK.QueuePresentKHR(sc->presentQueue, &presentInfo) call failed, result = VK_ERROR_OUT_OF_DATE_KHR
2022-11-22T12:24:54.547Z Wa(03) svga Vulkan Renderer: VK.AcquireNextImageKHR(dev->device, sc->swapchain, UINT64_MAX, acquireSema, VK_NULL_HANDLE, &index) call failed, result = VK_ERROR_OUT_OF_DATE_KHR
2022-11-22T12:24:54Z[+0.000] Wa(03) svga Caught signal 11 -- tid 7735 (addr 600)
2022-11-22T12:24:54Z[+0.000] In(05) svga SIGNAL: rip 0x7f646e87201e rsp 0x7f6475b59a40 rbp 0x7f6475b59ae0
2022-11-22T12:24:54Z[+0.000] In(05) svga SIGNAL: rax 0x21212121 rbx 0x7f6475b59ac3 rcx 0x7f6470411c30 rdx 0x7f6470583b40 rsi 0x7f6475b5a3c0 rdi 0x7f64686895a0
2022-11-22T12:24:54Z[+0.000] In(05) svga r8 0x7f6475b59ae0 r9 0x7f6470411c30 r10 0x0 r11 0x4 r12 0x7f6475b5a3c0 r13 0x7f64703b64c0 r14 0x0 r15 0x7f64686897f8
2022-11-22T12:24:54Z[+0.000] In(05) svga SIGNAL: stack 7F6475B59A40 : 0x0000000000000000 0x0000000000001000
2022-11-22T12:24:54Z[+0.000] In(05) svga SIGNAL: stack 7F6475B59A50 : 0x00007f6475b59b80 0x0000000000000001
2022-11-22T12:24:54Z[+0.000] In(05) svga SIGNAL: stack 7F6475B59A60 : 0x0000000000000000 0x00007f6475b59b80
2022-11-22T12:24:54Z[+0.000] In(05) svga SIGNAL: stack 7F6475B59A70 : 0x00007f6475b59ac3 0x00007f6475b59ae0
2022-11-22T12:24:54Z[+0.000] In(05) svga SIGNAL: stack 7F6475B59A80 : 0x0000000000000000 0x00007f646e8729e9
2022-11-22T12:24:54Z[+0.000] In(05) svga SIGNAL: stack 7F6475B59A90 : 0x00007f64686897f8 0x00007f6475b59ad2
2022-11-22T12:24:54Z[+0.000] In(05) svga SIGNAL: stack 7F6475B59AA0 : 0x0000000000001001 0x0000000000000000
2022-11-22T12:24:54Z[+0.000] In(05) svga SIGNAL: stack 7F6475B59AB0 : 0x00007f6475b59ac4 0x0000000000000000
This looks to be an issue with Workstation, not open-vm-tools.
Please use VMTN (https://communities.vmware.com/) or VMware Support service for further updates on this issue or other product issues unrelated to open-vm-tools.
The issue is still here with 17.0.1 build-21139696, @lemke1458 as this issue is still here for more than 2 years now, it's a "all hand on deck" situation and not VMTN (https://communities.vmware.com/) or VMware Support service as they cleary don't give f**k
@WardenCommander As @lemke1458 already mentioned, this appears to be an issue with MKS (mouse, keyboard, screen) in Workstation, not open-vm-tools. Please forward any VMTN links and/or VMware Support tickets you have raised, and I will try to escalate them for you. Thanks!
@AlexFromChaos @WardenCommander
The graphics organization is investigating the issue. Can we get the full mksSandbox.log for them?
Thanks!
Hi @dsouders, my license is from "org," my company, so I can't submit a ticket now. Waiting for my IT to reply and give me access to submit it. I can send mksSandbox.log somewhere else if you want.
@WardenCommander At this point I think the bug has enough traction that you won't need to submit a support ticket. Can you post mksSandbox.log here? Thanks!
@WardenCommander's logs indicate a Windows host, and a different error message:
VERIFY bora\mks\renderers\dx12\dx12PsoCache.cpp:378`
This error will also be attended to, but it's a distinct issue from @AlexFromChaos'.
@AlexFromChaos, please provide your complete vmware.log/mksSandbox.log logs if you can.
@jrfonseca don't understand what you are saying. I can provide these files that have been created when an error happens: mkssandbox.dmp mksSandbox.log vmware.log vmware-ui-8584.log vmware-unity-helper-13980.log vmware-vmx.dmp
also, I can provide my Win10 - Codesys.vmx
I added inside: mks.sandbox.socketTimeoutMS = "200000" hoping it will fix the issue according to the community on the VMware page.
@WardenCommander In a nutshell, there are two different bugs here. Both bugs will be addressed, but your issue is different than the one @AlexFromChaos reported, so @jrfonseca wants to also see the other logs.
@dsouders ok, so 2 different errors but both trigger mksSandbox to crash.
@dsouders @jrfonseca is there maybe some progress with this error?
For Windows hosts, you can workaround the crash by adding the following line to the VM's .vmx file.
mks.enableDX12Renderer=FALSE
Hey guys,
Try to add this line mks.forceDiscreteGPU = "TRUE" to vmx file. If you're using prime graphics on Linux host.
It solved my issue.
Ping. @AlexFromChaos, can you provide the full mksSandbox.log file?
Sorry for the long reply. I migrated my VMs to VBox long time ago, don't have the logs anymore.
Hi I have the same issue with you guyz, can anyone help me please?
here are my logs mksSandbox.log vmware.log
@henryhariyadi I have brought this latest issue to our MKS team on an internal PR.
However, you have provided very little information.
Please provide:
Host OS release and version. VM guest OS release and version (if involved) vmware.log (complete) mksSandbox.log (complete)
Thanks.
@henryhariyadi Thanks for the information and log files. I have forwrd everything the the Workstation and MKS teams.
Bug still present in Ubuntu 24.04 host with Windows 11 VM. Logs attached.
mks.forceDiscreteGPU = "TRUE" made no difference. Only way to run VM is disabling 3D graphics acceleration.
@did-vmonroig, I have brought this latest issue to our MKS team on an internal PR. Thank you for the logs and version information !
@did-vmonroig We are working on this at the mks team but meanwhile can you please try these options and see if you are able to run the VM. You will have to power off the VM and then add these in the vmx file
svga.allowAsyncReadback = "FALSE" virtualHW.version = "17" (change option to "17" if a virtualHW.version is already present)
The second option basically downgrades the VM so you won't have DX11 (DX10.1 should still be available) available so these are for checking if old workstation can still work on Meteor Lake GPUs. We are hoping to release a fix in the next workstation.
@shibdas, with those changes in vmx file the VM seems pretty stable. I'll report if I any problem arises.
@did-vmonroig that's great to hear! When you have a chance can you please attach the mksSandbox.log and vmware.log when you are running with these option. Thanks!
@shibdas Do you know when the next workstation release will be? I recently came across this error when taking a screenshot. Turning off 3D graphics helped, but it's not the best solution.
@shibdas Do you know when the next workstation release will be? I recently came across this error when taking a screenshot. Turning off 3D graphics helped, but it's not the best solution.
If you are hitting a renderer crash with 3d on that might be for a myriad of reasons. For example, there are multiple issues in the crashes reported in this thread itself. If you can provide VMware.log and mksSandbox.log then I can take a look if it's a related issue. As far the release timeline I can't comment but given previous releases I'd expect it to be very soon.
@shibdas My hardware configuration: Intel Core Ultra 7 155H Intel Meteor Lake-P [Intel Arc Graphics]
uname -a Linux 6.8.0-39-generic
I'm currently using Linux Mint because on newer Fedora kernels in vmware strange things are happening :( I'm adding the files you asked for vmware.log mksSandbox.log
I'd be happy to help with any re-testing, but I'll be back on Fedora :)