When the accelerator is activated, the QEMU emulator simply examines the code to verify that it can be executed natively,
and dispatches it to the accelerator. The code runs at full speed until the next exception, interrupt, or virtual device access;
QEMU then steps in and provides the service needed to maintain the virtual environment. One note: The Accelerator module is
closed-source. It’s still free and can be used in a commercial application, but you need permission to redistribute it.

QEMU Version 1.3.0
QEMU, qemu.com
|
Very Good 8.5 |
 |
| criteria |
score |
weight |
| Performance |
8 |
20% |
 |
| Scalability |
9 |
20% |
 |
| Setup |
9 |
20% |
 |
| Documentation |
6 |
15% |
 |
| Ease-of-use |
9 |
15% |
 |
| Value |
10 |
10% |
 |
|
 |
Cost: Open source
Platforms: Windows XP, 2000, and 2003 Server; Linux; MacOS
Bottom Line: Technically a simulator, QEMU nonetheless has virtualization capabilities that allow it to run Linux on Windows (or vice versa).
It can also run code from one CPU on a system with a different physical CPU, so an x86 Windows system can execute a virtualized
Sparc-based Solaris image. QEMU is slower than commercial virtualizers, but it's lightweight nature and platform support compensate
for performance.
|
 |
About our Reviews and Scoring Methodology
|
|
|
|
Virtual Comparisons
There are so many attractive aspects to QEMU, it’s hard to know where to start. For example, on Linux, running it in “user-mode
emulation” allows you to execute a Linux app written for a CPU other than the one running in your host system. QEMU intercepts
calls to the Linux kernel (from the guest app), and manages the marshalling of data in both directions. Consequently, even
if the endianness of the host is different from that of the guest, QEMU will take care of it.
I was also smitten by the wealth of command-line options available. For example, you can configure the guest environment to
recognize up to two virtual floppies and four virtual hard drives. If you want to protect the content of any of your virtual
drives from being overwritten, you can start QEMU in “snapshot” mode, which diverts all write operations to a temporary directory.
Even better, if you later decide you want to commit those write operations, you can do so through the QEMU monitor. You can
adjust the guest OS’s memory, turn sound hardware on and off, enable and disable USB drives, and on, and on. If that’s not
enough, QEMU can also emulate an SMP system. I wasn’t able to test this, but the documentation claims that you can simulate
up to 255 virtual processors.
To get an idea of how well QEMU performs next to VMware, I used Puppy Linux, a small-footprint Linux distribution. The Puppy Linux image takes less that 100MB and fits easily on a USB pendrive; nevertheless,
it includes a remarkable array of applications. I downloaded a QEMU-enabled version of Puppy Linux and VMware. Both were the same Linux release, and I adjusted the VMware version so both had 256 MB available.
For my test, I downloaded a moderately large JPEG file from the www.photo.net site and performed a blur operation in the mtPaint
application provided with Puppy Linux. On my 1GHz Dell system, the VMware version ran approximately 10 percent faster than
the QEMU version. Note that this was a comparison of raw processor execution; I imagine that applications that make heavy
use of virtualized hardware (such as an RDBMS performing a lot of seek operations) would produce a wider gap, with VMware
outperforming QEMU even more.
At this point, QEMU will be most attractive to a small or midsize software development organization that needs to create a
testbed of various OS flavors, and has decided that QEMU’s zero cost overwhelms its performance shortcomings. QEMU’s performance
can’t compete with commercial virtualizers; at least, not yet.
Even so, with the capabilities it has -- its ability to run in multiple systems; the ease with which new virtual machines
can be created; the performance enhancement of the Windows accelerator -- QEMU can hold its head high next to even the likes
of VMware.