Enable 3D HW acceleration on VMWare Workstation 10 on Ubuntu 14.04











up vote
41
down vote

favorite
22












I am trying to enable hardware accelerated 3D graphics in a Win 8.1 VM in VMware Workstation 10.0.3 on Ubuntu 14.04.1 LTS (Trusty Tahr) to play the game Smite smoothly. I have checked that the HW acceleration works in Ubuntu:



$ /usr/lib/nux/unity_support_test -p
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile
OpenGL version string: 3.0 Mesa 10.2.2

Not software rendered: yes
Not blacklisted: yes
GLX fbconfig: yes
GLX texture from pixmap: yes
GL npot or rect textures: yes
GL vertex program: yes
GL fragment program: yes
GL vertex buffer object: yes
GL framebuffer object: yes
GL version is 1.4+: yes

Unity 3D supported: yes


In VMware Workstation, on the VM under "Virtual Machine Settings" -> "Display" -> "Accelerate 3D Graphics" is checked.



Screenshot



But while booting the VM, it says "No 3D support is available from the host".



Screenshot



How comes VMware does not detect HW 3D acceleration? How can I fix this?



Thanks!










share|improve this question
























  • You will need to enable 3D support in VMware: vmware.com/support/ws55/doc/ws_vidsound_d3d_enabling_vm.html
    – MadMike
    Oct 16 '14 at 16:56










  • @madmike, I think I did this correctly -- see the first screenshot. But thanks for the in-depth link!
    – Siemen
    Oct 17 '14 at 8:19

















up vote
41
down vote

favorite
22












I am trying to enable hardware accelerated 3D graphics in a Win 8.1 VM in VMware Workstation 10.0.3 on Ubuntu 14.04.1 LTS (Trusty Tahr) to play the game Smite smoothly. I have checked that the HW acceleration works in Ubuntu:



$ /usr/lib/nux/unity_support_test -p
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile
OpenGL version string: 3.0 Mesa 10.2.2

Not software rendered: yes
Not blacklisted: yes
GLX fbconfig: yes
GLX texture from pixmap: yes
GL npot or rect textures: yes
GL vertex program: yes
GL fragment program: yes
GL vertex buffer object: yes
GL framebuffer object: yes
GL version is 1.4+: yes

Unity 3D supported: yes


In VMware Workstation, on the VM under "Virtual Machine Settings" -> "Display" -> "Accelerate 3D Graphics" is checked.



Screenshot



But while booting the VM, it says "No 3D support is available from the host".



Screenshot



How comes VMware does not detect HW 3D acceleration? How can I fix this?



Thanks!










share|improve this question
























  • You will need to enable 3D support in VMware: vmware.com/support/ws55/doc/ws_vidsound_d3d_enabling_vm.html
    – MadMike
    Oct 16 '14 at 16:56










  • @madmike, I think I did this correctly -- see the first screenshot. But thanks for the in-depth link!
    – Siemen
    Oct 17 '14 at 8:19















up vote
41
down vote

favorite
22









up vote
41
down vote

favorite
22






22





I am trying to enable hardware accelerated 3D graphics in a Win 8.1 VM in VMware Workstation 10.0.3 on Ubuntu 14.04.1 LTS (Trusty Tahr) to play the game Smite smoothly. I have checked that the HW acceleration works in Ubuntu:



$ /usr/lib/nux/unity_support_test -p
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile
OpenGL version string: 3.0 Mesa 10.2.2

Not software rendered: yes
Not blacklisted: yes
GLX fbconfig: yes
GLX texture from pixmap: yes
GL npot or rect textures: yes
GL vertex program: yes
GL fragment program: yes
GL vertex buffer object: yes
GL framebuffer object: yes
GL version is 1.4+: yes

Unity 3D supported: yes


In VMware Workstation, on the VM under "Virtual Machine Settings" -> "Display" -> "Accelerate 3D Graphics" is checked.



Screenshot



But while booting the VM, it says "No 3D support is available from the host".



Screenshot



How comes VMware does not detect HW 3D acceleration? How can I fix this?



Thanks!










share|improve this question















I am trying to enable hardware accelerated 3D graphics in a Win 8.1 VM in VMware Workstation 10.0.3 on Ubuntu 14.04.1 LTS (Trusty Tahr) to play the game Smite smoothly. I have checked that the HW acceleration works in Ubuntu:



