It seems that the problem is that when using the kernel provided by dom0, the nomodeset kernel option is set by default which is stopping amdgpu driver from loading.
Try to use in-VM kernel instead of a kernel provided by dom0:
Managing qube kernels | Qubes OS
Loaded the drivers witrh the second cmd and no error. 
What should I proceed with next?
I assume the script and conf stuff to get the second display?
user@Games:~$ sudo journalctl -f -n0
Nov 09 18:26:50 Games qubes-gui[1042]: Not supported selection_req target 0x162 text/plain;charset=utf-8
Nov 09 18:26:50 Games qubes-gui[1042]: Not supported selection_req target 0x162 text/plain;charset=utf-8
Nov 09 18:26:52 Games sudo[1368]: user : TTY=pts/3 ; PWD=/home/user ; USER=root ; COMMAND=/usr/sbin/modprobe amdgpu
Nov 09 18:26:52 Games sudo[1368]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Nov 09 18:26:52 Games sudo[1368]: pam_unix(sudo:session): session closed for user root
Nov 09 18:26:52 Games systemd[1]: Starting qubes-sync-time.service - Update time from ClockVM…
Nov 09 18:26:52 Games systemd[1]: qubes-sync-time.service: Deactivated successfully.
Nov 09 18:26:52 Games systemd[1]: Finished qubes-sync-time.service - Update time from ClockVM.
Yes, just follow the guide.
1 Like
Awesome so I got a second display and requesting to first configure i3 with option ENTER for yes.
Main issue is that Im not getting any inputs via mouse and keyboard so can’t interact
I did install:
apt install xserver-xorg-input-kbd xserver-xorg-input-libinput xserver-xorg-input-mouse i3
Installed openbox for window manager.
Do you have separate mouse/keyboard for your qube?
Yea I do!
Unfortunately doesn’t seem to work when I attach it, so I tried the one Im using for dom0 right now, I attached it to the Qube, which populated a new device and attach device and started working with my primary keyobard and mouse(only required this double attach once tho)
So I will have to get another mouse and keyboard set tomorrow and should be fine.
Just experimenting with the window managers to see which will best work but other seems good for now!
Thanks for the assistance
Okay so the diplay is showing me a window that a black screen like seen with openbox but has some network info, stuff like no battery, the ram, date, time and a icon for the networking.
Can’t interact with anything beside the the icon, and doesn’t seem that the other tools don’t populate like tint2, etc which I assume is due for it to be config in a autostart file which I can’t find.
So now Im trying enlightenment instead which apparently is more feature rich and interactive and still the display only shows this basic window.
Just need something easy to interact with so I can launch applications but just seems to be this plain black screen with no obvious way to interact. No right clicking on the screen for a drop down, etc
Would I be correct ot say that GNOME could work? but again the whole thing with the black so not sure if that would change it.
No idea, I didn’t try this setup with a separate display/mouse/keyboard myself so you’ll need to try it yourself or wait for someone who tried it to share their experience.
Yea that the thing as well, even with all this setup trying to use the GPU on a single monitor doesn’t work, even with the device attached, what the experience for you as you mentioned you don’t use the additional display for your GPU pass-through? Does your GPU just normally get utilized to the vm you have it connected to?
Apps that support Vulkan are using the GPU by default without any additional configuration.
If the apps don’t support Vulkan then you can use VirtualGL for them to use GPU:
Seamless GPU passthrough on Qubes OS with VirtualGL
But the performance could be lower compared to the dedicated display, because the image rendered by GPU is copied to dom0 using CPU to be displayed there (if CPU is the bottleneck).
Good day,
It tried the guide, installed everything, chose the correct options and made the changes with the config, disabled MSI and installed mesa and added export VGL_DISPLAY=egl to the last line of the required file.
Made a new standalone for gaming from it and now when I open any application such as terminal it will break and the crash. installed the latest virtualgl which i believe was 3.1.1
Not sure if you experienced any any point?
Hi,
I got up to the point where I get a external display with the script, my issue is the windows manager, I tried openbox and didn’t work out so installed GNOME instead but output was still a black screen with some minor sys info and the bottom right.
I know I am probably have missing understanding with the windows manager section to get some sort of functional and interactive GUI in the output.
I’m using NVIDIA GPU and it works for me.
Clone debian-12-xfce to d12x-gpu.
In d12x-gpu install virtualgl from the repository:
VirtualGL | Downloads / VirtualGL YUM and APT Repositories
Run:
sudo vglserver_config
Choose:
3
n
x
Create /etc/profile.d/vglrun.sh file with export VGL_DISPLAY=egl inside.
Install mesa-utils package:
sudo apt install mesa-utils
Install nvidia-open drivers.
Create app qube based on d12x-gpu template.
Set its virtualization to HVM, kernel to (provided by qube), disable memory balancing, set initial memory to 2 GB and attach GPU.
Start it and run this command in tits terminal to check GPU usage:
vglrun glxinfo | grep "OpenGL renderer"
I removed it from /etc/profile and created and added to the ne file as instructed.
All the other steps I’ve already done. Created the app vm will all need changes and the terminal still ends up freezing and then closes.
Explain in more detail what are you trying to do that is causing the terminal to freeze and then close.
Does it happen when you run vglrun glxinfo | grep "OpenGL renderer"?
Unable to do anything, I just start any application and it will crash, no cmd execution as even terminal crashes.
Sorry for delay just doing some of my own troubleshooting.
Won’t it cause an issue if i install those drivers since using an amdgpu?(havent installed any drivers in previous attempts)
I just described the steps that I did for my setup with NVIDIA GPU, of course you don’t need to install NVIDIA drivers if you have AMD GPU. You can try to install AMD proprietary drivers for a test instead.
You can also try to update your Debian template to trixie to see if VirtualGL will work with amdgpu driver in it.
The VirtualGL didn’t work for me with nouveau driver in Debian 12, but when I updated it to trixie then it started to work.
Hi so on Debian 12 I eventually managed to fix the issue with the crash and free of applications however when testing with an application like Alpaca from Flathub using Mistral nemo for example it will give the resource limitation error which such be resolved with the GPU(edit: tried some lightweight games and same issue act basically as if there was no passthrough). I was test the application on Kicksecure and Ubuntu outside Qubes of course without issue with the exact model.
Trying to install drivers from AMD which cause the same application breaking issue, did the same with the backports method and same issue.(Note all testing each was done entirely separate clones)
Upgrading a template to Debian 13 also causes the same issue with application when starting up an application, eventually one is prompted about how to handle grub which is about 6 different options however top two is keep the same or install the changes essentially which I chose the ladder and check my grub configs and the changes I made remained.
Which setup are you talking about?
With separate display or with seamless mode and using Vulkan/VirtualGL?
If second then are you starting the apps with vglrun?
What’s the output of this command?
vglrun glxinfo | grep "OpenGL renderer"