anylaysys/qemu-geniezone

★ 14CAudience · developerComplexity · 4/5LicenseSetup · hard

Mindmap

mindmap
  root((qemu-geniezone))
    What it does
      QEMU fork
      GenieZone Hypervisor support
      MediaTek emulation
    Base project
      QEMU open source
      ARM emulation
      Virtual machine host
    Build
      make.sh script
      C source code
      GPL v2 license
    Audience
      Embedded developers
      MediaTek chip devs
      Hypervisor testers

mindmap root((qemu-geniezone)) What it does QEMU fork GenieZone Hypervisor support MediaTek emulation Base project QEMU open source ARM emulation Virtual machine host Build make.sh script C source code GPL v2 license Audience Embedded developers MediaTek chip devs Hypervisor testers

Click or tap to explore — scroll the page freely

Things people build with this

USE CASE 1

Test MediaTek GenieZone hypervisor software on a standard laptop without owning physical MediaTek hardware

USE CASE 2

Emulate an ARM-based MediaTek environment to develop and debug drivers or virtual machine software

USE CASE 3

Use as a starting point for further QEMU patches targeting MediaTek or other custom hypervisor integrations

Tech stack

CQEMUMakeShell

Getting it running

Difficulty · hard Time to first run · 1day+

Requires a full C build toolchain, run make.sh to compile. Documentation of the GenieZone-specific changes is minimal and requires reading the source code directly.

GNU General Public License version 2, you can use, modify, and distribute this software freely, but any modified version you distribute must also be released under GPL v2.

In plain English

QEMU is an open-source tool that lets one computer run software written for a completely different type of machine, all in software with no special hardware required. For example, it can simulate an ARM-based board on a standard x86 laptop, or run an entire operating system inside a virtual window on your desktop. It does this by translating instructions on the fly, which allows it to reach reasonable speeds even without chip-level virtualization support. This repository is a customized fork of QEMU, modified by AnyLaySys to add support for MediaTek's GenieZone Hypervisor. A hypervisor is software that creates and manages virtual machines, which are isolated software environments that behave like separate physical computers. GenieZone is MediaTek's own hypervisor technology, and this fork patches QEMU so that GenieZone can run inside a QEMU emulation environment. The intended audience is developers who need to test or develop software targeting MediaTek chips without access to the physical hardware. Building this version is slightly simpler than standard QEMU: after cloning the repository, you run a shell script called make.sh to compile everything. No other custom setup is documented beyond that single step. Beyond the build change, the README is largely the standard QEMU documentation, covering how to file bug reports, submit patches, and contact the broader QEMU developer community. The project inherits the same GNU General Public License version 2 as upstream QEMU. The repository has only 14 stars and the README provides little detail about how GenieZone support was actually implemented or what was changed from the base QEMU code. Developers interested in the GenieZone integration would need to read the code directly rather than relying on any written explanation.

Copy-paste prompts

Prompt 1

I cloned qemu-geniezone. Walk me through running make.sh to build it and then launching a basic ARM virtual machine to verify the emulator works.

Prompt 2

What changes does qemu-geniezone add on top of standard QEMU to support the MediaTek GenieZone Hypervisor? I want to understand the diff at a high level before reading the C code.

Prompt 3

I want to run a GenieZone-aware Linux kernel image inside qemu-geniezone. What QEMU command-line flags and machine type should I use for a MediaTek target?

Prompt 4

How do I set up a development workflow with qemu-geniezone where I can quickly rebuild after changing C source files and relaunch the emulator?

Open on GitHub → Explain another repo

← anylaysys on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.