From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joerg Roedel Subject: Re: VMX ideas Date: Wed, 29 Oct 2008 16:01:55 +0100 Message-ID: <20081029150154.GA20843@8bytes.org> References: <687FC948-DBF4-4A7C-AD14-F6DB53A092D6@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: KVM list To: Alexander Graf Return-path: Received: from 8bytes.org ([88.198.83.132]:41862 "EHLO 8bytes.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753925AbYJ2PB4 (ORCPT ); Wed, 29 Oct 2008 11:01:56 -0400 Content-Disposition: inline In-Reply-To: <687FC948-DBF4-4A7C-AD14-F6DB53A092D6@suse.de> Sender: kvm-owner@vger.kernel.org List-ID: On Wed, Oct 29, 2008 at 03:52:21PM +0100, Alexander Graf wrote: > Hi list, > > I really do like KVM and would love to make using it a complete no- > brainer user experience. For the average user, loading a kernel module > (and unloading it) isn't really one of the most common tasks. > > So I was considering to automatically load kvm-intel and kvm-amd on > bootup, when the CPU has a CPUID flag. Unfortunately it doesn't work > that easily. VMX enters Root mode, setting a page to use for the VMCS. > KVM sets up this page when the kvm-intel module gets loaded. This > means, as soon as kvm-intel is modprobe'd, vmware, virtual box, > parallels and the like are screwed. > From a distribution perspective, this isn't exactly an ideal situation. > > So I was thinking hard on what to do to circumvent this problem and > came up with several approaches: If you want to allow parallel execution of different hypervisors at the same time you have a similar problem with SVM because you don't know which hypervisor uses which ASID. Joerg