VMware workstation 17 player no 3D support from host

[Darhagonable]

Before when using version 16 3D acceleration was working no problem but after updating to version 17 it no longer works and gives me the following message:

My host is running Windows 10 22h2 and has a GTX 770 gpu.

I have tried the following but none helped:
mks.gl.allowUnsupportedDrivers="TRUE"
mks.gl.allowBlacklistedDrivers = "TRUE"
mks.requireISBRenderer = "FALSE"
mks.enableISBRenderer = "FALSE"

Anything I can do to fix it?

I have attached my DxDiag output.

Attachment(s)

DxDiag.txt   114 KB 1 version

[merlingecko]

same here, have here a NVIDIA Quadro K4100M; latest driver is installed (R418 U9 (426.78) WHQL, Release Date: 2020.6.24 ). this graphics card support directx 11 (minimum requirement); directx function levels: 11_0, 10_1, 10_0, 9_3, 9_2 and 9_1 (dxdiag); so whats wrong; can we have a official statement from vmware please?

[Michal Krol]

Please try this vmx option instead:

mks.enableDX12Renderer=FALSE

If possible, I would appreciate it if you attached "mksSandbox.log" for the VM session that reported no 3D support.

[merlingecko]

note: i have vmware workstation 17, not the player; the technology should be the same.

the vmx option mks.enableDX12Renderer=FALSE does not work; i have attached the mksSandbox.logs before and after the modification of the vmx.

Attachment(s)

mks.zip   9 KB 1 version

[Darhagonable]

mks.enableDX12Renderer=FALSE didn't help sadly.
Here is the mksSandbox.log

Attachment(s)

mksSandbox.log   13 KB 1 version

[Michal Krol]

Both Quadro K4100M and GTX 770 do not support feature level 11_1 (they are only feature level 11_0) that is the minimum level required by WS 17.

During installation, you should see a warning message saying that 3D will not be supported on such systems.

[merlingecko]

sorry, no; i had get no warning; offical documentation has no info for minimum dx level required; it says only directx 11; any cause, why feature level 11_1 is needed?

[Darhagonable]

I don't remember getting any such warning.
Any way to override it so one can run it using 11_0 at one own's risk? Or disable whatever feature that requires 11_1?
Newer versions of windows 11 doesn't work on vmware 16 so I sadly don't have the option to simply downgrade vmware.

[Michal Krol]

In order to support OpenGL 4.3 in the VMs we had to start requiring DirectX feature level 11.1 on the host. I'm sorry but there is no vmx config option to override that requirement.

[Darhagonable]

This can be fixed by changing the renderer with the following in the vmx:
mks.enableDX11Renderer = "FALSE"
mks.enableGLRenderer = "TRUE"

[Sam2555]

My CPU is Intel Core i5-4690, using integrated video card "Intel(R) HD Graphics 4600", which is supports OpenGL 4.3 and DirectX feature level 11.1, but it also have this problem. Tested in a Windows Server 2022 x64 vm, and VMWare Tools have been installed. Whatever set mks.enableDX11Renderer = "FALSE" and mks.enableGLRenderer = "TRUE" or not seems haven't affect, always show "no 3D support". By the way, ISBRendererComm: Lost connection to mksSandbox (3093) SOMETIMES happened, A vm maybe works well a moment ago, but it may show ISBRendererComm: Lost connection to mksSandbox (3093) after shutdown and boot again.

[Michal Krol]

Sam2555,

I would appreciate it if you attached vmware*.log and mksSandbox*.log files from a problematic session.

As a workaround, if GLRenderer worked for you, these are the vmx config options to enable GLRenderer in WS 17:

mks.enableDX12Renderer=FALSE

mks.enableDX11Renderer=FALSE

mks.enableGLRenderer=TRUE

[Sam2555]

I also record screen after setting workaround. Here's something wrong. https://wormhole.app/N6oBO#tXc5SfE9_EX3GV8tD_O02w

Attachment(s)

mksSandbox.log   89 KB 1 version

mksSandbox-2.log   108 KB 1 version

vmware.log   238 KB 1 version

vmware-0.log   276 KB 1 version

mksSandbox-1.log   89 KB 1 version

vmware-1.log   237 KB 1 version

mksSandbox-0.log   89 KB 1 version

[Michal Krol]

Can you try using DX11Renderer? These are the vmx config options:

mks.enableDX12Renderer=FALSE

mks.enableDX11Renderer=TRUE

[Sam2555]

When I set mks.enableDX12Renderer=TRUE mks.enableDX11Renderer=FALSE Everything is OK, but it said no 3D support. When I set mks.enableDX12Renderer=FALSE mks.enableDX11Renderer=TRUE Everything is OK, but it also said no 3D support.

