I’ve been testing a Windows 10 Qube for about a week now, and things have been going pretty well, but tonight, I lost network connectivity. I am thinking it was my ISP had a short outage, because the issue seem to be on my laptop as well, but not 100% sure.
Anyway, when it happened, I swapped back to dom0 and the network qube to check things, and the Windows qube blue screened and shut down unexpectedly. The bugcheck was 0x50, which is PAGE_FAULT_IN_NONPAGED_AREA. I tried restarting it, but it went through the “unclean shutdown” disk check, then shut back down. I noticed then I got the “VM failed to start - qrexec failed to connect to qube” message (paraphrased).
After that, I decided to just do a complete shutdown and power cycle, and try to bring it back up. I got Qubes back up fine, and checked networking, and it was fine. I started the Windows 10 Qube, and it started up fine (which is where I discovered the bugcheck code in Event Viewer), EXCEPT networking was not working. The Xen Net driver was running, but it didn’t seem to be able to pull the IP config. I shut it down again, and the “qrexec failed to connect” message came up again, which I found strange. I started it up again, and still no net, but I checked both sys-net and sys-firewall to check to see that:
- The computer was connected to the network, and to the Internet fine.
- The vif adapter for the Qube was created with the correct IP and Mac address that matched the generated libvirt template. sys-firewall showed the proper routes for it.
Also, I have persistent USB passthrough devices which showed up in Windows, and I can pass the keyboard and mouse to the Windows Qube normally (likely since it is using IP to connect to the stub domain). However, my detach script I came up with would not work, likely because the communication via qrexec and the qubes daemon back to dom0 was not working. In fact, the Event Viewer said that the QdbDaemon startup timed out after 45 seconds.
I guess the question now is where I need to be looking to solve the problem. The Qubes daemon/qrexec backend problem needs to be solved for sure, but does networking setup run through that link as well? Or is it just handled through the Xen Net driver doing DHCP to (I guess) sys-net or sys-firewall? Does the qubes backend rely on networking? Chicken or egg?
I looked at the guest-dm logs, and I don’t see anything out of the ordinary. There are several runs of logs in the log file from startups/shutdowns over the past week, and the latest one looks pretty much like all the previous ones. No errors or warnings that I can see.
It’s late now, so I’ll attack it again tomorrow.
Thank you in advance for any advice!