I have installed the latest version of QubesOS in VMware Workstation. Hardware resources assigned are 10GbRAM, 4CPU cores, 60Gb Nvme.
Do you know why when i performed any operation(start/setting/etc) in any qube, whole machine is freezeing for 10-20 seconds?
As long as your CPU is reasonably modern, everything should at least run. RAM will be the deciding factor in how well it runs. 16 GB should be adequate, as long as you aren’t running too many VMs at once.
Is not the latest configuration:
PC Fujitsu Intel Xeon E3-1230V2(8 Threads) up to 3.7 Ghz, 16 gb ddr3, SSD 240 GB si 2 x HDD 1 TB RAID.
Ready to be upgrated from 16Gb RAM to 32 and an enterprise SSD 960Gb from Kingston
With the caveat that QubesOS as a guest is not a supportable production configuration (as it negates several security safeguards, and adds other problems).
Qubes as a nested guest relies on the outer hypervisor (such a VMware) to give it the right machine layout and cpu/bios capabilities.
E.g. I found VMware WS on Windows was unable to virtualize QubesOS on AMD Zen CPUs, others have said it works on their Intel CPUs, but that can depend on the physical machine cpu and bios to report things well enough that VMWare can ingest the configuration and map it well to a virtual configuration for the guests.
Anyway…I had good results recently using Linux KVM as the outer hypervisor on the Zen machines. Posted in a recent thread, search for KVM.
@brendanhoar unfortunatelly not. I have deployed ParrotOS and once i have lanched the update process , whole machine freezed for few seconds. IN QubesOS, once i started a qube-> same behaviour
Hardware resources allocated were in both cases the same: 10Gb RAM, 4 core CPU, SSD 60Gb