Solved: Re: VMware workstation 17 player no 3D support fro... - Page 2

Darhagonable · ‎11-20-2022

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.

Sam2555 · ‎11-28-2022

https://wormhole.app/xNbPW#kloLPhm8YNqS_tHWWbd1OA

mjkrol · ‎11-28-2022

Thank you,

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

Sam2555 · ‎11-28-2022

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

mjkrol · ‎11-28-2022

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"

kutewenox · ‎11-29-2022

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 · ‎11-29-2022

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

AndrewatVmWCom · ‎12-01-2022

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

Sam2555 · ‎12-02-2022

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,

mjkrol · ‎12-02-2022

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

mjkrol · ‎12-02-2022

Sam,

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

Sam2555 · ‎12-06-2022

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

mjkrol · ‎12-06-2022

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?

banackm · ‎12-06-2022

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

AndrewatVmWCom · ‎12-07-2022

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.

Sam2555 · ‎12-10-2022

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

Sam2555 · ‎12-10-2022

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?

RoopsCumbria · ‎06-06-2023

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

ci4ic4 · ‎11-14-2023

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.

All

VMware workstation 17 player no 3D support from host