Check your idea: does it exist already?
Describe what you are building or planning. Amigadex compares it with every indexed project by meaning, not only by words, and shows the closest ones, so you can join, fork or coordinate before duplicating work.
15+ projects about “qemu”
A few words find the projects about them. Describe your idea in a sentence or two to compare it by meaning: what it does, for which system, how.
Sort: closest · recently active · most stars · newest
-
Automated QEMU lifecycle + build + deploy + run for AmigaOS 4 development
-
QEMU fork hosting AmigaOS 4 on Windows - AmigaOne X5000 (P5020) machine. BETA.
-
Qemu cutom with more options, for Retro programming, target 68k, ppc, x86, MacOS 7.1 to 9.2.2, Atari, HaiKUOS, Amiga
-
A living computer museum: 90+ vintage and exotic operating systems from 1970 to today, running live on one Proxmox host and streamed interactively to your browser.
-
BBoot boot loader for AmigaOS on QEMU (fork of codeberg.org/qmiga/bboot) with SAM460ex support
-
Linux kernels for X1000 and e5500 (X5000/20, X5000/40, Mirari, and QEMU VMs) PowerPC computers
-
Intel e1000 (82540EM) SANA-II network device driver for AmigaOS 4.1 PPC on QEMU sam460ex — a modern replacement for the stock rtl8139.device, with proper DMA descriptor rings and IRQ moderation via the OS4 PCI SPI....
-
Clean-room reimplementation of the Pegasos II PowerPC firmware. v0.5: boots AmigaOS 4 in QEMU. Real-hardware validation pending.
-
These are some scripts that help run AmigaOS 4 and MorphOS on Qemu
-
VirtIO SCSI device driver for AmigaOS4.1FE
-
VirtIO GPU driver (virtiogpu.chip) for AmigaOS 4.1 on QEMU Pegasos2
-
virtio-net-pci SANA-II network driver for AmigaOS 4.1 on QEMU sam460ex — the first virtio-net driver for OS4. Guest-native ring endianness, no descriptor-format archaeology, no PCI cache-flush ceremony. Working...
-
VirtIO 9P filesystem handler for AmigaOS 4.1 — mounts QEMU host-shared folders as DOS volumes via 9P2000.L protocol
-
MCP server for driving AmigaOS 4.1 machines (QEMU + real hardware) via Model Context Protocol