$ /usr/lib/nux/unity_support_test -p
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile
OpenGL version string: 3.0 Mesa 10.2.2

Not software rendered: yes
Not blacklisted: yes
GLX fbconfig: yes
GLX texture from pixmap: yes
GL npot or rect textures: yes
GL vertex program: yes
GL fragment program: yes
GL vertex buffer object: yes
GL framebuffer object: yes
GL version is 1.4+: yes

Unity 3D supported: yes


In VMware Workstation, on the VM under "Virtual Machine Settings" -> "Display" -> "Accelerate 3D Graphics" is checked.



Screenshot



But while booting the VM, it says "No 3D support is available from the host".



Screenshot



How comes VMware does not detect HW 3D acceleration? How can I fix this?



Thanks!







14.04 vmware 3d hardware-acceleration vmware-workstation






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Oct 17 '14 at 8:24









MadMike

3,77172244




3,77172244










asked Oct 16 '14 at 13:13









Siemen

308134




308134












  • You will need to enable 3D support in VMware: vmware.com/support/ws55/doc/ws_vidsound_d3d_enabling_vm.html
    – MadMike
    Oct 16 '14 at 16:56










  • @madmike, I think I did this correctly -- see the first screenshot. But thanks for the in-depth link!
    – Siemen
    Oct 17 '14 at 8:19




















  • You will need to enable 3D support in VMware: vmware.com/support/ws55/doc/ws_vidsound_d3d_enabling_vm.html
    – MadMike
    Oct 16 '14 at 16:56










  • @madmike, I think I did this correctly -- see the first screenshot. But thanks for the in-depth link!
    – Siemen
    Oct 17 '14 at 8:19


















You will need to enable 3D support in VMware: vmware.com/support/ws55/doc/ws_vidsound_d3d_enabling_vm.html
– MadMike
Oct 16 '14 at 16:56




You will need to enable 3D support in VMware: vmware.com/support/ws55/doc/ws_vidsound_d3d_enabling_vm.html
– MadMike
Oct 16 '14 at 16:56












@madmike, I think I did this correctly -- see the first screenshot. But thanks for the in-depth link!
– Siemen
Oct 17 '14 at 8:19






@madmike, I think I did this correctly -- see the first screenshot. But thanks for the in-depth link!
– Siemen
Oct 17 '14 at 8:19












3 Answers
3






active

oldest

votes

















up vote
69
down vote



accepted










Edit the file ~/.vmware/preferences and look for a line that starts with mks.gl.allowBlacklistedDrivers, if it is not present - you can add it into the file.



This should be changed to mks.gl.allowBlacklistedDrivers = "TRUE"
(note the double quotes around TRUE)






share|improve this answer



















  • 4




    Just wanted to note that this also works in Workstation 11. By default, the mks.gl.allowBlacklistedDrivers parameter is not present in the preferences file, but adding it does work. Thanks.
    – user394700
    Apr 3 '15 at 22:15








  • 3




    Work in VMware Workstation 12.
    – Guicara
    Nov 30 '15 at 22:30






  • 2




    Same is needed for the free vmware-player
    – Treviño
    Apr 19 '16 at 18:24






  • 2




    Works in VMware Workstation 14.1
    – shadowbq
    Feb 7 at 15:34






  • 1




    Worked for VMware Player 14.1.1 on Fedora 27
    – Chang Qian
    Mar 18 at 6:48


















up vote
12
down vote













Add mks.gl.allowBlacklistedDrivers = "TRUE" in the .vmx file.



It has worked for Linux Mint Cinnamon as host with kernel 3.16 and Debian 8.2 Cinnamon as guest.






share|improve this answer























  • +1 for likely relevant answer. While this forum post in 2013 seems to agree, this Ask Ubuntu post indicates it is not always the case. This depends on video driver support too.
    – clearkimura
    Dec 4 '15 at 4:09










  • I didn't have a Preferences file so I modified the VMX on Workstation 12. Worked like a charm.
    – Drewdin
    May 5 '16 at 2:00










  • Note for those migrating XP guests from VirtualBox to VMWare Workstation 12 Player Linux 64-bit following a Sysprep process - adding this option to my .vmx file fixed an issue where the mouse pointer was stuck in a single place on the screen and couldn't move. After adding this line the mouse was working again.
    – Pabru
    Jun 4 '16 at 0:22


















