Win qubes and sys-gui-gpu

I never tried in 4.1 because I didn’t have a need, but now under 4.2 I am desperate to have Win 10/11 qube fully functional.

So I set for Win 7/10/11 guivm to be sys-gui-gpu. They start, but no gui for any. Neither choosing specific application from the menu to start (Wordpad, for example) helps. Just silence while green dot behind their name in sys-gui-gpu Qube Manager… Funny.

Has anyone, including devs (@marmarek) tried and succeeded to run Win qubes in sys-gui-gpu actually?

1 Like

sys-gui-gpu is purpose is to manage Qubes OS from a qube and detach the GPU from dom0 to reduce attack vectors.

it is not supposed to be used as a regular qube to have GPU available, for instance sys-gui-gpu does not have network access, like dom0.

I never said something like that. I’m using sys-gui-gpu for 2 years probably, but never Win qube in it.

My question is specific: has anyone tried to run Win qubes in sys-gui-gpu, because I can and have a whole set of Linux qubes succesfully running in sys-gui-gpu.

1 Like

My apologies, I did not understand your question correctly the first time.

2 Likes

I can confirm a qube with Windows installed in it does not display in a sys-gui-vnc either, although it works when using dom0 for display. My sys-gui-vnc works fine as all my AppVMs are displayed.

3 Likes

Yeah HVM qubes don’t display in sys-gui session for me , I have tried in 3 devices and filed a GitHub issue for the bug few days back, is that the case for everyone here? I mean does Ubuntu or any other HVM not show it’s GUI under sys-gui session? PVH mode VMs Which are Linux based here work fine.
I can still access Linux HVMs using xen console from qubes manager but that’s not a real GUI

3 Likes

Issue tracking for HVM qubes not having a GUI under sys-gui

You can also report the status or any relevant information on that GitHub issue if it’s relevant to all HVM machines, otherwise it’s possibly different.
I didn’t know that it affected sys-gui-vnc and sys-gui-gpu , but I suspected so.
This would help developers to know more about the issue to fix it :slight_smile:

1 Like

Unfortunately, there are bigger issues with Win qubes (qwt under 4.2), that are adressed long time ago there, but to no avail.

I was able to confirm that the problem isn’t hvm or “standalone” as in the bugreport, as hvm standalone debian systems made from a debian-xfce template work fine.

However, putting windows 7 into seamless mode did not work either. Does anyone know how the qwt windows 7 graphics driver differs from the qubes driver for debian and fedora?

Has anyone tried the new windows 10 seamless mode in a sys-gui or sys-gui-vnc? qubes-windows-tools: Support for Windows 10/11 · Issue #1861 · QubesOS/qubes-issues · GitHub seems to imply that the windows 10/11 seamless mode is done but you’ll have to build it yourself

(Note: i recommend doing initial debugging in a sys-gui-vnc so you can see policy permission error notifications, and you dont have to keep logging out/logging in)

1 Like