I've been making my Quickemu project macOS-compatible; meaning it can run on a macOS host 🍎
Quickemu is a project to quickly create and run optimised Linux, macOS and Windows virtual machines 👍
Here's my test case in action:
This is NixOS ❄️ running a virtual machine of macOS Ventura 🍏 via Quickemu, which is running a virtual machine of Aline Linux 🐧 via Quickemu #linux#qemu
Impressed by how easy it is to run a virtualized MacOS Ventura on Linux with quickemu! I tried some other MacOS virtual machines or Docker images, but none has worked so easily and immediate as with quickemu.
Last I tried screwing around with #zfs, #KVM and #qemu on #slackware I had a bunch of fun with scripts from sbo and dependency hell – since neither is an official slack package.
How does this fare in 2024 if I were to try to get a headless host for my stuff (qubes-like but I like pain)?
As I knew I was on holiday for soft freeze I got all my #qemu maintainer PRs in early for 9.0. It is now released to the wild. The big #arm64 update is FEAT_NV2 emulation as well as a number of enhancements to various board models (and some deprecations of the older unloved code). For #tcg#plugins we now support reading register values as well as a new thread-safe inline ops API. The #gdbstub also saw a number of tweaks. More to come for 9.1 and the tree is now open ;-) https://www.qemu.org/2024/04/23/qemu-9-0-0/
"'block: virtio-blk now supports multiqueue where different queues of a single disk can be processed by different I/O threads
migration: support for “mapped-ram” capability allowing for more efficient VM snapshots, improved support for zero-page detection, and checkpoint-restart support for VFIO
ARM: architectural feature support for ECV, NV, and NV2
ARM: board support for […] raspi4b (Raspberry Pi 4 Model B)"'
@dduque what made my #qemu blindingly fast (for a Windows VM) was to set aside a partition formatted to NTFS, instead of using the default virtual file on the host OS (also #manjaro Linux).
My main laptop is a #Macbook Air running #MacOS, but interestingly, I don't really use the #OS. I use it as if it's a #Chromebook instead. I only launch #Chrome with it (and #QEMU to run #Linux). Every time I HAVE to use the OS at length, e.g. to do something with Finder, it's an exercise in frustration.
What I enjoy very much is the interaction of the hardware with the input UI software (e.g. how the touchpad feels and behaves in conjunction to #software). Not the rest of the system.
Fixed an issue reported by one of our users, seemed "file_data" package couldn't be installed, upon checking it seemed the checksum didn't match, a revision bump solved the issue, trick used, update Haiku sources, create an anyboot.image and boot this in #qemu on #HaikuOS. :)
"'"[…] This article explores the live migration steps #QEMU performs and how it tracks the information it needs to make the process transparent. It explains how QEMU coordinates with vhost-kernel […]. I will also explain how the guest can switch device properties, such as MAC address or number of active queues, and resume the workload seamlessly in the destination."'"
How am I able to setup a new #qemu Win10-VM in #NixOS?
aqemu which I was using for years is broken in NixOS since at least one major release. It doesn't even install when I allow broken packages for a nix-shell.
qt5-virt-manager doesn't seem to have a VM setup wizard.
#qtemu is not able to find the installed qemu-img to create a new virtual disk ("Ensure that you have installed qemu-img in your system and it's available").
"'"A vDPA device is a type of device that follows the virtio specification for its datapath but has a vendor-specific control path.
vDPA devices can be both physically located on the hardware or emulated by software.
[…]
Below are several examples on how to use VDUSE and the QEMU Storage Daemon with VMs (QEMU) or Containers (podman). These steps are easily adaptable […]
"'"