[Michal Krol]

Can you double check that and send me the *.log files as you are getting different beahviour from your original post?

I have an i5-4310M with the same HD 4600 and with the below configuration the VM will not start:

mks.enableDX12Renderer=TRUE

mks.enableDX11Renderer=FALSE

But with the below configuration everything works:

mks.enableDX12Renderer=FALSE

mks.enableDX11Renderer=TRUE

[Sam2555]

https://wormhole.app/5W9oR#_A78KBwRI17UFErrb9CdIQ

I do 3 tests in a Windows Server 2022 VM:

vmware.log

mks.enableDX12Renderer=FALSE
mks.enableDX11Renderer=TRUE

vmware-0.log

mks.enableDX12Renderer=TRUE
mks.enableDX11Renderer=FALSE

vmware-1.log

Doesn't modify anything.

[Sam2555]

3 tests are all well except it said "No 3D support is available from the host".

[Michal Krol]

Sam2555,

Can you reupload the files as they are appear to be already gone?

[Sam2555]

https://wormhole.app/xNbPW#kloLPhm8YNqS_tHWWbd1OA

[Michal Krol]

Thank you,

Can you please also attach the mksSandbox*.log files that are created along vmware*.log files?

[Sam2555]

Sorry, but here're no mksSandbox*.log in this VM's folder, strange,

[Michal Krol]

Sam2555,

It looks like your vMotion configuration has 3D disabled. Can you backup your .vmx file and remove or comment out all lines containing "vmotion.svga."? There should be 21 options to remove in total in your case. This is the most important, but try removing them all if you still don't get 3D:

vmotion.svga.supports3D = "0"

[Sam2555]

It seems doesn't work, these items seems recovery when VM boot.

[Michal Krol]

Sam,

Can you upload the new vmware*.log and mksSandbox*.log files after removing the vMotion config options?

[Sam2555]

https://wormhole.app/KMWmJ#TwTJ-QjaGNUxXJkMWdzN5w I don't know why mksSandbox*.log doesn't exist.

[Michal Krol]

Sam,

As I already mentioned in an earlier post, your system has an HD 4600 GPU and must have the following vmx config options:

mks.enableDX12Renderer=FALSE

mks.enableDX11Renderer=TRUE

Can you please apply these options to affected VMs, reboot your host OS and try again?

[Sam2555]

Thank you very much, it works. And I found low avaliable memory will causing "no 3D support from host".happens.

[Michael Banack]

Sam2555,

The logs show that your host doesn't have enough memory to start up our 3D graphics stack.

How much memory does your host have, and how big are all of the VMs you're trying to run at once?

You can try to set the following config option to reduce our 3d memory usage, but the performance/stability might suffer:

mks.sandbox.dataChannelSizeMB = 1024

[Sam2555]

Thank you very much, it works. I wonder what's the difference between VM -> Settings -> Hardware -> Display -> Graphics memory, and "mks.sandbox.dataChannelSizeMB" config in .vmx file? And, if possible, could VMWare add some options in GUI to set mks.sandbox.dataChannelSizeMB size and DX version, and provide more information when vm launch failure, such as graphic card only support lower DX version:X ; mks sandbox doesn't have enough free memory?

[merlingecko]

Thanks to for your hint (will test it); have someone tested vulkan or in other words is vulkan supported and faster than opengl?

 

[AndrewatVmWCom]

machine msi ge60 2pe apache pro, 16GB Ram, 256 SSD (RAID0) + 1TB HDD runing windows 8.1 64bit

After updating to workstation 16 pro all vm started displaying the message at startup "no 3D support from host"

All vm's, that is windows versions (7 and 10) as well as several linux distros (mint, ubuntu, suse)

Applying the suggested change solved the problem for the windows vms'

Any solution for the linux distros?

Many thanks for the (windows) solution

AndrewatVmCom

[Michal Krol]

Andrewat,

Your system has a GTX 860M which is no longer supported both by DX12 and DX11 Renderer. As other pointed out, try disabling these renderers and enabling GL Renderer:

mks.enableDX11Renderer = FALSE

mks.enableDX12Renderer = FALSE

mks.enableGLRenderer = TRUE

[AndrewatVmWCom]

Thank you mjkrol

for your suggestion.

1. it seems that the settings I wrote about did not solve the problem for windows or linux.

2. I have also used your suggested parameters

mks.enableDX11Renderer = FALSE

mks.enableDX12Renderer = FALSE

mks.enableGLRenderer = TRUE

to no avail.

 

But thank you anyway for your input.

 

 

[RoopsCumbria]

In case it helps anyone else on older hardware:-

I have also had the same/similar error in VMWare 16 on Windows 8.1 for ages and eventually decided to silence it by turning off 3d support entirely (as far as I can see).

 