up vote
1
down vote













For me, I had to add mks.gl.allowBlacklistedDrivers = "TRUE"to my virtual machine (.vmx) file






share|improve this answer





















  • why did you have to do so?
    – Pierre.Vriens
    Dec 1 '17 at 19:49











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














 

draft saved


draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f537787%2fenable-3d-hw-acceleration-on-vmware-workstation-10-on-ubuntu-14-04%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























3 Answers
3






active

oldest

votes








3 Answers
3






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
69
down vote



accepted










Edit the file ~/.vmware/preferences and look for a line that starts with mks.gl.allowBlacklistedDrivers, if it is not present - you can add it into the file.



This should be changed to mks.gl.allowBlacklistedDrivers = "TRUE"
(note the double quotes around TRUE)






share|improve this answer



















  • 4




    Just wanted to note that this also works in Workstation 11. By default, the mks.gl.allowBlacklistedDrivers parameter is not present in the preferences file, but adding it does work. Thanks.
    – user394700
    Apr 3 '15 at 22:15








  • 3




    Work in VMware Workstation 12.
    – Guicara
    Nov 30 '15 at 22:30






  • 2




    Same is needed for the free vmware-player
    – Treviño
    Apr 19 '16 at 18:24






  • 2




    Works in VMware Workstation 14.1
    – shadowbq
    Feb 7 at 15:34






  • 1




    Worked for VMware Player 14.1.1 on Fedora 27
    – Chang Qian
    Mar 18 at 6:48















up vote
69
down vote



accepted










Edit the file ~/.vmware/preferences and look for a line that starts with mks.gl.allowBlacklistedDrivers, if it is not present - you can add it into the file.



This should be changed to mks.gl.allowBlacklistedDrivers = "TRUE"
(note the double quotes around TRUE)






share|improve this answer



















  • 4




    Just wanted to note that this also works in Workstation 11. By default, the mks.gl.allowBlacklistedDrivers parameter is not present in the preferences file, but adding it does work. Thanks.
    – user394700
    Apr 3 '15 at 22:15








  • 3




    Work in VMware Workstation 12.
    – Guicara
    Nov 30 '15 at 22:30






  • 2




    Same is needed for the free vmware-player
    – Treviño
    Apr 19 '16 at 18:24






  • 2




    Works in VMware Workstation 14.1
    – shadowbq
    Feb 7 at 15:34






  • 1




    Worked for VMware Player 14.1.1 on Fedora 27
    – Chang Qian
    Mar 18 at 6:48













up vote
69
down vote



accepted







up vote
69
down vote



accepted






Edit the file ~/.vmware/preferences and look for a line that starts with mks.gl.allowBlacklistedDrivers, if it is not present - you can add it into the file.



This should be changed to mks.gl.allowBlacklistedDrivers = "TRUE"
(note the double quotes around TRUE)






share|improve this answer














Edit the file ~/.vmware/preferences and look for a line that starts with mks.gl.allowBlacklistedDrivers, if it is not present - you can add it into the file.



This should be changed to mks.gl.allowBlacklistedDrivers = "TRUE"
(note the double quotes around TRUE)







share|improve this answer














share|improve this answer



share|improve this answer








edited Nov 30 '15 at 9:14









Community

1




1










answered Oct 16 '14 at 15:47









Charles Green

12.9k73556




12.9k73556








  • 4




    Just wanted to note that this also works in Workstation 11. By default, the mks.gl.allowBlacklistedDrivers parameter is not present in the preferences file, but adding it does work. Thanks.
    – user394700
    Apr 3 '15 at 22:15








  • 3




    Work in VMware Workstation 12.
    – Guicara
    Nov 30 '15 at 22:30






  • 2




    Same is needed for the free vmware-player
    – Treviño
    Apr 19 '16 at 18:24






  • 2




    Works in VMware Workstation 14.1
    – shadowbq
    Feb 7 at 15:34






  • 1




    Worked for VMware Player 14.1.1 on Fedora 27
    – Chang Qian
    Mar 18 at 6:48














  • 4




    Just wanted to note that this also works in Workstation 11. By default, the mks.gl.allowBlacklistedDrivers parameter is not present in the preferences file, but adding it does work. Thanks.
    – user394700
    Apr 3 '15 at 22:15








  • 3




    Work in VMware Workstation 12.
    – Guicara
    Nov 30 '15 at 22:30






  • 2




    Same is needed for the free vmware-player
    – Treviño
    Apr 19 '16 at 18:24






  • 2




    Works in VMware Workstation 14.1
    – shadowbq
    Feb 7 at 15:34






  • 1




    Worked for VMware Player 14.1.1 on Fedora 27
    – Chang Qian
    Mar 18 at 6:48








