I tried to find a computer I could install Qubes 4.2 on in order to do some testing.
First was a Xeon server. Booted the installer media, got grub and selected the installer... black screen. Bust. But it's a server, so not a huge surprise, but I was hoping.
Next I tried my previous desktop. Of look, no power supply. Easy enough to rectify.
Oh listen, beep codes. Turned our to be memory issue (seating dust, bad slot... whatever it was it's not happening now).
Booted and grub said it was Ubuntu 14.10! Wow, what a throwback. It turned out it was actually 16.04, but that's still pretty old. Worked fine though.
The CPU was an AMD Phenom II X4 965, which was from 2009. It's 3.4 GHz, but, unsurprisingly, it didn't have IOMMU support and so I couldn't run Qubes on there. The installer didn't even manage get into grub. Some error about i386 modukes not found (which is peculiar, since this is a 64-bit CPU).
So the search continues...
Run it inside proxmox?
for evaluation possibly but running a hypervisor on top of a hypervisor is not recommended for security. "nesting" increases attack surface.
Meh.
nostr:note15ppatp3l3a0l6pdfjvkyxtupv47nhqvjuqzwxs6pt8mgp68gzsyqzkpat5
I'm testing USB passthtu to a physical hardware device, so virtual machines are not the solution here, and it's not very often I say THAT.
qubes depends on xen and xen hardly runs on anything
whonix is better if you want to try containing everything
a home made solution would be to run every app inside nspawn, not sure how to navigate the interface to the GUI, should be able to use a container network interface, linux namespaces are practically as good as xen isolation
