Original Message:
Sent: Jul 11, 2025 11:37 AM
From: xxx
Subject: Graphics artifacts suddenly fill the VM screen after long use of a Kali Linux VM guest with 3D acceleration enabled
The same issue was reproduced today. And the corresponding attachment below contains all the logs you requested:
* vmware.log and mksSandbox.log are generated under full debugging information mode.
* kern.log is copied directly from the Kali Linux VM.
* dmesg.log is the output of the dmesg command from the Kali Linux VM.
Again, I removed some sensitive information for security reasons.
And I noticed the following error in the log:
* vmware.log contains huge SVGA Driver errors.
* kern.log contains vmwgfx errors
I hope these logs can assist in identifying and resolving the issue efficiently.
Original Message:
Sent: Jul 10, 2025 01:32 PM
From: Shibdas Bandyopadhyay
Subject: Graphics artifacts suddenly fill the VM screen after long use of a Kali Linux VM guest with 3D acceleration enabled
Also please attach dmesg.log and /var/log/kern.log from the Kali linux guest. Thanks!
Original Message:
Sent: Jul 09, 2025 10:23 PM
From: xxx
Subject: Graphics artifacts suddenly fill the VM screen after long use of a Kali Linux VM guest with 3D acceleration enabled
Attached are all the log files from the folder where the Kali Linux VM is stored. Some sensitive information has been excluded for security reasons.
Original Message:
Sent: Jul 09, 2025 12:39 PM
From: Shibdas Bandyopadhyay
Subject: Graphics artifacts suddenly fill the VM screen after long use of a Kali Linux VM guest with 3D acceleration enabled
Can you please attach vmware.log and mksSandbox.log from the VM? Thanks!
Original Message:
Sent: Jul 09, 2025 10:43 AM
From: xxx
Subject: Graphics artifacts suddenly fill the VM screen after long use of a Kali Linux VM guest with 3D acceleration enabled
I tested a new vmx configuration today, and the same problem still occurs after the Kali Linux VM guest has been running continuously for about 14 hours (using "Windows PC host 2" as previously described):
```
mks.enableDX12Presentation = "FALSE"
mks.enableVulkanRenderer = "TRUE"
# mks.vk.forceDevice = "NVIDIA"
mks.vk.allowMultiGPU = "TRUE"
```
Original Message:
Sent: Jul 07, 2025 04:56 PM
From: Shibdas Bandyopadhyay
Subject: Graphics artifacts suddenly fill the VM screen after long use of a Kali Linux VM guest with 3D acceleration enabled
For this system, instead of the running on DX12 renderer using the config options
mks.enableDX12Presentation = "FALSE"
mks.enableVulkanRenderer = "FALSE"
Can you instead use these config options and run on vulkan renderer and check if you still hit the crash. If you see rendering corruption (right at the beginning) add mks.enableDX12Presentation = "FALSE" too.
mks.vk.forceDevice=NVIDIA
mks.vk.allowMultiGPU=TRUE
Original Message:
Sent: Jul 07, 2025 09:52 AM
From: xxx
Subject: Graphics artifacts suddenly fill the VM screen after long use of a Kali Linux VM guest with 3D acceleration enabled
This is the mksSandbox log file associated with the ISBRenderComm error.
Original Message:
Sent: Jul 07, 2025 09:17 AM
From: xxx
Subject: Graphics artifacts suddenly fill the VM screen after long use of a Kali Linux VM guest with 3D acceleration enabled
Today I added the following two new lines to the vmx file of my Kali Linux VM guest:
```
svga.noScreenBuffering = "TRUE"
mks.noScreenBuffering = "TRUE"
```
After running this VM continuously for 13 hours, the VM simply crashed with the following error:
This is something I have never encountered before.
Original Message:
Sent: Jul 05, 2025 11:03 AM
From: xxx
Subject: Graphics artifacts suddenly fill the VM screen after long use of a Kali Linux VM guest with 3D acceleration enabled
Description:
When "Accelerate 3D graphics" is enabled for a Kali Linux VM guest, its desktop environment (GNOME Wayland) becomes filled with graphical artifacts after the VM has been running continuously for around 20 hours on a Windows 11 host (physical machine). At this moment, the Kali Linux VM guest continues running, and the graphical interface can be restored by rebooting the VM.
This issue does not usually occur during a short-term running Kali Linux VM guest, like 4 hours.
This issue has persisted for at least six months and can be consistently reproduced on two different Windows 11 PCs with different hardware configurations.
Below are more details.
Windows PC host 1:
```
OS: Windows 11 Pro for Workstation, 24H2, build 26100.3775
Features:
Virtual Machine Platform [Disabled]
Windows Hypervisor Platform [Disabled]
Windows Sandbox [Disabled]
Windows Subsystem for Linux [Disabled]
Vitalization-based security [Disabled]
CPU: AMD Ryzen 9 9950X
GPU: AMD Radeon Graphics (integrated in the CPU)
GPU driver: AMD Software Adrenalin Edition 25.6.1
VMware Workstation Pro 17.6.3 build-24583834
```
Windows PC host 2:
```
OS: Exactly the same as PC 1
CPU: AMD Ryzen Threadripper Pro 5975WX
GPU: Nvidia GeForce RTX 4060 Ti 16GB
GPU driver: Nvidia Studio Driver 576.80
VMware Workstation Pro: Exactly the same as PC 1
```
Kali Linux VM guest：
```
OS: Kali Linux 2025.2, kernel 6.12.33+kali-amd64
mesa: 25.0.5-2
Desktop environment: GNOME 48.1, Wayland
vmx file:
mks.enable3d = "TRUE"
mks.enableDX12Presentation = "FALSE"
mks.enableVulkanRenderer = "FALSE"
mainMem.useNamedFile = "FALSE"
```