Thanks @marmarek for keep trying to get things better!
For the 1 point I hope we can at least build version of QWT for further community testing.
@GWeck Thank you for all it testing and I here is some details and workarounds we known:
- Installation without gui-agent (WIndows 10 case) sets gui qvm-feature empty which is not false, so you will see no window next boot. It needs to be unset or 0
- QWT installation time-to-time (always?) activates memory balancing, it would crush VM
- It is better to run installation as Administrator to complete our preparation script which disable recovery mode and recovery console. It helps next boot if you get BSOD
- Disk pv drivers in my case are pretty stable (we builds with 8.2.2) and gives more performance, but it is better to install with second try after moving profile
- Within installation say no reboot question because it might be driver question and installation didn’t finished yet.
- Copy-Paste doesn’t works first boot after installation. Next times all works fine.
- Audio is really scratchy, but there is no QWT in it, device emulates by QEMU. Upstream version use version 4.2, we updated it to 5.1 and it seems better. @marmarek I could PR this, but right after USB request I guess
- It is better (Windows 10 especially) to set qrexec_timeout to 9999 to prevent possibility to break windows updates applying
- We don’t use block device hotplug attaching and advise you too
- We removed QubesNetworkSetup, but bring qnetwork_setup script for manual configuration.
- We have version with 9.0.0 pvdrivers, it gives no advantage and have some problem with uninstalling. Perhaps with next release will be better
And we did not try it on 4.0.
UPDATED: Network pv drivers has DCHP issue, so we disable it by default