I have a Win10 HVM on Qubes R4.0.4 that is intermittent with regards to the qrexec connection. The qrexec timeout is currently set to 600 so that I can investigate things before Qubes finally forces the VM to shutdown, which can be catastrophic if Windows has already decided to start doing updates or something else important. I have had to revive it by restoring it from backups on occasion because of this.
Each time I start the Win10 vm the Qube Manager shows the yellow dot indicating that it is starting and it may connect and turn green for a number of times that I use it, until it doesn’t. Once it fails to connect it will continue failing for all subsequent attempts, even with shutting down or rebooting Qubes.
The only remedy I have found is to start the VM as normal and then tell it to “restart” from the start menu at which point it will get a xenbus error and freeze solid and the VM’s window can not be closed by any Qubes Gui/qvm command I can find. I either have to restart Qubes or issue a dom0 “xl destroy Win10” command to force it to close that catatonic window. Once I finally get that window closed the next time the VM will start and qrexec will connect properly each and every time until it decides once again that its time to start failing. Then I need to restart/xenbuss-error again to get it working again.
When it does qrexec connect the VM works just fine. When it doesn’t connect the Win10 VM still works fine but without the additional qrexec services until it is forced to close by the timeout. In all other respects it seems to work with no visible errors. I have been snooping around but I don’t know what exactly I need to look for when its not connecting properly, and then it mystifies me as to why a xenbus failure would somehow correct the problem, but only for a while (hours, days, months if not used often).
Q: What is supposed to happen on the Windows side needed to support this qrexec connection? Does that qrexec receiver process have a logfile on the Windows side? I’m just looking for ideas of where to look.
guest-Win10-dm.log (53.8 KB)