IOMMU GPU passthrough with device selection would be a helpful feature: https://www.google.com/search?q=gpu+passthrough+qemu

LXD manages qemu VMs and supports snapshotting, live migration, and a number of storage drivers: https://news.ycombinator.com/item?id=45270468

virtio-gpu-rutabaga works with Android VMs on qemu, but does it work with Win/Mac/Lin: https://news.ycombinator.com/item?id=42921315

Brilliant!

This may just become my next most favorite project on GitHub!

For anyone who would create their own OS, or just experiment with other OS'es, this could be a godsend!

The set of ideas which gives rise to this tool are brilliant, and while I haven't reviewed all of the code for potential security implications (as I would want to if I were deploying it to a production server in a business environment) -- it looks very well thought out at first glance!

Extra kudos for having a flake.nix (for us Nix users!)

(If you're using NixOS or the Nix package manager, you can download it here https://search.nixos.org/packages?channel=25.11&query=quicke... , i.e., "$ nix-shell -p quickemu")

And extra extra kudos for having Alpine, Nix, ReactOS, TinyCore and OpenBSD as downloadable OS choices!

In the future, I'd love to see Windows XP, Windows 2000, and Windows NT too (assuming that Microsoft would permit that!) -- but that would just be the icing on the cake!

Short review: There's potentially something for everyone here! (Well, any OS person! Could Minix 3 be added in the future? :-) )

Long review: Will definitely have to watch this project in the future, to see where it goes!

Related. Others?

Quickemu: Quickly run optimised Windows, macOS and Linux virtual machines - https://news.ycombinator.com/item?id=39188432 - Jan 2024 (133 comments)

I've been trying to do something similar to set up Windows VMs with developer tools. This would be awesome if there was a way to inject a `ps1` script where we could go through the awkwardness of installing choco and various dev tools.

For anyone interested, the magic incantation in the autoattend.xml is:

    <settings pass="specialize">
    <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
        <RunSynchronous>
        <RunSynchronousCommand wcm:action="add">
            <Order>1</Order>
            <Path>cmd /c powershell.exe -ExecutionPolicy Bypass -File A:\scripts\setup-dev.ps1 &gt; \\.\COM1</Path>
            <Description>Run dev setup script</Description>
        </RunSynchronousCommand>
        </RunSynchronous>
    </component>
    </settings>

Redirecting to COM1 is a fun hack I discovered that allows you to remotely monitor these from build scripts.

Even better would be figuring out how to slipstream the choco packages into the ISO - it's not super reliable to install these packages in my recent experience.

I thought that macOS was proprietary, and that apple only allowed it to be run on apple hardware. Just last month, I used incus to test a software package in 6 Linux distributions. I want to also test the package in macOS. Must I get a license from apple to do that with Quickemu?

Is this less buggy than UTM on apple silicon?

I have to try this. All my previous attempts to get to grips with qemu left me with the impression that it’s strictly for rocket scientists. This might ease the learning curve for me.

I'm a little confused as to why projects like this support macOS since at a minimum it's a TOS violation.

Doing stuff like this, and integrating it into the main project puts the whole thing at risk.

The only real reason to MacOS is it's tight integration with Mac hardware.

Weird flex...

This type of thing always makes me think about an alternate timeline where Docker never got popular because VM runtimes and tooling did everything Docker can do, better.

No support for aarch64 host? (Asahilinux)

No Windows binaries, even as qemu itself fully supports Windows hosts?

How does it differ from Vagrant ?

> quickget windows 10 Downloading Windows 10 (English International) - Parsing download page: https://www.microsoft.com/en-us/software-download/windows10I... - Getting Product edition ID: 2618 - Permit Session ID: ea2e2386-932a-44f2-b9b1-da7629b3d601 - Getting language SKU ID: 16068 - Getting ISO download link... - URL: https://software.download.prss.microsoft.com/dbazure/Win10_2... #################################### #################################################################################################### 100.0% Downloading VirtIO drivers... #################################################################################################### 100.0% Downloading Spice drivers... #################################################################################################### 100.0% #################################################################################################### 100.0% #################################################################################################### 100.0% Making unattended.iso Making windows-10.conf - Setting windows-10.conf executable

To start your Windows virtual machine run: quickemu --vm windows-10.conf

> quickemu --vm windows-10.conf ERROR! QEMU 6.0.0 or newer is required, detected 10.1.2.

Really useful tool, OSS for the win!!!

I'll keep it in mind but honestly learning the basics of QEMU is probably a safe bet. It's a bit like bash, you might like it or not but decades later it's still there, on most devices. Plenty of tools rely on it and getting the basics right is really a matter of following a 15min tutorial.

I feel the need for this as I went from raw dogging qemu commands to using virt-manager and its still not perfect.