Granted at the current rate of speed increase, even bad low-level emulation will longterm be feasile on COTS parts that ain't expensive.
For a lot of people, a #VirtualBox on some #MiniPC would likely be sufficient, but then again they likely just want to play something and not tinker much.
I could not for the life of me get macOS to run in Virtual Box.
So I cheated and download a premade VM of an older build of OS X Mountain Lion (10.8).
Perhaps it was good that I couldn't get a current release to work. Even though 10.8 is 15 years old and was last updated 8 years ago, my mouse lagged as I moved it across the screen
I presume it was a display (graphic) issue, given that I could still download and install software superfast
I had massive problems with #DDEV, #colima and #qemu on a Mac M1 the last few days. The system was super fast, but then out of the blue requests took 1 to 3 minutes and the qemu process went up to 400% CPU workload.
It looks like (and I cross my fingers) the problem was running colima with a docker installation from Docker-Desktop. I uninstalled it and installed Docker with "brew install docker" in lieu of "brew install --cask docker" and everything is working fine again. By now.
Not gonna lie, the most useful skill I picked up in the last two months was setting up a #QEMU install to test my custom kernels (and some made up hardware on the side).
If you want to be as punk as that, I have the instructions right here:
VFIO: improved live migration support, no longer an experimental feature
GTK GUI now supports multi-touch events
ARM: emulation support for bpim2u (Banana Pi BPI-M2 Ultra) board and neoverse-v1 (Cortex Neoverse-V1) CPU
x86: CPU model support for GraniteRapids
and lots more…""""
There's a vision in my mind for workflow that involves VMs and GPU passthrough. The idea is to have a stable foundation (e.g. Debian) and spring off various VMs as seen in the chart
Arch for proton gaming.
Ubuntu for work.
Windows for audio and non-proton games.
NixOS for anything else.
I wish I could use NixOS for the base but I am unable to find much documentation for #VFIO. The most promising one are
I now have my Framework laptop running Fedora. I have KVM installed and Proxmox is installed in KVM with nested virtualization enabled on the host. I'm now running a restored VM from a Proxmox backup.
I had to do a bit of data juggling with my external NVMe SSD to import the backup to the correct location to enable me to restore within the Proxmox VM. I also had some initial issues getting the target guest VM to run but I noticed I had my vCPU allocation a bit too high. After adjusting this and removing an additional vNIC and Audio virtual device for Spice, I was able to get it to run.
I'll have to figure out the best way to get data portability of these VMs. Ideally if I could determine how the vma format works that Proxmox uses for backup maybe I can skip the Proxmox VM and load the guest VM directly into KVM on my Framework host.
Or better yet if I can leverage LVM snapshotting and save out a volume of the entire VM then load that directly into KVM/QEMU on the laptop that would be nice.