After hacking about trying various options I ended up with this in the .vmx for Linux Mint:-

 

mks.enableDX12Renderer = "FALSE"
mks.enableDX11Renderer = "FALSE"
mks.enableGLRenderer = "TRUE"
mks.enable3d = "FALSE"

 

I'm assuming that the line mks.enable3d = "FALSE" is the operative one in this case   Not subtle, but the irritating message is gone and 3D accel isn't really needed for my usage.

 

Roops

[kutewenox]

Hey guys,

I'm assuming it's an error, but after a lot of trying I found the solution:

Add "mks.dx12.vendorID = "0x10de"" to .vmx file and the vm also can use with accelerate 3d graphics. (The vondorID describes the (i)gpuID and shown in the device manager.)

Please try. 

 

 

[Sam2555]

I try mks.dx12.vendorID = "0x8086" in a Windows Server 2022 VM, it seems works for me, but it doesn't work after a time,

[ci4ic4]

Hi,

I don't want to hijack the thread, but as the title is the same as I wanted to use, I am posting here - even if my case relates to VMWare Workstation 17.5 running on Linux Mint 21.2 running the latest Liquorix kernel, whereas this topic seems to deal mainly with execution under Windows. The hardware it is running on is a ThinkPAD P16s Gen1 with AMD Ryzen 7 PRO 6850U with Radeon Graphics (family: 0x19, model: 0x44, stepping: 0x1), native 3D acceleration works perfectly under Linux (actually faster than under Windows 11). l

I got the same message running the latest Ubuntu under 17.5; I don't remember getting it when I first installed 17.02 on the same machine (but hey, 17.5 is much better than 17.02 on both platforms, so no one is complaining). Examining the mkSandbox.log file, I saw:

2023-11-13T22:38:28.581Z In(05) mks  Vulkan Renderer: VKRDevice_Create trying DISPLAY=:0
2023-11-13T22:38:28.629Z In(05) mks  Vulkan Renderer: Only the AMDVLK driver is supported at this time.
2023-11-13T22:38:28.629Z In(05) mks  Vulkan Renderer: Only the AMDVLK driver is supported at this time.
2023-11-13T22:38:28.629Z In(05) mks  Vulkan Renderer: Available Vulkan devices:
2023-11-13T22:38:28.629Z In(05) mks  Vulkan Renderer: Vulkan Device 0:
2023-11-13T22:38:28.629Z In(05) mks  Vulkan Renderer:   Vendor= 'AMD'
2023-11-13T22:38:28.629Z In(05) mks  Vulkan Renderer:   ID= 0x1681
2023-11-13T22:38:28.629Z In(05) mks  Vulkan Renderer:   Type= 0x1
2023-11-13T22:38:28.629Z In(05) mks  Vulkan Renderer:   Name= 'AMD Unknown (RADV REMBRANDT)'
2023-11-13T22:38:28.629Z In(05) mks  Vulkan Renderer:   GPU chip= Unknown (RDNA?)
2023-11-13T22:38:28.629Z In(05) mks  Vulkan Renderer:   GPU type= Integrated
2023-11-13T22:38:28.629Z In(05) mks  Vulkan Renderer:   Driver Name= 'radv'
2023-11-13T22:38:28.629Z In(05) mks  Vulkan Renderer:   Driver Version= 0x5c00004
2023-11-13T22:38:28.629Z In(05) mks  Vulkan Renderer:   Driver Info= 'Mesa 23.0.4-0ubuntu1~22.04.1'
2023-11-13T22:38:28.629Z In(05) mks  Vulkan Renderer:   API Version= 1.3.238
2023-11-13T22:38:28.629Z In(05) mks  Vulkan Renderer: Only the AMDVLK driver is supported at this time.
2023-11-13T22:38:28.629Z In(05) mks  Vulkan Renderer:   Device supported= no
2023-11-13T22:38:28.629Z In(05) mks  Vulkan Renderer:   Presentation support= true
2023-11-13T22:38:28.629Z In(05) mks  Vulkan Renderer: Vulkan Device 1:
2023-11-13T22:38:28.629Z In(05) mks  Vulkan Renderer:   Vendor= 'Mesa'
2023-11-13T22:38:28.629Z In(05) mks  Vulkan Renderer:   ID= 0x0
2023-11-13T22:38:28.629Z In(05) mks  Vulkan Renderer:   Type= 0x4
2023-11-13T22:38:28.629Z In(05) mks  Vulkan Renderer:   Name= 'llvmpipe (LLVM 15.0.7, 256 bits)'
2023-11-13T22:38:28.629Z In(05) mks  Vulkan Renderer:   GPU chip= Unknown (Unknown)
2023-11-13T22:38:28.629Z In(05) mks  Vulkan Renderer:   GPU type= CPU
2023-11-13T22:38:28.629Z In(05) mks  Vulkan Renderer:   Driver Name= 'llvmpipe'
2023-11-13T22:38:28.629Z In(05) mks  Vulkan Renderer:   Driver Version= 0x1
2023-11-13T22:38:28.629Z In(05) mks  Vulkan Renderer:   Driver Info= 'Mesa 23.0.4-0ubuntu1~22.04.1 (LLVM 15.0.7)'
2023-11-13T22:38:28.629Z In(05) mks  Vulkan Renderer:   API Version= 1.3.238
2023-11-13T22:38:28.629Z In(05) mks  Vulkan Renderer:   Device supported= no
2023-11-13T22:38:28.629Z In(05) mks  Vulkan Renderer:   Presentation support= true
2023-11-13T22:38:28.629Z Wa(03) mks  Vulkan Renderer: No supported Vulkan device/driver found (See mks.vk.allowUnsupportedDevices or mks.vk.forceDevice configuration options).
2023-11-13T22:38:28.630Z In(05) mks  Vulkan Renderer: Max GPU memory used: 0
2023-11-13T22:38:28.630Z In(05) mks  Vulkan Renderer: GPU memory in use at exit: 0
2023-11-13T22:38:28.630Z In(05) mks  Vulkan Renderer: Max GPU allocations: 0
2023-11-13T22:38:28.630Z In(05) mks  Vulkan Renderer: GPU allocations at exit: 0

