update Nov 22nd: after a reboot DispVMs are starting as usual. Hope this is a good sign.
today I noticed that instead of a DispVM fedora-32-dvm is started every time I try to start a DispVM from the menu.
I’m running Q4.0.3. dom0 is fully updated (today) to security- testing. fedora-32-dvm is based on a freshly installed and fully updated fedora-32 template. I’ve (tried to) set fedora-32-dvm as the default for dispvms in dom0 (qvm-prefs fedora-32-dvm template_for_dispvms).
If I try to start a terminal in a DispVM from dom0 via “qvm-run --dispvm=dvm-template --service qubes.StartApp+xterm” I get “Got empty response from qubesd.”
Journalctl reports "permission denied for call b’admin.vm.CreateDisposable’+b. for every attempt to start a terminal in the way described above.
Can anyone help / advice how to fix the situation.