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?
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.
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.
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
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