forge/ayakael.net
1
0
Fork 0
Code Issues 15 Pull requests Projects Releases Packages Wiki Activity Actions

guides/virtualized-hardware-acceleration-qubes-os: add graphical artifacts update for linux 7.0
All checks were successful
/ render (push) Successful in 47s
Details

Browse source
This commit is contained in:
Antoine Martin 2026-05-20 09:37:39 -04:00
commit 25de10bb94
Signed by: forge
GPG key ID: D62A472A4AA7D541
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
guides/virtualized-hardware-acceleration-qubes-os.mdwn
View file

@ -200,5 +200,5 @@ dom0. The VM should also be an HVM, like any other VM you attach devices to.
## Known issues
* Fans can sometimes get stuck at 100% when there is no monitor connected. Workaround is to plug a headless displayport adapter. ([read more](https://www.linkedin.com/pulse/running-docker-swarm-cluster-intel-arc-pro-b50-sascha-siekmann-wcwqc#:~:text=Well%2C%20after%2020%20minutes%20the,advice:%20never%20throw%20anything%20away.))
* Using the Intel Arc B50 as dom0's GPU is problematic. After a while, artifacts appear (flickering black bars, black boxes). This seems to be a bug with Xen when dom0 is in PV mode ([qubes os ticket](https://github.com/QubesOS/qubes-issues/issues/10661), [upstream report](https://lore.kernel.org/xen-devel/aYtznP_tT6xNPwf-@mail-itl/T/#u)). My workaround is to use a different GPU for dom0, which defeats the purpose of pre-allocating VRAM, but alas... hopefully this is fixed soon.
* Using the Intel Arc B50 as dom0's GPU is problematic. After a while, artifacts appear (flickering black bars, black boxes). This seems to be a bug with Xen when dom0 is in PV mode ([qubes os ticket](https://github.com/QubesOS/qubes-issues/issues/10661), [upstream report](https://lore.kernel.org/xen-devel/aYtznP_tT6xNPwf-@mail-itl/T/#u)). My workaround is to use a different GPU for dom0, which defeats the purpose of pre-allocating VRAM, but alas... hopefully this is fixed soon. (update 2026/05/20 - since update to linux 7.0, these artifacts happen a lot less frequently)
* Quite often, VM hangs for a moment, and kernel log shows: `xe 0000:00:08.0: [drm] *ERROR* TLB invalidation fence timeout, seqno=287 recv=286`. Still investigating a workaround. (seems to be related to [gitlab.freedesktop.org/drm/i915#14469](https://gitlab.freedesktop.org/drm/i915/kernel/-/work_items/14469#note_3170015) and [gh/strongtz/i915-sriov-dkms#332](https://github.com/strongtz/i915-sriov-dkms/issues/332))