From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: KVM Port Date: Thu, 26 Mar 2009 12:46:25 +0200 Message-ID: <49CB5D01.3050005@redhat.com> References: <0A1FE637C2C7E148B9573BB60CC630E519272E@zch01exm26.fsl.freescale.net> <0A1FE637C2C7E148B9573BB60CC630E51927BD@zch01exm26.fsl.freescale.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Liu Yu-B13201 , kvm@vger.kernel.org, kvm-ppc@vger.kernel.org To: kvm port Return-path: Received: from mx2.redhat.com ([66.187.237.31]:57225 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751617AbZCZKqc (ORCPT ); Thu, 26 Mar 2009 06:46:32 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: 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