Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
QEMU
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Integration== ===VirtualBox=== [[VirtualBox]], first released in January 2007, used some of QEMU's virtual hardware devices, and had a built-in [[Dynamic recompilation|dynamic re-compiler]] 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 re-compiler only as a fallback mechanism β for example, when guest code executes in [[real mode]].<ref name="LMJ9L3">{{cite web |title=VirtualBox Developer FAQ |url=http://virtualbox.org/wiki/Developer_FAQ |access-date=2015-02-02}}</ref> In addition, VirtualBox did a lot of code analysis and patching using a built-in disassembler to minimize recompilation. VirtualBox is free and open-source (available under [[GNU General Public License|GPL]]), except for certain features. ===Xen-HVM=== [[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 architecture|ARM]] [[ARM Cortex-A7|Cortex-A7]] and [[ARM Cortex-A15|Cortex-A15]] virtualization extensions.<ref name="ZfeJ33">{{cite web |title=Xen ARM with Virtualization Extensions |url=http://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions}}</ref> This means that instead of para-virtualized devices, a real set of virtual hardware is exposed to the DomU, enabling it to use real device drivers. 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.<ref name="Fu2I73">{{cite web |title=Oracle and Sun Microsystems - Strategic Acquisitions - Oracle |url=http://www.sun.com/blueprints/1107/820-3703.pdf |website=www.sun.com}}</ref> 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.<ref name="29Ixu3">[http://ian.blenke.com/xen/hvm/svm/vtx/qemu Demystifying Xen HVM] {{webarchive|url=https://web.archive.org/web/20071222101854/http://ian.blenke.com/xen/hvm/svm/vtx/qemu|date=December 22, 2007}}</ref> APIC support is provided by Xen. Xen-HVM utilizes device emulation based on the QEMU project to deliver I/O virtualization to virtual machines (VMs). Hardware is emulated through a QEMU "device model" daemon running as a backend in Dom0. Unlike other QEMU modes, such as dynamic translation or KVM, the hypervisor fully manages virtual CPUs, pausing them as necessary while QEMU handles memory-mapped I/O emulation. ===KVM=== [[Kernel-based Virtual Machine|KVM]] (Kernel-based Virtual Machine) is a FreeBSD and Linux kernel module that allows a [[user space]] program access to the [[Hardware-assisted virtualization|hardware virtualization]] features of various processors, with which QEMU can 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=== 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,<ref name="7MfDb3">[http://weblog.infoworld.com/virtualization/archives/2006/06/win4lin_announc.html win4lin VDS announcement] {{webarchive|url=https://web.archive.org/web/20080210042356/http://weblog.infoworld.com/virtualization/archives/2006/06/win4lin_announc.html|date=February 10, 2008}}</ref> 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 [https://web.archive.org/web/20110613051010/http://www.vbridges.com/home.php 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.<ref name="jGa1D3">[http://win4solaris.com/jml/index.php?option=com_content&task=view&id=17&Itemid=1 Win4Solaris announcement] {{webarchive|url=https://web.archive.org/web/20071223221725/http://win4solaris.com/jml/index.php?option=com_content&task=view&id=17&Itemid=1|date=December 23, 2007}}</ref> ===SerialICE=== 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 emulation|in-circuit emulators]] (ICE).<ref name="SEdrl3">{{Cite web |title=SerialICE |url=http://serialice.com/ |website=serialice.com}}</ref> ===WinUAE=== [[UAE (emulator)|WinUAE]] introduced support for the [[PowerUP (accelerator)|CyberStorm PPC and Blizzard 603e boards]] using the QEMU PPC core in version 3.0.0.<ref name="N2pRW3">{{cite web |date=2014-12-17 |title=WinUAE 3.0.0 |url=http://eab.abime.net/showpost.php?p=992271&postcount=1 |access-date=2016-03-25 |publisher=English Amiga Board}}</ref> ===Unicorn=== 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.<ref name="ggqXJ3">{{cite web |title=Unicorn & QEMU |url=https://www.unicorn-engine.org/docs/beyond_qemu.html |website=Unicorn Engine}}</ref> === Limbo x86 PC Emulator === Limbo is an x86 and [[ARM64]] QEMU-based virtual machine for Android.<ref>{{Cite web |title=Limbo Emulator Tutorials |url=https://virtualmachinery.weebly.com/tutorials.html |access-date=2023-09-02 |website=Virtual Machinery |language=en}}</ref> It is one of the few pieces of virtual machine software available for Android capable of emulating Microsoft Windows,<ref>{{Citation |title=How to Install Windows on any Android Device Full Installation [No Root] ( Using Limbo PC Emulator ) |url=https://www.youtube.com/watch?v=D6Vz3plWktQ |access-date=2023-09-02 |language=en}}</ref> 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.<ref>{{Cite web |title=India: mobile OS share 2022 |url=https://www.statista.com/statistics/262157/market-share-held-by-mobile-operating-systems-in-india/ |access-date=2023-09-02 |website=Statista |language=en}}</ref> 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 (file format)|APK]] (Android Package) installation.<ref>{{Cite web |title=Limbo Downloads |url=https://virtualmachinery.weebly.com/limbo-downloads.html |access-date=2023-09-02 |website=Virtual Machinery |language=en}}</ref> Limbo tends to have issues regarding its audio quality and playback. No fixes have been found for these problems as of 2024.<ref>{{Cite web |title=Downloads |url=https://github.com/limboemu/limbo/wiki/Downloads |access-date=2023-09-02 |website=GitHub |language=en}}</ref> Overall, Limbo is less well-known than other virtual machine software, which leads to less available information regarding its troubleshooting. It is required to install an 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.<ref>{{Citation |last=Weidner |first=Klaus |title=klausw/hackerskeyboard |date=2023-09-01 |url=https://github.com/klausw/hackerskeyboard |access-date=2023-09-02}}</ref> It is recommended to install Hacker's Keyboard with an APK file, as the Google Play version says it doesn't work with newer versions of Android.<ref>{{Cite web |title=Hacker's Keyboard - Apps on Google Play |url=https://play.google.com/store/apps/details?id=org.pocketworkstation.pckeyboard&hl=en_US |access-date=2023-09-02 |website=play.google.com |language=en-US}}</ref>{{Verify source|date=October 2024|reason=Could not find about APK files on the store page, is it collapsed somewhere?}}<!-- Updates are done to simplify. OLD: It is required to install an 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.[1] 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; for an APK file allows installing Hacker's Keyboard on newer versions of Android. -->
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)