bin VS docker-qemu

I found this script to be a simple rather nice solution to the things that I missed from Vagrant. The QCOW2 image files are simply files kept in a single location, I can use the filesystem to manage these, and refer to them via the aforementioned environment variable. The ability to provision machines is done simply by copying the provision script and executing it to the machine once booted, and portforwarding is hacked ontop of that too. You can find this script here if you're interested in making use of it yourself.

qemu.org, wiki.qemu.org, patchew.org, kvm-forum.qemu.org are all Podman containers on the same machine (running CentOS Stream 9) with an nginx front-end. nginx and certbot are the only two things that run outside containers.

As someone who enjoys playing video games, and a recent convert to Linux, I was well aware of the derth of support for games. I was also aware of some of the solutions, one of those being GPU passthrough to this thing called QEMU. QEMU is a fast and lightweight machine emulator and virtualizer. This was of course something that interested me, so I went about exploring QEMU and playing with it. When I first started using it, I was offput by it. No slick UI to use, a myriad of flags to pass it, some flags which even took more options. But when I figured out the right incantation of flags to pass it, it worked, and I noticed its speed in comparison to VirtualBox.

install the windows-version using https://WineHQ.org or put in an a VM, like https://qemu.org/

for context I am modifying https://github.com/gnh1201/docker-qemu/wiki/Windows-Guest because combining the files into one iso has proved fruitless as it breaks booting the disk image.

You can do it the same way you run Linux containers on Windows. https://github.com/gnh1201/docker-qemu/wiki/Windows-Guest