From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joanna Rutkowska Subject: Re: A few KVM security questions Date: Mon, 07 Dec 2009 15:06:54 +0100 Message-ID: <4B1D0BFE.60202@invisiblethingslab.com> References: <4B1CFD93.7090307@invisiblethingslab.com> <4B1D0057.8030707@redhat.com> <4B1D0383.1080306@invisiblethingslab.com> <4B1D0544.9000603@redhat.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig519577AB861A062FAAE0BBA7" Cc: kvm@vger.kernel.org To: Avi Kivity Return-path: Received: from out1.smtp.messagingengine.com ([66.111.4.25]:51583 "EHLO out1.smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935066AbZLGOGu (ORCPT ); Mon, 7 Dec 2009 09:06:50 -0500 In-Reply-To: <4B1D0544.9000603@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig519577AB861A062FAAE0BBA7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Avi Kivity wrote: > On 12/07/2009 03:30 PM, Joanna Rutkowska wrote: >> Avi Kivity wrote: >> >> =20 >>>> 1) Do you have any support for para-virtualized VMs? >>>> =20 >>> Yes, for example, we support paravirtualized timers and mmu for Linux= =2E >>> These are fairly minimal compared to Xen's pv domains. >>> >>> =20 >> Can I run a regular Linux as PV-guest? Specifically, can I get rid of >> qemu totally, assuming I have only PV guests? >> >> =20 >=20 > No. Paravirtualization just augments the standard hardware interface, > it doesn't replace it as in Xen. >=20 Can you point to a document/source file that would list all the possible interfaces between VM and the host? I.e. all the VMX handlers, and all the hypercalls (PV interfaces). joanna. --------------enig519577AB861A062FAAE0BBA7 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAksdC/4ACgkQORdkotfEW86XqgCg3GWXN1e5ck3CkhHZ0kSr5wmo pnUAoI+DBgVVsTVAGWxX00PFmbdbCEVn =5rzz -----END PGP SIGNATURE----- --------------enig519577AB861A062FAAE0BBA7--