which made me search for AMDVLK driver under Mint. I followed https://github.com/GPUOpen-Drivers/AMDVLK - roughly, as some steps, e.g. the generation of the 32-bit elements, didn't work at all - and was able eventually to configure the system to use this driver. The build took quite a lot of time, as was expected, even on this reasonably fast 8c/16t CPU. Now the Ubuntu guest runs with 3D acceleration and the corresponding bits from mkSandbox.log file read:

2023-11-14T09:04:29.394Z In(05) mks  Vulkan Renderer: VKRDevice_Create trying DISPLAY=:0
2023-11-14T09:04:29.447Z In(05) mks  Vulkan Renderer: Available Vulkan devices:
2023-11-14T09:04:29.447Z In(05) mks  Vulkan Renderer: Vulkan Device 0:
2023-11-14T09:04:29.447Z In(05) mks  Vulkan Renderer:   Vendor: 'AMD'
2023-11-14T09:04:29.447Z In(05) mks  Vulkan Renderer:   ID: 0x1681
2023-11-14T09:04:29.447Z In(05) mks  Vulkan Renderer:   Type: 0x1
2023-11-14T09:04:29.447Z In(05) mks  Vulkan Renderer:   Name: 'Unknown AMD GPU'
2023-11-14T09:04:29.447Z In(05) mks  Vulkan Renderer:   GPU chip: Unknown (RDNA?)
2023-11-14T09:04:29.447Z In(05) mks  Vulkan Renderer:   GPU type: Integrated
2023-11-14T09:04:29.447Z In(05) mks  Vulkan Renderer:   Driver Name: 'AMD open-source driver'
2023-11-14T09:04:29.447Z In(05) mks  Vulkan Renderer:   Driver Version: 0x800120
2023-11-14T09:04:29.447Z In(05) mks  Vulkan Renderer:   Driver Info: '2023.Q4.1 (LLPC)'
2023-11-14T09:04:29.447Z In(05) mks  Vulkan Renderer:   API Version: 1.3.267
2023-11-14T09:04:29.447Z In(05) mks  Vulkan Renderer:   Device supported: yes
2023-11-14T09:04:29.447Z In(05) mks  Vulkan Renderer:   Presentation support: true
2023-11-14T09:04:29.447Z In(05) mks  Vulkan Renderer: Using device 0 of 1
2023-11-14T09:04:29.454Z In(05) mks  XConnection: Closing console display
2023-11-14T09:04:29.454Z In(05) mks  Vulkan Renderer: VKRDevice_Create: Succeeded with DISPLAY=(null)
2023-11-14T09:04:29.454Z In(05) mks  Vulkan Renderer: Physical Device Limits:
2023-11-14T09:04:29.454Z In(05) mks  Vulkan Renderer:   maxImageDimension2D=16384

and 3D is accelerated in the Ubuntu guest. Measuring using https://cad.onshape.com/check the performance is a little more than half of that on real hardware, so it is definitely a win.

 

Just a bit of experience to share, in case one wants to have an accelerated guest in similar circumstances. The Mint instance in question was earlier configured for development, so I had already llvm 17.05 etc. installed.