4




4




Just wanted to note that this also works in Workstation 11. By default, the mks.gl.allowBlacklistedDrivers parameter is not present in the preferences file, but adding it does work. Thanks.
– user394700
Apr 3 '15 at 22:15






Just wanted to note that this also works in Workstation 11. By default, the mks.gl.allowBlacklistedDrivers parameter is not present in the preferences file, but adding it does work. Thanks.
– user394700
Apr 3 '15 at 22:15






3




3




Work in VMware Workstation 12.
– Guicara
Nov 30 '15 at 22:30




Work in VMware Workstation 12.
– Guicara
Nov 30 '15 at 22:30




2




2




Same is needed for the free vmware-player
– Treviño
Apr 19 '16 at 18:24




Same is needed for the free vmware-player
– Treviño
Apr 19 '16 at 18:24




2




2




Works in VMware Workstation 14.1
– shadowbq
Feb 7 at 15:34




Works in VMware Workstation 14.1
– shadowbq
Feb 7 at 15:34




1




1




Worked for VMware Player 14.1.1 on Fedora 27
– Chang Qian
Mar 18 at 6:48




Worked for VMware Player 14.1.1 on Fedora 27
– Chang Qian
Mar 18 at 6:48












up vote
12
down vote













Add mks.gl.allowBlacklistedDrivers = "TRUE" in the .vmx file.



It has worked for Linux Mint Cinnamon as host with kernel 3.16 and Debian 8.2 Cinnamon as guest.






share|improve this answer























  • +1 for likely relevant answer. While this forum post in 2013 seems to agree, this Ask Ubuntu post indicates it is not always the case. This depends on video driver support too.
    – clearkimura
    Dec 4 '15 at 4:09










  • I didn't have a Preferences file so I modified the VMX on Workstation 12. Worked like a charm.
    – Drewdin
    May 5 '16 at 2:00










  • Note for those migrating XP guests from VirtualBox to VMWare Workstation 12 Player Linux 64-bit following a Sysprep process - adding this option to my .vmx file fixed an issue where the mouse pointer was stuck in a single place on the screen and couldn't move. After adding this line the mouse was working again.
    – Pabru
    Jun 4 '16 at 0:22















up vote
12
down vote













Add mks.gl.allowBlacklistedDrivers = "TRUE" in the .vmx file.



It has worked for Linux Mint Cinnamon as host with kernel 3.16 and Debian 8.2 Cinnamon as guest.






share|improve this answer























  • +1 for likely relevant answer. While this forum post in 2013 seems to agree, this Ask Ubuntu post indicates it is not always the case. This depends on video driver support too.
    – clearkimura
    Dec 4 '15 at 4:09










  • I didn't have a Preferences file so I modified the VMX on Workstation 12. Worked like a charm.
    – Drewdin
    May 5 '16 at 2:00










  • Note for those migrating XP guests from VirtualBox to VMWare Workstation 12 Player Linux 64-bit following a Sysprep process - adding this option to my .vmx file fixed an issue where the mouse pointer was stuck in a single place on the screen and couldn't move. After adding this line the mouse was working again.
    – Pabru
    Jun 4 '16 at 0:22













up vote
12
down vote










up vote
12
down vote









Add mks.gl.allowBlacklistedDrivers = "TRUE" in the .vmx file.



It has worked for Linux Mint Cinnamon as host with kernel 3.16 and Debian 8.2 Cinnamon as guest.






share|improve this answer














Add mks.gl.allowBlacklistedDrivers = "TRUE" in the .vmx file.



It has worked for Linux Mint Cinnamon as host with kernel 3.16 and Debian 8.2 Cinnamon as guest.







share|improve this answer














share|improve this answer



share|improve this answer








edited Dec 4 '15 at 8:16









clearkimura

3,71711852




3,71711852










answered Dec 3 '15 at 21:45









