I have tried what happens in Qubes R4.1 (Version 20201014 Alpha) with Windows and QWT 22.214.171.124. So far, the following results are obtained:
For Windows 7 with QWT installed, the VM from R4.0 can be imported, but not started - error in
Couldn't open /sys/bus/pci/drivers/pciback/allow_interrupt_control: File or directory not foundThe VM stays in an intrermediate state, shown as running or starting, but it cannot be shutdown or killed, claiming it were not running.
For Windows 10 with QWT installed, the VM from R4.0 can be imported and started, but somewhere in the boot process, the VM crashes with the error message
INACCESSIBLE BOOT DEVICE,an error I already have seen in my earlier tests on Qubes R4.0. This error does not make sense as the VM was started, so it has access to the boot device. This might have to do with switching to a Xen disk driver???
For Windows 7 without QWT, the VM from R4.0 can be imported and started. The QWT can be installed, like documented for R4.0, even with the option to move the user profiles. The VM seems to behave quite normally, but is cheating on that behalf: The Qube Manager shows the VM as running (green dot), although the Qubes PRC Agent, which should have been started automatically, is not running. The agent cannot be started manually, showing error 1067 (Process terminated unexpectedly). Communication with Qubes does seem to work only partially, since file copy to/from other VMs does not work, but the VM stays running. - The screen resolution stays fixed at 1920 x 1024 (my screen is 1920 x 1200), and the only other option shown is 800 x 600. Trying to change the resolution renders the VM inoperative - it cannot even be killed, and Qubes has to be restarted to get access to it again.
An AppVM based on this Windows 7 template cannot be started. It crashes with the
For Windows 10 without QWT, the VM from R4.0 can be imported and started. However, the VM stays invisible, until
qvm-features gui-emulatedis set to 1. The Xen drivers and QWT can be installed, like documented above. Then, the VM seems to behave quite normally, but is cheating on that behalf: The Qube Manager shows the VM as running (green dot). The Qubes RPC agent is not started, although its start type is set to Automatic, but it can be started manually. Communication with Qubes does not seem to work, since file copy to/from other VMs does not work, but the VM stays running, as long as
qvm-features qrexecis not set. - The screen resolution is set to 1024 x 768, but can be changed to 1920 x 1080 or 800 x 600, and the system stays responsive.
An AppVM based on this Windows 10 template can be started and behaves like the template.
So there are small changes from the previous version (20200914) of Qubes R4.1, but there remains still a lot to do with respect to QWT and the Xen drivers. Is anyone out there willing to dive into the Windows and drivers mess?!