- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
I have setup a new Windows 7 Ultimate and a new Guest Windows 7 Ultimate, both inclusive all updates and VMWare Tools installed.
When starting the Guest OS I see the following error message:
No 3D support is available from the host. The 3D features of the virtual machine will be disabled.
dxdiag on the host shows:
Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.151019-1254)
Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
System Model: System Product Name
BIOS: BIOS Date: 10/31/12 20:41:07 Ver: 36.02
Processor: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz (8 CPUs), ~3.4GHz
Memory: 24576MB RAM
Available OS Memory: 24544MB RAM
Page File: 3643MB used, 45441MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode
I have an NVidia GTX-275, DirectX 10 compliant. With latest drivers.
Card name: NVIDIA GeForce GTX 275 | |
Manufacturer: NVIDIA | |
Chip type: GeForce GTX 275 | |
DAC type: Integrated RAMDAC | |
Device Key: Enum\PCI\VEN_10DE&DEV_05E6&SUBSYS_82F21043&REV_A1 | |
Display Memory: 4068 MB |
Dedicated Memory: 869 MB
Shared Memory: 3199 MB | |
Current Mode: 1920 x 1200 (32 bit) (59Hz) | |
Monitor Name: SyncMaster 245T(Digital) | |
Monitor Model: SyncMaster | |
Monitor Id: SAM02F5 | |
Native Mode: 1920 x 1200(p) (59.950Hz) | |
Output Type: DVI | |
Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um |
Driver File Version: 9.18.0013.4192 (English)
Driver Version: 9.18.13.4192 | |
DDI Version: 10 | |
Driver Model: WDDM 1.1 |
Driver Attributes: Final Retail
Driver Date/Size: 10/13/2015 20:00:02, 17559432 bytes
WHQL Logo’d: Yes | |
WHQL Date Stamp: |
Device Identifier: {D7B71E3E-46A6-11CF-9363-FFA21CC2C435}
Vendor ID: 0x10DE | |
Device ID: 0x05E6 | |
SubSys ID: 0x82F21043 | |
Revision ID: 0x00A1 |
Driver Strong Name: oem31.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section002:9.18.13.4192:pci\ven_10de&dev_05e6
Rank Of Driver: 00E02001 | ||
Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C | ||
D3D9 Overlay: Supported | ||
DXVA-HD: Supported | ||
DDraw Status: Enabled | ||
D3D Status: Enabled | ||
AGP Status: Enabled |
Directory of C:\Windows\System32
05.12.2015 15:22 1,238,528 d3d10.dll
05.12.2015 15:22 296,960 d3d10core.dll
05.12.2015 15:22 648,192 d3d10level9.dll
30.07.2015 19:06 2,565,120 d3d10warp.dll
05.12.2015 15:22 194,560 d3d10_1.dll
05.12.2015 15:22 333,312 d3d10_1core.dll
05.12.2015 15:21 1,887,232 d3d11.dll
14.07.2009 02:40 12,288 d3d8thk.dll
21.11.2010 04:24 2,067,456 d3d9.dll
26.05.2010 11:41 511,328 d3dx10_43.dll
26.05.2010 11:41 276,832 d3dx11_43.dll
26.05.2010 11:41 2,401,112 D3DX9_43.dll
Directory of C:\Windows\SysWOW64
05.12.2015 15:22 1,080,832 d3d10.dll
05.12.2015 15:22 220,160 d3d10core.dll
05.12.2015 15:22 604,160 d3d10level9.dll
30.07.2015 18:57 1,987,584 d3d10warp.dll
05.12.2015 15:22 161,792 d3d10_1.dll
05.12.2015 15:22 249,856 d3d10_1core.dll
05.12.2015 15:21 1,505,280 d3d11.dll
14.07.2009 02:15 1,036,800 d3d8.dll
14.07.2009 02:15 11,264 d3d8thk.dll
21.11.2010 04:24 1,828,352 d3d9.dll
14.07.2009 02:15 386,048 d3dim.dll
14.07.2009 02:15 817,664 d3dim700.dll
14.07.2009 02:15 593,920 d3dramp.dll
26.05.2010 11:41 470,880 d3dx10_43.dll
26.05.2010 11:41 248,672 d3dx11_43.dll
26.05.2010 11:41 1,998,168 D3DX9_43.dll
14.07.2009 02:15 53,760 d3dxof.dll
I searched for tips, but didn’t found any.
What is a possible cause, that I don’t have 3D support in my Guest system?
Итак, я использую VMware Workstation 12 Player на хосте 16.04. И каждый гость, которого я запускаю, жалуется, что «с хоста нет поддержки 3d» и «Аппаратное ускорение графики недоступно» «Ускорение 3D-графики отключено в плеере. У меня 8-гигабайтный графический процессор AMD RX480 с драйверами amd
sudo lspci -knn | grep -A2 VGA
02:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:67df] (rev c7)
Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e347]
Kernel driver in use: amdgpu
glxinfo | grep direct direct rendering: Yes
$ vmplayer &
Gtk-Message: Failed to load module "atk-bridge": /usr/lib/x86_64-linux-gnu/libatspi.so.0: undefined symbol: g_type_class_adjust_private_offset
Gtk-Message: Failed to load module "unity-gtk-module": libunity-gtk-module.so: cannot open shared object file: No such file or directory
(vmware-modconfig:4752): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
...repeats x20 ...
vmware-modconfig:4752): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmware-modconfig:4752): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
Gtk-Message: Failed to load module "canberra-gtk-module": libcanberra-gtk-module.so: cannot open shared object file: No such file or directory
Gtk-Message: Failed to load module "atk-bridge": /usr/lib/x86_64-linux-gnu/libatspi.so.0: undefined symbol: g_type_class_adjust_private_offset
Gtk-Message: Failed to load module "unity-gtk-module": libunity-gtk-module.so: cannot open shared object file: No such file or directory
(vmplayer:4747): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(vmplayer:4747): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
Gtk-Message: Failed to load module "canberra-gtk-module": libcanberra-gtk-module.so: cannot open shared object file: No such file or directory
I/O warning : failed to load external entity "/etc/vmware/hostd/proxy.xml"
Immediately after I upgraded from VMware Fusion 10.x to 11.0.1, I got the following error when trying to start the VM of any «advanced» OS like Windows 10 and Ubuntu 16.04, which worked perfectly fine in VMware Fusion 10:
No 3D support is available from the host.
The 3D features of the virtual machine will be disabled.
After several hours of digging around and experimentation, I sorted out the answer which I’ll post below.
asked Nov 22, 2018 at 20:01
S. McCandlishS. McCandlish
3191 gold badge3 silver badges8 bronze badges
- Revert to VMware Fusion 10.x, and open that app. It may prompt you to allow something in System Preferences and such; do so.
- Start up every VM that is not in a fully shut-down state (anything you can «Resume»). Shut each down entirely.
- Upgrade again to VMware Fusion 11.
- For each VM in which you need 3D stuff, go into its Settings and pick the Compatibility tab, then Advanced Options drop-down, then select Use Hardware Version: 16.
- Then in the Display tab, turn on Accelerate 3D Graphics (if it’s not on already), and set the Shared Graphics Memory you need.
- Shut down VMware Fusion.
-
Edit your main VMware Fusion preferences file. This should be «
~/Library/Preferences/VMware Fusion/preferences
«. Add the following lines (or edit any that are present to make them conform), then save the file:mks.enableMTLRenderer = "0" mks.enableGLRenderer = "1" mks.gl.allowBlacklistedDrivers = "TRUE"
-
If you have a 2013 or later Mac, and a recent version of macOS, and are running the Metal 2 3D graphics library, you can try setting the first of those (the MTL one) to «1», and could try setting the one below it (GL) to «0», but I have not tested this personally.
- If it still doesn’t work, shut down the VM, and VMware Fusion, then go find your VM in the macOS filesystem, right-click or ctrl-click it, and pick «Show package contents». Open its
[whatever].vmx
file, and add themks.gl.allowBlacklistedDrivers = "TRUE"
line to that file as well. Save the file. - Under no circumstances should you fire up the VM entirely (i.e., past the point where you get a login screen and can pick the option to shut the VM down) until this «No 3D support» problem is fixed. That is apt to really booger something up.
- If you just cannot get it to work at all, set the VM’s Hardware Level back to 14, and its VRAM (Display > Shared Graphics Memory) back to no more than 2048 (the max in VMware 10), then downgrade the VMware app back to VMware Fusion 10.x. In that, see if there’s an option to go to Hardware Level 15; if not, leave it at 14. Your VMs should now work properly again. If not, undo the two changes made to the config files (
preferences
and*.vmx
). - If it did work in VMware Fusion 11, then after restarting your VM fully, re-install VMware Tools from within the VM. This will upgrade the video drivers, etc., to VMware Fusion 11 versions.
What seems to have happened was that either Hardware Version 14 did support DirectX and this support was removed, or there was a Version 15 that did and that entire version was removed. Either way, any VMs under VMware Fusion 10.x that supported DirectX, under the highest Hardware Version then available, suddenly lost that ability in VMware Fusion 11.x, until upgraded to Hardware Version 16. And on top of this, VMware silently assumed everyone was using Metal 2 and had abandoned OpenGL, which of course isn’t true.
On the up side, you now get up to 3GB shared VRAM instead of 2GB, so you’ll be able to play some less-ancient games and use slightly more modern 3D-rendering apps. However, VMware is still lagging badly on 3D support (DirectX 10 has been obsolete since 2008, so VMware’s a decade behind user needs – it’s still stuck at DirectX 10.1).
Credits:
- Charles Green and Amandeep Dhindsa in this Ubuntu VMware Workstation thread at Stack Exchange: https://askubuntu.com/questions/537787/enable-3d-hw-acceleration-on-vmware-workstation-10-on-ubuntu-14-04/1095171#1095171
- Mikero in this Macs and VMware Fusion thread at VMTN: https://communities.vmware.com/thread/597366
answered Nov 22, 2018 at 20:14
S. McCandlishS. McCandlish
3191 gold badge3 silver badges8 bronze badges
By experiment, I found out with Prefer External GPU checked on Catalina:
If you enable on Fusion 11.5 High Performance Graphic support on Windows 10 guest with above lines added to preferences, it will use Open GL framework from dGPU. If you, however, disable High Performance Graphic support for the guest entirely, it will use eGPU, probably via Metal. Open GL with subjectively similar performance to host, perhaps bogged down by number of vCores assigned.
I ran a few WebGL demos and I can see eGPU (Vega 64 FE) utilized to 30% before hitting limits on CPU allocation (2C in my case). Performance with eGPU is significantly better than performance with 5500M dGPU where I see GPU maxed out before CPU.
answered Dec 4, 2019 at 20:28
2
You must log in to answer this question.
Not the answer you’re looking for? Browse other questions tagged
.
Not the answer you’re looking for? Browse other questions tagged
.
Facts: VMware Player on Ubuntu 18.04 LTS with the
standard Gnome desktop running an AMD WX-2100 graphics card. Both glxinfo and glxgears show 3d acceleration is
enabled and working on the host. In addition to VMware Player, the host is also running the qemu-kvm/libvirtd stack from Ubuntu’s official repositories. My use case for 3d accelerated graphics in a Windows guest is to occasionally play a Windows-only game.
Issue: Player barks this warning during installation of… anything.
Solution: This
askubuntu post, Powered by StackExchange[TM], provides the solution:
-
Make sure 3d graphics is enabled in the guest settings and VMware Tools installed in it.
-
Shut down the Windows VM and exit Player.
-
Edit ~/.vmware/preferences to add…
mks.gl.allowBlacklistedDrivers = "TRUE"
- Start up the guest VM in Player.
NOTES:
-
Why not use qemu-kvm instead of VMware Player? Because there isn’t a working Windows driver for virtual 3d accelerated graphics. The virGL project had this as a goal around five years ago (back when I went all-in on qemu-kvm myself), but has yet to deliver for Windows guests.
-
Why not PCI (VFIO) pass-through? Too expensive for me, and I suspect for most ordinary users. If you need 3d graphics
on Windows, it’s probably justifiable. But then you could put the same money into a second workstation running Windows on bare metal. There’s still a frustratingly high learning curve for getting pass-through graphics up and running, and the premium hardware required is very expensive (high-end motherboard and two graphics cards, as well as a spare monitor or a pro KVM switch — like a Blackbox for reliability and durability). -
You can’t run a VMware and a qemu-kvm guest at the same time, each virtualization system wants exclusive access to the kernel. For desktop use that shouldn’t be a problem, but if the host doubles as a virtual lab (as mine does) you’re going to have to shut down all your qemu-kvm guests before launching a guest in Player. It’s an annoyance, but manageable for me. Note that you do not have to shut down or recycle libvirtd before or after using VMware Player.