I can change the Xen config, but I can't figure out how to make VNC work properly.
With the default HVM, the Qubes OS will configure Xen to use device model stub domain for the devices (<emulator type='stubdom-linux'/>), including the <graphics type='vnc'/>. So the VNC server will be started for the stub domain.
When I try to connect to the VNC server from dom0 I can see this message:
"Guest has not initialized the display (yet)"
https://i.stack.imgur.com/D5HsM.png
VNC client connects to the vmname-dm VM.
When I searched for this problem, I've found this config, suggesting that VNC should work with stub domain emulator (but it's not certain):
https://www.mail-archive.com/libvir...@redhat.com/msg00118.html
There is also example Xen config for stub domain with VNC that seems to work:
https://wiki.xenproject.org/wiki/StubDom
But there are two separate configs: for HVM and HVM-dm, but in my case there is singe libvirt config and I don't know how to use these example configs for my case.
Can someone suggest how to fix this issue? Is it just wrong libvirt config or does Qubes OS somehow interfere with video/graphics/something else that is breaking VNC.