From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomasz Chmielewski Subject: KVM paravirtualization on non-VMX/SVM CPUs? Date: Mon, 19 Mar 2007 17:37:21 +0100 Message-ID: <45FEBC41.6060802@wpkg.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Return-path: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org In January, Ingo Molnar announced "KVM paravirtualization for Linux"[1]. The announcement mentions "support for the hardware cr3-cache feature of Intel-VMX CPUs" and "i only tested this on 32-bit VMX". Because of this, I'm not sure how to understand it: 1) KVM paravirtualization means that it will be possible to use KVM on non-VMX/SVM CPUs (much like Xen)? 2) KVM paravirtualization means paravirtualized drivers only (net, disk etc.), but it will still run only on VMX/SVM-capable CPUs? Which one is true? First, or second? [1] http://people.redhat.com/mingo/kvm-paravirt-patches/ANNOUNCE -- Tomasz Chmielewski http://wpkg.org ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV