[GH-ISSUE #1233] --no3d in virtual machines? #838

Closed
opened 2026-05-05 06:57:10 -06:00 by gitea-mirror · 6 comments
Owner

Originally created by @laniakea64 on GitHub (Apr 18, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1233

firejail self-build from e31d453f4e
Xubuntu 16.04 VirtualBox guest (under VirtualBox 5.1.18)

My Xubuntu 16.04 VM has VirtualBox Guest Additions installed and 3D acceleration enabled. But, within that VM, I would like to disable hardware acceleration only for 2048-qt. So I tried using firejail with the --no3d command-line option -

firejail --no3d --noprofile 2048-qt

And 2048-qt had hardware acceleration enabled. 🙁

Now as I recall, compared to the "standard" graphics drivers, there is some weirdness in how VirtualBox Guest Additions does 3D acceleration. (I don't know any details, sorry.) So I'm not sure whether --no3d as it is should be expected to work in a VirtualBox VM.

Can firejail be used to disable hardware acceleration for individual programs inside a VirtualBox VM?

Originally created by @laniakea64 on GitHub (Apr 18, 2017). Original GitHub issue: https://github.com/netblue30/firejail/issues/1233 firejail self-build from https://github.com/netblue30/firejail/commit/e31d453f4ebec9974f7bcaee33cadaa83e12b791 Xubuntu 16.04 VirtualBox guest (under VirtualBox 5.1.18) My Xubuntu 16.04 VM has VirtualBox Guest Additions installed and 3D acceleration enabled. But, within that VM, I would like to disable hardware acceleration only for 2048-qt. So I tried using firejail with the `--no3d` command-line option - ``` firejail --no3d --noprofile 2048-qt ``` And 2048-qt had hardware acceleration enabled. 🙁 Now as I recall, compared to the "standard" graphics drivers, there is some weirdness in how VirtualBox Guest Additions does 3D acceleration. (I don't know any details, sorry.) So I'm not sure whether `--no3d` as it is should be expected to work in a VirtualBox VM. Can firejail be used to disable hardware acceleration for individual programs inside a VirtualBox VM?
gitea-mirror 2026-05-05 06:57:10 -06:00
Author
Owner

@chiraag-nataraj commented on GitHub (Sep 30, 2018):

@laniakea64 Is this still an issue?

<!-- gh-comment-id:425686047 --> @chiraag-nataraj commented on GitHub (Sep 30, 2018): @laniakea64 Is this still an issue?
Author
Owner

@laniakea64 commented on GitHub (Oct 5, 2018):

Yes, this is still an issue in self build from 9db1effb59

<!-- gh-comment-id:427216380 --> @laniakea64 commented on GitHub (Oct 5, 2018): Yes, this is still an issue in self build from https://github.com/netblue30/firejail/commit/9db1effb598027c3facfa009bf4a5bcf90821b00
Author
Owner

@chiraag-nataraj commented on GitHub (Oct 6, 2018):

Going to see if this is an issue in e.g. qemu. Are you launching virtualbox with firejail as well?

<!-- gh-comment-id:427573487 --> @chiraag-nataraj commented on GitHub (Oct 6, 2018): Going to see if this is an issue in e.g. `qemu`. Are you launching `virtualbox` with `firejail` as well?
Author
Owner

@chiraag-nataraj commented on GitHub (Oct 6, 2018):

Hmm, this seems to be an issue with qemu as well. I suspect this is going to be a problem with any virtualization platform. @netblue30 Do you understand why this is happening?

<!-- gh-comment-id:427574221 --> @chiraag-nataraj commented on GitHub (Oct 6, 2018): Hmm, this seems to be an issue with `qemu` as well. I suspect this is going to be a problem with any virtualization platform. @netblue30 Do you understand why this is happening?
Author
Owner

@laniakea64 commented on GitHub (Oct 6, 2018):

Are you launching virtualbox with firejail as well?

No

<!-- gh-comment-id:427600987 --> @laniakea64 commented on GitHub (Oct 6, 2018): > Are you launching `virtualbox` with `firejail` as well? No
Author
Owner

@laniakea64 commented on GitHub (Apr 6, 2020):

--no3d appears to be working for me in VirtualBox 6.0.18 VM, Xubuntu 18.04 64-bit guest with firejail 0.9.62 -

$ /usr/lib/nux/unity_support_test -p
OpenGL vendor string:   VMware, Inc.
OpenGL renderer string: SVGA3D; build: RELEASE;  LLVM;
OpenGL version string:  2.1 Mesa 19.2.8

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
$ firejail --version
firejail version 0.9.62

Compile time support:
        - AppArmor support is enabled
        - AppImage support is enabled
        - chroot support is enabled
        - file and directory whitelisting support is enabled
        - file transfer support is enabled
        - firetunnel support is disabled
        - networking support is enabled
        - overlayfs support is enabled
        - private-home support is enabled
        - seccomp-bpf support is enabled
        - user namespace support is enabled
        - X11 sandboxing support is enabled

$ firejail --noprofile --no3d /usr/lib/nux/unity_support_test -p
Parent pid 1608, child pid 1609
Child process initialized in 21.98 ms
libGL error: failed to open drm device: Permission denied
libGL error: failed to load driver: vmwgfx
OpenGL vendor string:   VMware, Inc.
OpenGL renderer string: llvmpipe (LLVM 9.0, 256 bits)
OpenGL version string:  3.1 Mesa 19.2.8

Not software rendered:    no
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:       no

Parent is shutting down, bye...
$ 
<!-- gh-comment-id:609964890 --> @laniakea64 commented on GitHub (Apr 6, 2020): `--no3d` appears to be working for me in VirtualBox 6.0.18 VM, Xubuntu 18.04 64-bit guest with firejail 0.9.62 - ``` $ /usr/lib/nux/unity_support_test -p OpenGL vendor string: VMware, Inc. OpenGL renderer string: SVGA3D; build: RELEASE; LLVM; OpenGL version string: 2.1 Mesa 19.2.8 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 $ firejail --version firejail version 0.9.62 Compile time support: - AppArmor support is enabled - AppImage support is enabled - chroot support is enabled - file and directory whitelisting support is enabled - file transfer support is enabled - firetunnel support is disabled - networking support is enabled - overlayfs support is enabled - private-home support is enabled - seccomp-bpf support is enabled - user namespace support is enabled - X11 sandboxing support is enabled $ firejail --noprofile --no3d /usr/lib/nux/unity_support_test -p Parent pid 1608, child pid 1609 Child process initialized in 21.98 ms libGL error: failed to open drm device: Permission denied libGL error: failed to load driver: vmwgfx OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 9.0, 256 bits) OpenGL version string: 3.1 Mesa 19.2.8 Not software rendered: no 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: no Parent is shutting down, bye... $ ```
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#838
No description provided.