When letting the installer create the default VMs, I would like the sys-* ones to be based on a minimal image.
A backup that is more space efficient (incremental backup) and the ability to include/exclude certain files.
Allow permanent device bindings based on device IDs instead of the port it is connected to.
Some sort of best practices guide on how to safely use QubesOS (“if I want to be protected against X, then I have to do Y” and “those are general security and privacy best practices”). Make this documentation accessible for the less technical people.
If you still get the popup asking you to confirm the file transfer, then it’s basically just a graphical version of qvm-copy-to-vm (note: not qvm-copy, which doesn’t specify the target machine on the command line, forcing you to choose it in the dialog).
I don’t know why but whenever I use qvm-copy-to-vm <vmname> <filename> I still get the dialog asking me to choose the VM. How come?
I wouldn’t bother with a pop-up confirmation, graphical ques would be fine. But then I don’t work with really sensitive material and a strict need for separation, unlike some other users. Maybe that’s just too lax for Qubes, as @qubist implies.
That is the well known contradiction between security and usability. Take your suggestion to an extreme case, e.g. imagine one’s cat walking on the desk, stepping on the mouse button, dragging (and then stepping on the “Enter” key to confirm inside a potential popup, if there is one). Of course, that is a probably a silly example because one should never allow cats walking on computers or leave an unlocked desktop when not in use but you get the idea. Dangerous things can happen even when one is tired, or when one spills something on the desk. Nothing can prevent all possible insecurities caused by human error but we should be careful when we request/implement insecurities deliberately.
Personally, I would like to have the convenience you suggest too. However, that should come:
as an option which one unlocks explicitly (after a big warning)
in a controllable way - one should be able to control between which qubes and in which direction the feature should work, e.g. I may want to be able to drag to a disposable but I may not like to drag from a network connected qube to a disconnected one, or from “personal” to “work” and vice versa, etc.
State-preserving VM suspends
A tool to “gracefully retire” archived qubes (extract documents and browser passwords and save them in a convenient way), a tool to export and import qubes as vmdk’s
More qube colors
Liteqube in default setup
Full Windows guest support (seamless mode and decent performance)
Screenshot tool working out of the box
Permanently attach USB devices regardless of bus id’s they get
I have 2 qubes installs. One is actually for privacy, and the other is a test lab. I think qubes is a fun virtualization lab, where you can be operating in a GUI locally and interacting with your VMs. I wish more UX attention was focused on this. I desperately need folders in my qubes manager or some better organizational system, ive resorted to giving them symbolic prefixes to make filtering easier.
Also, while this is possible, ive noticed no OS is really tinkering with it: The 11th+ gen i915 gpus support true SR-IOV and intel has posted some stuff in github to indicated that the VFs can be assigned to outputs, even ones that don’t exist physically (they might electrically). If you combined this with the dummy monitor driver that the looking-glass dev is tinkering with I think you could accelerate 3-7 qubes on the i7/i9 gpus. You can either go the IVSHMEM or h264/h265 streaming route. At the very least you could just use it for ffmpeg in a qube
I’ve successfully gotten it work work in a windows VM using patched i915 kernel module on arch linux
My use of the term Tabs is a bit like Favorites in a browser. With a quick click or two, one creates Tab for a specific webpages. But a Tab for quick access to a program.
I wanted to work up some examples with exact description, but I have been hampered by storms which have made power - intermittently available, internet less available, my need to do errands for other people. I am both old and lazy.
Better hardware compatibility. I have 3 laptops, all made between 2019-now, from different manufacturers, and I have only been able to get one to work with Qubes (although with no external monitors). Too bad it’s the only laptop I have that is powerful enough to play games on… I could dual boot or get a new system, but I’d either need to buy more storage or buy a new laptop.
That being said - I also understand the incompatibilities are a result of the very specialized requirements. I just really like the idea of Qubes and would love to try and use it as my main OS.