public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: kvm port <kvmport@gmail.com>
Cc: Liu Yu-B13201 <Yu.Liu@freescale.com>,
	kvm@vger.kernel.org, kvm-ppc@vger.kernel.org
Subject: Re: KVM Port
Date: Thu, 26 Mar 2009 12:46:25 +0200	[thread overview]
Message-ID: <49CB5D01.3050005@redhat.com> (raw)
In-Reply-To: <cc73a6140903260321j40d2589eh1f30132e1ffe89c9@mail.gmail.com>

kvm port wrote:
> AFAIK KVM userspace app creates a VM using /dev/kvm. Now if IO has a
> MMU managed by KVM arch module, do i still need qemu?
>
>   

qemu is needed to allocate memory, and to emulate devices.  For example 
the IDE disk controller is implemented in qemu.


-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2009-03-26 10:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25 15:08 KVM Port kvm port
     [not found] ` <cc73a6140903250808n4919e74vb93b3e286fac3614-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-03-25 16:15   ` Avi Kivity
2009-03-25 16:45     ` kvm port
     [not found]       ` <cc73a6140903250945ob58312agb73538d7b54b24b7-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-03-25 16:45         ` kvm port
2009-03-26  1:52   ` Liu Yu-B13201
2009-03-26  6:03     ` kvm port
     [not found]       ` <cc73a6140903252303r4048d6c7p78149cdc91e2b991-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-03-26  6:33         ` Liu Yu-B13201
     [not found]           ` <0A1FE637C2C7E148B9573BB60CC630E51927BD-bKEhWGtIRUJ4Lp7cDGe+DVjVikpgYyvb5NbjCUgZEJk@public.gmane.org>
2009-03-26 10:21             ` kvm port
2009-03-26 10:46               ` Avi Kivity [this message]
     [not found]                 ` <49CB5D01.3050005-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-04-04 18:41                   ` kvm port
2009-04-06 16:51                     ` Hollis Blanchard

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=49CB5D01.3050005@redhat.com \
    --to=avi@redhat.com \
    --cc=Yu.Liu@freescale.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=kvmport@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox