Jump to content

QEMU

From Wikipedia, the free encyclopedia
This article is about the virtual machine monitor. For the Quarterdeck expanded memory manager, see QEMM.
QEMU
Original author(s)Fabrice Bellard
Developer(s)QEMU team:
Peter Maydell, et al.
Stable release
9.1.1[1] Edit this on Wikidata / 21 October 2024
Repository
Written inC
Operating systemLinux, Microsoft Windows, macOS and some other UNIX platforms
TypeHypervisor, Emulator
LicenseGPL-2.0-only[2]
Websitewww.qemu.org Edit this on Wikidata

QEMU (Quick Emulator)[3] is a free and open-source emulator that uses dynamic binary translation to emulate the processor of a computer. It provides a variety of hardware and device models for the machine, enabling it to run different guest operating systems. QEMU can be used in conjunction with Kernel-based Virtual Machine (KVM) to execute virtual machines at near-native speeds. Additionally, QEMU supports the emulation of user-level processes, allowing applications compiled for one processor architecture to run on another.[4]

QEMU supports the emulation of various processor architectures, including x86, ARM, PowerPC, RISC-V, and others.

Licensing

[edit]

QEMU was developed by Fabrice Bellard and is free software. Its different components are licensed under the GNU General Public License (GPL), BSD license, GNU Lesser General Public License (LGPL), or other GPL-compatible licenses.[5]

Operating modes

[edit]

QEMU has multiple operating modes:[6]

  • User-mode emulation. In the user emulation mode, QEMU runs single Linux or Darwin/macOS programs that were compiled for a different instruction set. System calls are thunked for endianness and for 32/64 bit mismatches. Fast cross-compilation and cross-debugging are the main targets for user-mode emulation.
  • System emulation. In the system emulation mode, QEMU emulates a full computer system, including peripherals. It can be used to provide virtual hosting of several virtual computers on a single computer. QEMU can boot many guest operating systems, including Linux, Solaris, Microsoft Windows, DOS, and BSD;[7] it supports emulating several instruction sets, including x86, MIPS, 32-bit ARMv7, ARMv8, PowerPC, RISC-V, SPARC, ETRAX CRIS and MicroBlaze.
  • Hypervisor support. In the hypervisor support mode, QEMU either acts as a Virtual Machine Manager (VMM) or as a device emulation back-end for virtual machines running under a hypervisor. The most common is Linux's KVM but the project supports a number of hypervisors including Xen, Apple's HVF, Windows' WHPX and NetBSD's nvmm.[8]

Features

[edit]

QEMU can save and restore the state of the virtual machine while all programs are running. Guest operating systems do not need patching in order to run inside QEMU.

QEMU supports the emulation of various architectures, including x86, MIPS64 (up to Release 6),[9] SPARC (sun4m and sun4u), ARM (Integrator/CP and Versatile/PB), SuperH, PowerPC (PReP and Power Macintosh), ETRAX CRIS, MicroBlaze, and RISC-V.

The virtual machine can interface with many types of physical host hardware, including the user's hard disks, CD-ROM drives, network cards, audio interfaces, and USB devices. USB devices can be completely emulated, or the host's USB devices can be used, although this requires administrator privileges and does not work with some devices.

Virtual disk images can be stored in a special format (qcow or qcow2) that only takes up as much disk space as the guest OS actually uses. This way, an emulated 120 GB disk may occupy only a few hundred megabytes on the host. The QCOW2 format also allows the creation of overlay images that record the difference from another (unmodified) base image file. This provides the possibility of reverting the emulated disk's contents to an earlier state. For example, a base image could hold a fresh install of an operating system that is known to work, and the overlay images are used. Should the guest system become unusable (through virus attack, accidental system destruction, etc.), the user can delete the overlay and use an earlier emulated disk image.

QEMU can emulate network cards (of different models) which share the host system's connectivity by translating network addresses, effectively allowing the guest to use the same network as the host. The virtual network cards can also connect to network cards of other instances of QEMU or to local TAP interfaces. Network connectivity can also be achieved by bridging a TUN/TAP interface used by QEMU with a non-virtual Ethernet interface on the host OS using the host OS's bridging features.

QEMU integrates several services to allow the host and guest systems to communicate; for example, an integrated SMB server and network-port redirection (to allow incoming connections to the virtual machine). It can also boot Linux kernels without a bootloader.

QEMU does not depend on the presence of graphical output methods on the host system. Instead, it can allow one to access the guest OS screen via an integrated VNC server. It can also use an emulated serial line, without any screen, with applicable operating systems.

Simulating multiple CPUs running SMP is possible.

QEMU does not require administrative rights to run unless additional kernel modules are used to improve speed (like KQEMU) or certain modes of its network connectivity model are utilized.

Tiny Code Generator

[edit]

The Tiny Code Generator (TCG) aims to remove the shortcoming of relying on a particular version of GCC or any compiler, instead incorporating the compiler (code generator) into other tasks performed by QEMU at run time. The whole translation task thus consists of two parts: basic blocks of target code (TBs) being rewritten in TCG ops – a kind of machine-independent intermediate notation, and subsequently this notation being compiled for the host's architecture by TCG. Optional optimization passes are performed between them, for a just-in-time compiler (JIT) mode.

TCG requires dedicated code written to support every architecture it runs on, so that the JIT knows what to translate the TCG ops to. If no dedicated JIT code is available for the architecture, TCG falls back to a slow interpreter mode called TCG Interpreter (TCI). It also requires updating the target code to use TCG ops instead of the old dyngen ops.

Starting with QEMU Version 0.10.0, TCG ships with the QEMU stable release. It replaces the dyngen, which relied on GCC 3.x to work.[10][11]

Accelerator

[edit]

KQEMU was a Linux kernel module, also written by Fabrice Bellard, which notably sped up emulation of x86 or x86-64 guests on platforms with the same CPU architecture. This worked by running user mode code (and optionally some kernel code) directly on the host computer's CPU, and by using processor and peripheral emulation only for kernel-mode and real-mode code. KQEMU could execute code from many guest OSes even if the host CPU did not support hardware-assisted virtualization. KQEMU was initially a closed-source product available free of charge, but starting from version 1.3.0pre10 (February 2007),[12] it was relicensed under the GNU General Public License. QEMU versions starting with 0.12.0 (as of August 2009) support large memory which makes them incompatible with KQEMU.[13] Newer releases of QEMU have completely removed support for KQEMU.

QVM86 was a GNU GPLv2 licensed drop-in replacement for the then closed-source KQEMU. The developers of QVM86 ceased development in January 2007.

Kernel-based Virtual Machine (KVM) has mostly taken over as the Linux-based hardware-assisted virtualization solution for use with QEMU in the wake of the lack of support for KQEMU and QVM86.[citation needed] QEMU can also use KVM on other architectures like ARM and MIPS.[14]

Intel's Hardware Accelerated Execution Manager (HAXM) is an open-source alternative[15] to KVM for x86-based hardware-assisted virtualization on NetBSD, Linux, Windows and macOS using Intel VT. As of 2013 Intel mostly solicits its use with QEMU for Android development.[16] Starting with version 2.9.0, the official QEMU includes support for HAXM, under the name hax.[17]

QEMU also supports the following accelerators:[17]

  • hvf, Apple's Hypervisor.framework based on Intel VT.
  • whpx, Microsoft's Windows Hypervisor Platform based on Intel VT or AMD-V.
  • tcg, QEMU's own Tiny Code Generator. This is the default.

Supported disk image formats

[edit]

QEMU supports the following disk image formats:[18]

QEMU Object Model

[edit]

The QEMU Object Model (QOM) provides a framework for registering user creatable types and instantiating objects from those types.[20]

QOM provides the following features:

  • System for dynamically registering types
  • Support for single-inheritance of types
  • Multiple inheritance of stateless interfaces
See also: Object model

Parallel emulation

[edit]

Virtualization solutions that use QEMU can execute multiple virtual CPUs in parallel. For user-mode emulation, QEMU maps emulated threads to host threads. For full system emulation, QEMU is capable of running a host thread for each emulated virtual CPU (vCPU). This is dependent on the guest having been updated to support parallel system emulation, currently ARM, Alpha, HP-PA, PowerPC, RISC-V, s390x, x86 and Xtensa. Otherwise, a single thread is used to emulate all virtual CPUs (vCPUS) which executes each vCPU in a round-robin manner.

Integration

[edit]

VirtualBox

[edit]

VirtualBox, first released in January 2007, used some of QEMU's virtual hardware devices, and had a built-in dynamic recompiler based on QEMU. As with KQEMU, VirtualBox runs nearly all guest code natively on the host via the VMM (Virtual Machine Manager) and uses the recompiler only as a fallback mechanism – for example, when guest code executes in real mode.[21] In addition, VirtualBox did a lot of code analysis and patching using a built-in disassembler in order to minimize recompilation. VirtualBox is free and open-source (available under GPL), except for certain features.

Xen-HVM

[edit]

Xen, a virtual machine monitor, can run in HVM (hardware virtual machine) mode, using Intel VT-x or AMD-V hardware x86 virtualization extensions and ARM Cortex-A7 and Cortex-A15 virtualization extensions.[22] This means that instead of paravirtualized devices, a real set of virtual hardware is exposed to the domU to use real device drivers to talk to.

QEMU includes several components: CPU emulators, emulated devices, generic devices, machine descriptions, user interface, and a debugger. The emulated devices and generic devices in QEMU make up its device models for I/O virtualization.[23] They comprise a PIIX3 IDE (with some rudimentary PIIX4 capabilities), Cirrus Logic or plain VGA emulated video, RTL8139 or E1000 network emulation, and ACPI support.[24] APIC support is provided by Xen.

Xen-HVM has device emulation based on the QEMU project to provide I/O virtualization to the VMs. Hardware is emulated via a QEMU "device model" daemon running as a backend in dom0. Unlike other QEMU running modes (dynamic translation or KVM), virtual CPUs are completely managed to the hypervisor, which takes care of stopping them while QEMU is emulating memory-mapped I/O accesses.

KVM

[edit]

KVM (Kernel-based Virtual Machine) is a FreeBSD and Linux kernel module that allows a user space program access to the hardware virtualization features of various processors, with which QEMU is able to offer virtualization for x86, PowerPC, and S/390 guests. When the target architecture is the same as the host architecture, QEMU can make use of KVM particular features, such as acceleration.

Win4Lin Pro Desktop

[edit]

In early 2005, Win4Lin introduced Win4Lin Pro Desktop, based on a 'tuned' version of QEMU and KQEMU and it hosts NT-versions of Windows. In June 2006,[25] Win4Lin released Win4Lin Virtual Desktop Server based on the same code base. Win4Lin Virtual Desktop Server serves Microsoft Windows sessions to thin clients from a Linux server.

In September 2006, Win4Lin announced a change of the company name to Virtual Bridges with the release of Win4BSD Pro Desktop, a port of the product to FreeBSD and PC-BSD. Solaris support followed in May 2007 with the release of Win4Solaris Pro Desktop and Win4Solaris Virtual Desktop Server.[26]

SerialICE

[edit]

SerialICE is a QEMU-based firmware debugging tool running system firmware inside of QEMU while accessing real hardware through a serial connection to a host system. This can be used as a cheap replacement for hardware in-circuit emulators (ICE).[27]

WinUAE

[edit]

WinUAE introduced support for the CyberStorm PPC and Blizzard 603e boards using the QEMU PPC core in version 3.0.0.[28]

Unicorn

[edit]

Unicorn is a CPU emulation framework based on QEMU's "TCG" CPU emulator. Unlike QEMU, Unicorn focuses on the CPU only: no emulation of any peripherals is provided and raw binary code (outside of the context of an executable file or a system image) can be run directly. Unicorn is thread-safe and has multiple bindings and instrumentation interfaces.[29]

Limbo X86 PC Emulator

[edit]

Limbo is an X86 and ARM64 virtual machine for Android based on QEMU[30] It is one of the few pieces of virtual machine software available for Android capable of emulating Microsoft Windows,[31] although it was designed to emulate Linux and DOS. Unlike other QEMU-based emulators, it does not require users to type commands to use, instead having a user interface to set the virtual machine's settings.

It is more popular in developing countries in Asia such as India, Malaysia, and Thailand on YouTube due to the high usage of the Android Operating System.[32] Limbo was removed from the Google Play Store for unknown reasons between February 2019 and December 2020, though it can still be installed off the developer's website with an APK (Android Package) installation.[33] Limbo is known for having stepped, glitchy and laggy audio quality, and no known fixes have been found as of 2023.[34] Limbo is generally unknown in popularity compared to other virtual machine software, making troubleshooting very difficult.

It is required to install a special application known as "Hacker's Keyboard" to use many keyboard functions that a basic Android keyboard cannot do in Limbo X86, such as the Ctrl, Alt, Del, and function keys.[35] It is recommended to install Hacker's Keyboard with an APK file due to the Google Play Store stating it does not support newer Android versions; an APK file allows installing Hacker's Keyboard on newer versions of Android.[36][verification needed]

Emulated hardware platforms

[edit]

x86

[edit]

QEMU can emulate i386 and x86_64 architecture. Besides the CPU (which is also configurable and can emulate a number of Intel CPU models including (as of 3 March 2018) Sandy Bridge,[37] Ivy Bridge,[38] Haswell,[39] Broadwell[40][41] and Skylake[39]), the following devices are emulated:

The BIOS implementation used by QEMU starting from version 0.12 is SeaBIOS. The VGA BIOS implementation of SeaBIOS is also used starting from version 2.0.0. The UEFI firmware for QEMU is OVMF.[45]

PowerPC

[edit]

PowerMac

[edit]

QEMU emulates the following PowerMac peripherals:

  • UniNorth PCI bridge
  • PCI-VGA-compatible graphics card which maps the VESA Bochs Extensions
  • Two PMAC-IDE-Interfaces with hard disk and CD-ROM support.
  • NE2000 PCI adapter
  • Non-volatile RAM
  • VIA-CUDA with ADB keyboard and mouse.

OpenBIOS is used as the firmware.

PREP

[edit]

QEMU emulates the following PREP peripherals:

  • PCI bridge
  • PCI VGA-compatible graphics card with VESA Bochs Extensions
  • Two IDE interfaces with hard disk and CD-ROM support
  • Floppy disk drive
  • NE2000 network adapter
  • Serial interface
  • PREP non-volatile RAM
  • PC-compatible keyboard and mouse

On the PREP target, Open Hack'Ware, an Open-Firmware-compatible BIOS, is used.

IBM System p

[edit]

QEMU can emulate the paravirtual sPAPR interface with the following peripherals:

  • PCI bridge, for access to virtio devices, VGA-compatible graphics, USB, etc.
  • Virtual I/O network adapter, SCSI controller, and serial interface
  • sPAPR non-volatile RAM

On the sPAPR target, another Open-Firmware-compatible BIOS is used, called SLOF.

ARM

[edit]

ARM32

[edit]
QEMU booted into the ARM port of Fedora 8

QEMU emulates the ARMv7 instruction set (and down to ARMv5TEJ) with NEON extension.[46] It emulates full systems like Integrator/CP board, Versatile baseboard, RealView Emulation baseboard, XScale-based PDAs, Palm Tungsten|E PDA, Nokia N800 and Nokia N810 Internet tablets, etc. QEMU also powers the Android emulator which is part of the Android SDK (most current Android implementations are ARM-based). Starting from version 2.0.0 of their Bada SDK, Samsung has chosen QEMU to help development on emulated 'Wave' devices.

In 1.5.0 and 1.6.0, Samsung Exynos 4210 (dual-core Cortex-A9) and Versatile Express ARM Cortex-A9 ARM Cortex-A15 are emulated. In 1.6.0, the 32-bit instructions of the ARMv8 (AArch64) architecture are emulated, but 64-bit instructions are unsupported.

The Xilinx Cortex A9-based Zynq SoC is modelled, with the following elements:

  • Zynq-7000 ARM Cortex-A9 CPU
  • Zynq-7000 ARM Cortex-A9 MPCore
  • Triple Timer Counter
  • DDR Memory Controller
  • DMA Controller (PL330)
  • Static Memory Controller (NAND/NOR Flash)
  • SD/SDIO Peripheral Controller (SDHCI)
  • Zynq Gigabit Ethernet Controller
  • USB Controller (EHCI – Host support only)
  • Zynq UART Controller
  • SPI and QSPI Controllers
  • I2C Controller

ARM64

[edit]

SPARC

[edit]

QEMU has support for both 32- and 64-bit SPARC architectures.

When the firmware in the JavaStation (sun4m-Architecture) became version 0.8.1 Proll,[47] a PROM replacement used in version 0.8.2, was replaced with OpenBIOS.

SPARC32

[edit]

QEMU emulates the following sun4m/sun4c/sun4d peripherals:

  • IOMMU or IO-UNITs
  • TCX Frame buffer (graphics card)
  • Lance (Am7990) Ethernet
  • Non-volatile RAM M48T02/M48T08
  • Slave I/O: timers, interrupt controllers, Zilog serial ports, keyboard and power/reset logic
  • ESP SCSI controller with hard disk and CD-ROM support
  • Floppy drive (not on SS-600MP)
  • CS4231 sound device (only on SS-5, not working yet)

SPARC64

[edit]

QEMU emulates Sun4u (UltraSPARC PC-like machine), Sun4v (T1 PC-like machine), or generic Niagara (T1) machine with the following peripherals:

  • UltraSparc IIi APB PCI Bridge
  • PCI VGA-compatible card with VESA Bochs Extensions
  • PS/2 mouse and keyboard
  • Non-volatile RAM M48T59
  • PC-compatible serial ports
  • 2 PCI IDE interfaces with hard disk and CD-ROM support
  • Floppy disk

MicroBlaze

[edit]

QEMU supports the following peripherals:

  • MicroBlaze with/without MMU, including[sentence fragment]
  • AXI Timer and Interrupt controller peripherals
  • AXI External Memory Controller
  • AXI DMA Controller
  • Xilinx AXI Ethernet
  • AXI Ethernet Lite
  • AXI UART 16650 and UARTLite
  • AXI SPI Controller

LatticeMico32

[edit]

Supported peripherals: From the Milkymist SoC

  • UART
  • VGA
  • Memory card
  • Ethernet
  • pfu
  • timer

CRIS

[edit]
Main article: ETRAX CRIS

OpenRISC

[edit]
Main article: OpenRISC

Others

[edit]

External trees exist, supporting the following targets:

See also

[edit]

References

[edit]
  1. ^ "[ANNOUNCE] QEMU 9.1.1 Stable released". 21 October 2024. Retrieved 21 October 2024.
  2. ^ "License - QEMU".
  3. ^ "Glossary". National Institute of Standards and Technology. Retrieved 2023-04-24.
  4. ^ Speed, Richard (2019-04-25). "QEMU 4 arrives with toys for Arm admirers, RISC-V revolutionaries, POWER patriots... you get the idea". www.theregister.co.uk. The Register. Archived from the original on 2019-10-01. Retrieved 2019-10-01.
  5. ^ "License - QEMU". wiki.qemu.org.
  6. ^ "About QEMU". qemu.readthedocs.io.
  7. ^ "QEMU OS Support List". www.claunia.com. Archived from the original on 2014-05-13. Retrieved 2024-03-21. Frequent changes recorded in archive in years before going offline.{{cite web}}: CS1 maint: postscript (link)
  8. ^ "Supported host architectures".
  9. ^ "QEMU PRIP 1 - support for MIPS64 Release 6 - PRPL". wiki.prplfoundation.org. Archived from the original on 2017-04-21. Retrieved 2014-12-22.
  10. ^ "[Qemu-devel] ANNOUNCE: Release 0.10.0 of QEMU". lists.gnu.org.
  11. ^ Filardo, Nathaniel (September 11, 2007). "Porting QEMU to Plan 9: QEMU Internals and Port Strategy" (PDF). gsoc.cat-v.org. -- a review of how the old dyngen worked
  12. ^ "KQEMU 1.3.0pre10 released - under the GPL [LWN.net]". Lwn.net. February 6, 2007. Retrieved 2009-01-03.
  13. ^ Liguori, Anthony (10 August 2009). "[Qemu-devel] [PATCH 1/2] Unbreak large mem support by removing kqemu". Retrieved 2010-03-11.
  14. ^ "QEMU / KVM CPU model configuration". QEMU 5.0.50 (v5.0.0-962-g49ee115552) documentation.
  15. ^ "HAXM goes open source". QEMU developers. 2017-11-17. Retrieved 2017-01-14. HAXM is now open source
  16. ^ "Intel Hardware Accelerated Execution Manager". Intel. 2013-11-27. Retrieved 2014-05-12. The Intel Hardware Accelerated Execution Manager (Intel® HAXM) is a hardware-assisted virtualization engine (hypervisor) that uses Intel Virtualization Technology (Intel® VT) to speed up Android app emulation on a host machine.
  17. ^ a b "Invocation". QEMU 5.0.50 (v5.0.0-962-g49ee115552) documentation.
  18. ^ "QEMU Emulator User Documentation". qemu.weilnetz.de. Archived from the original on 2019-04-27. Retrieved 2018-04-10.
  19. ^ "Booting from an ISO image using qemu". Linux Tips. 3 August 2015.
  20. ^ "Qemu Readme". GitHub. 26 October 2021.
  21. ^ "VirtualBox Developer FAQ". Retrieved 2015-02-02.
  22. ^ "Xen ARM with Virtualization Extensions".
  23. ^ "Oracle and Sun Microsystems - Strategic Acquisitions - Oracle" (PDF). www.sun.com.
  24. ^ Demystifying Xen HVM Archived December 22, 2007, at the Wayback Machine
  25. ^ win4lin VDS announcement Archived February 10, 2008, at the Wayback Machine
  26. ^ Win4Solaris announcement Archived December 23, 2007, at the Wayback Machine
  27. ^ "SerialICE". serialice.com.
  28. ^ "WinUAE 3.0.0". English Amiga Board. 2014-12-17. Retrieved 2016-03-25.
  29. ^ "Unicorn & QEMU". Unicorn Engine.
  30. ^ "Limbo Emulator Tutorials". Virtual Machinery. Retrieved 2023-09-02.
  31. ^ How to Install Windows on any Android Device Full Installation [No Root] ( Using Limbo PC Emulator ), retrieved 2023-09-02
  32. ^ "India: mobile OS share 2022". Statista. Retrieved 2023-09-02.
  33. ^ "Limbo Downloads". Virtual Machinery. Retrieved 2023-09-02.
  34. ^ "Downloads". GitHub. Retrieved 2023-09-02.
  35. ^ Weidner, Klaus (2023-09-01), klausw/hackerskeyboard, retrieved 2023-09-02
  36. ^ "Hacker's Keyboard - Apps on Google Play". play.google.com. Retrieved 2023-09-02.
  37. ^ "[Qemu-devel] [PATCH 3/3] add SandyBridge CPU model". lists.gnu.org.
  38. ^ "Qemu-Changelog-2.3 x86". wiki.qemu.org.
  39. ^ a b "QEMU-changelog-2.6, x86 KVM". wiki.qemu.org.
  40. ^ "QEMU-changelog-2.1, x86 KVM". wiki.qemu.org.
  41. ^ "QEMU-changelog-2.5, x86 CPU Models and Features". wiki.qemu.org.
  42. ^ https://qemu.weilnetz.de/doc/qemu-doc.html#pcsys_005fnetwork Archived 2019-04-27 at the Wayback Machine "i82551, i82557b, i82559er, ne2k_pci, ne2k_isa, pcnet, rtl8139, e1000, smc91c111, lance and mcf_fec"
  43. ^ http://pclosmag.com/html/issues/201208/page11.html Networking on QEMU: Setting Up The E1000 & Novell NE2000 ISA Evaluation
  44. ^ "ChangeLog/0.14". Retrieved 2011-08-08.
  45. ^ "UEFI/OVMF - Ubuntu Wiki".
  46. ^ "gitorious.org Git - rowboat: external-qemu.git/commit". gitorious.org.
  47. ^ "Zaitcev's Linux". 090427 people.redhat.com
  48. ^ "QEMU Z80 Target". Archived from the original on 2016-06-06. 090506 homepage.ntlworld.com
[edit]
Wikimedia Commons has media related to QEMU.
Wikibooks has more on the topic of: QEMU
Retrieved from "https://en.wikipedia.org/w/index.php?title=QEMU&oldid=1257864134"