31–40 of 41 posts
Earlier quoted context omitted.
If only the hardware compatibility was better. It hasn't worked on my past three laptops.
There is a hardware compatibility page with user reports. The main thing is that, to be practical, it needs at least 16GB of RAM. With only 16GB, you will want to use the ZRAM swap driver on your linux VMs. Dunno if any equivalent exists for windos.
No need for chatty telemetry at Windows and app level in the background.
What I am really looking for in Qube is when the window of Windows VM gets minimized, it performs a CPU suspend, preferably within its VM. No need for chatty telemetry at Windows and app level in the background.
I hope to try qubes one day, it's a shame that my current hardware isn't supported. If I wanted to learn how to add support for my own hardware where would I start (would probably be quite an undertaking, but might be worth learning about regardless of how far I'd get).
Otherwise, feel free to open an issue on the Qubes issue tracker and the Core Team will look into it.
I have been trying to buy a Librem 14 for Qubes but need a backup. What’s best-in-class?
What I am really looking for in Qube is when the window of Windows VM gets minimized, it performs a CPU suspend, preferably within its VM. No need for chatty telemetry at Windows and app level in the background.
Qubes supports VM suspension so if you wanted to you could easily create a simple shell script to suspend and resume upon the Windows VM window becoming minimized and reopened. You could use `xprop -spy ` to check the window status without polling and `qvm-pause`/`qvm-unpause` to suspend/resume the VM.
While the suggestion does not encroach inside the Windows’ VM to perform “their” CPU suspension, it is a better idea to process suspend the host’s KVM underlying that Windows VM. Hope that the guest’s video driver doesn’t leave its hardware in an inconsistent state for the host’s main video driver and its entire system.
This tidbit needs to be made a prominent FAQ on Qube website.
Earlier quoted context omitted.
There is a hardware compatibility page with user reports. The main thing is that, to be practical, it needs at least 16GB of RAM. With only 16GB, you will want to use the ZRAM swap driver on your linux VMs. Dunno if any equivalent exists for windos.
Well that isn't universal. I've made do with 8gb and get on fine with 16gb while never having heard of that ZRAM driver.
1. A dev machine. I have a persistent and static disposable version of this build.
2. An anon build connected to whonix. Again, I have persistent and disposable versions.
One thing I had to do was compile the QWT v4.1.65 iso and install the resulting msi. Other than that it all works flawlessly and provides great peace of mind for those occasions when I have to use Windows.
Awesome work Elliot, and much appreciated. I've just got Windows-10 ltsc working on qubes 4.1 with whonix 16. My 2 use cases are: 1. A dev machine. I have a persistent and static disposable version of this build. 2. An anon build connected to whonix. Again, I have persistent and disposable versions. One thing I had to do was compile the QWT v4.1.65 iso and install the resulting msi. Other than that it all works flawl…