Amandeep Dhindsa

12112




12112












  • +1 for likely relevant answer. While this forum post in 2013 seems to agree, this Ask Ubuntu post indicates it is not always the case. This depends on video driver support too.
    – clearkimura
    Dec 4 '15 at 4:09










  • I didn't have a Preferences file so I modified the VMX on Workstation 12. Worked like a charm.
    – Drewdin
    May 5 '16 at 2:00










  • Note for those migrating XP guests from VirtualBox to VMWare Workstation 12 Player Linux 64-bit following a Sysprep process - adding this option to my .vmx file fixed an issue where the mouse pointer was stuck in a single place on the screen and couldn't move. After adding this line the mouse was working again.
    – Pabru
    Jun 4 '16 at 0:22


















  • +1 for likely relevant answer. While this forum post in 2013 seems to agree, this Ask Ubuntu post indicates it is not always the case. This depends on video driver support too.
    – clearkimura
    Dec 4 '15 at 4:09










  • I didn't have a Preferences file so I modified the VMX on Workstation 12. Worked like a charm.
    – Drewdin
    May 5 '16 at 2:00










  • Note for those migrating XP guests from VirtualBox to VMWare Workstation 12 Player Linux 64-bit following a Sysprep process - adding this option to my .vmx file fixed an issue where the mouse pointer was stuck in a single place on the screen and couldn't move. After adding this line the mouse was working again.
    – Pabru
    Jun 4 '16 at 0:22
















+1 for likely relevant answer. While this forum post in 2013 seems to agree, this Ask Ubuntu post indicates it is not always the case. This depends on video driver support too.
– clearkimura
Dec 4 '15 at 4:09




+1 for likely relevant answer. While this forum post in 2013 seems to agree, this Ask Ubuntu post indicates it is not always the case. This depends on video driver support too.
– clearkimura
Dec 4 '15 at 4:09












I didn't have a Preferences file so I modified the VMX on Workstation 12. Worked like a charm.
– Drewdin
May 5 '16 at 2:00




I didn't have a Preferences file so I modified the VMX on Workstation 12. Worked like a charm.
– Drewdin
May 5 '16 at 2:00












Note for those migrating XP guests from VirtualBox to VMWare Workstation 12 Player Linux 64-bit following a Sysprep process - adding this option to my .vmx file fixed an issue where the mouse pointer was stuck in a single place on the screen and couldn't move. After adding this line the mouse was working again.
– Pabru
Jun 4 '16 at 0:22




Note for those migrating XP guests from VirtualBox to VMWare Workstation 12 Player Linux 64-bit following a Sysprep process - adding this option to my .vmx file fixed an issue where the mouse pointer was stuck in a single place on the screen and couldn't move. After adding this line the mouse was working again.
– Pabru
Jun 4 '16 at 0:22










up vote
1
down vote













For me, I had to add mks.gl.allowBlacklistedDrivers = "TRUE"to my virtual machine (.vmx) file






share|improve this answer





















  • why did you have to do so?
    – Pierre.Vriens
    Dec 1 '17 at 19:49















up vote
1
down vote













For me, I had to add mks.gl.allowBlacklistedDrivers = "TRUE"to my virtual machine (.vmx) file






share|improve this answer





















  • why did you have to do so?
    – Pierre.Vriens
    Dec 1 '17 at 19:49













up vote
1
down vote










up vote
1
down vote









For me, I had to add mks.gl.allowBlacklistedDrivers = "TRUE"to my virtual machine (.vmx) file






share|improve this answer












For me, I had to add mks.gl.allowBlacklistedDrivers = "TRUE"to my virtual machine (.vmx) file







share|improve this answer












share|improve this answer



share|improve this answer










answered Dec 1 '17 at 18:21









BXL

585




585












  • why did you have to do so?
    – Pierre.Vriens
    Dec 1 '17 at 19:49


















  • why did you have to do so?
    – Pierre.Vriens
    Dec 1 '17 at 19:49
















why did you have to do so?
– Pierre.Vriens
Dec 1 '17 at 19:49




why did you have to do so?
– Pierre.Vriens
Dec 1 '17 at 19:49


















 

draft saved


draft discarded



















































 


draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f537787%2fenable-3d-hw-acceleration-on-vmware-workstation-10-on-ubuntu-14-04%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

Mangá

 ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