Bliss OS is x86_64-only, so the e2e VM couldn't run on Apple Silicon at all: there is no hardware virt for x86 guests, and QEMU disables MTTCG for a strongly-ordered guest on a weakly-ordered host, so it would be single-threaded TCG regardless of -smp. Switch to LineageOS 23.2 packaged for upstream QEMU, which ships the same image for arm64 and x86_64. vm-config.sh now derives the qemu binary, machine, accel and cpu from VM_GUEST_ARCH (default: the host's, the only case that gets hardware acceleration) and locates UEFI firmware across Homebrew, Debian and Fedora layouts. The guest boots from disk over UEFI, so kernel/initrd/cmdline are gone. The VM is now ephemeral: run-vm.sh branches fresh qcow2 overlays off the pristine bases on every start, so guest state never persists and tests cannot leak into each other. Note efi_vars.fd is itself a sparse qcow2 whose virtual size matches the pflash unit, so it must be attached as qcow2 rather than raw.
EtchDroid
EtchDroid is an open-source application that helps you write images to USB drives.
Use it to make a bootable operating system USB drive when your laptop is dead.
Supported devices
- ✅ USB flash drives
- ✅ USB SD card adapters
- ❌ USB hard drives / SSDs
- ❌ USB docks and hubs
- ❌ Internal SD card slot
- ❌ Optical or floppy disk drives
- ❌ Thunderbolt-only devices
Supported disk image types
- ✅ Modern GNU/Linux operating system images, including Arch Linux, Ubuntu, Debian, Fedora, pop!_OS, Linux Mint, FreeBSD, BlissOS and many more
- ✅ Raspberry PI SD card images (but you must unzip them first!)
- ❌ Official Microsoft Windows ISOs from microsoft.com
- ⚠️ Community-built Windows images, made for EtchDroid (be careful: they may contain viruses!)
- ❌ Apple DMG disk images
- ❌ Older GNU/Linux OS images < 2010 such as Damn Small Linux
Support the project
If you want to say thanks, you can send a donation.
- Patreon: https://www.patreon.com/depau
- GitHub Sponsors: https://github.com/sponsors/depau
- One-time options on the website: https://etchdroid.app/donate/
Help out translating EtchDroid
Telemetry
Note
F-Droid builds do not include telemetry. Google Play and GitHub builds do.
EtchDroid Google Play and GitHub builds collect minimal telemetry to investigate app issues.
While we don't collect any personally-identifying information, we believe in transparency and want you to know that opened image file names and USB device IDs are collected anonymously to help diagnose issues with specific hardware. Unless your image file names or device IDs are highly sensitive, it's safe to share this data.
If you don't want to share this data, you can disable telemetry in the app menu, or download the F-Droid version of EtchDroid.
Be a part of our open-source community—keep telemetry enabled and help improve EtchDroid for everyone!
See the privacy policy for more information.






