From 446718f5bd89819d2dd167d8bcb6cc9619d7a2d4 Mon Sep 17 00:00:00 2001 From: Colleirose <167055039+colleirose@users.noreply.github.com> Date: Thu, 11 Dec 2025 21:19:08 +0000 Subject: [PATCH] Add more information about GPU-accelerated tasks It is possible to run GPU-accelerated tasks on Qubes if you have one GPU for the Qube and another for dom0, but it comes with significant trade-offs. I added information about this. --- introduction/faq.rst | 14 +++++--------- 1 file changed, 5 insertions(+), 9 deletions(-) diff --git a/introduction/faq.rst b/introduction/faq.rst index 67021932..7ebcf1d1 100644 --- a/introduction/faq.rst +++ b/introduction/faq.rst @@ -389,19 +389,15 @@ Can I watch YouTube videos in qubes? Absolutely. -Can I run applications, like games, which require hardware acceleration? -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +Can I run applications, like games and video editors, which require hardware acceleration? +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -Those won’t fly. We do not provide GPU virtualization for Qubes. This is mostly a security decision, as implementing such a feature would most likely introduce a great deal of complexity into the GUI virtualization infrastructure. However, Qubes does allow for the use of accelerated graphics (e.g. OpenGL) in dom0’s Window Manager, so all the fancy desktop effects should still work. App qubes use a software-only (CPU-based) implementation of OpenGL, which may be good enough for basic games and applications. - -For further discussion about the potential for GPU passthrough on Xen/Qubes, please see the following threads: - -- `GPU passing to HVM `__ - -- `Clarifications on GPU security `__ +This is possible with some configurations, but it is currently not recommended. It's usually a better idea to have a separate device for GPU-intensive tasks, but if that isn't practical for your use case and you absolutely must use GPU acceleration, this can be done with significant effort and security trade-offs. For instructions, see [Create a Gaming HVM](https://forum.qubes-os.org/t/create-a-gaming-hvm/19000) on the Qubes forum. +Qubes OS uses the CPU to render graphics outside of dom0 and does not currently implement GPU virtualization, so any GPU-based tasks will require giving a Qube full access to your GPU, and therefore any security vulnerabilities in your GPU will be exploitable if the Qube is compromised. However, there are plans to implement GPU virtualization in Qubes OS in the future, see `the GPU acceleration project on GitHub `__ for more information. +Furthermore, your system will need two GPUs - one to render the Qubes desktop, and one for your GPU-accelerated Qube. If you have an integrated graphics chip on your CPU, you can use the CPU graphics to render Qubes and the dedicated graphics for your GPU-accelerated Qube. Also note that you will likely experience noticeably worse performance in video games and other CPU-intensive programs unless you have a good CPU due to the virtualization overhead. Is Qubes a multi-user system? ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^