From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: gerryw-dHy0zPTSVEVBDgjK7y7TUQ@public.gmane.org
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: QEMU vs KVM
Date: Wed, 12 Sep 2007 12:04:33 +0300 [thread overview]
Message-ID: <46E7ABA1.5060107@qumranet.com> (raw)
In-Reply-To: <OF3A65175E.144A21B6-ON86257354.0014DBC7-86257354.0015941E-Ojamyiewz+ICx7yrEBmKXg@public.gmane.org>
gerryw-dHy0zPTSVEVBDgjK7y7TUQ@public.gmane.org wrote:
>
> Hello All,
>
> I am a bit unclear about the differences between QEMU and KVM. If I
> understand correctly, QEMU can run in a mode on an x86 where it
> executes user space code directly on the cpu without emulation. This
> seems to be very similar to what KVM is doing with the exception of
> using the virtualization capability of the cpu. I would think there
> would be very little difference in performance between the two in this
> case. Please forgive my ignorance, because I don't know that much
> about the new VT cpus yet. What is the actual difference / objective
> of the KVM project?
You're describing kqemu, not qemu.
Qemu is an emulator; it can emualte a large number of guests on a large
number of hosts, albeit at fairly slow speeds.
kqemu is a "qemu accelerator" which can be used to speed up qemu
emulation if the guest and host are the same.
kvm is a hardware virtualization system that is part of the Linux
kernel. While at present the only serious user is a modified qemu, it
is not tied to qemu. It is faster than either qemu of kqemu. The
downside is that it requires hardware virtualization extensions for
fully virtualized guests.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2007-09-12 9:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-12 3:55 QEMU vs KVM gerryw-dHy0zPTSVEVBDgjK7y7TUQ
[not found] ` <OF3A65175E.144A21B6-ON86257354.0014DBC7-86257354.0015941E-Ojamyiewz+ICx7yrEBmKXg@public.gmane.org>
2007-09-12 9:04 ` Avi Kivity [this message]
[not found] ` <46E7ABA1.5060107-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-12 9:40 ` gerryw-dHy0zPTSVEVBDgjK7y7TUQ
[not found] ` <OF72F0C452.CAF51B52-ON86257354.0033603F-86257354.00368EF4-Ojamyiewz+ICx7yrEBmKXg@public.gmane.org>
2007-09-12 9:43 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46E7ABA1.5060107@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=gerryw-dHy0zPTSVEVBDgjK7y7TUQ@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.