From mboxrd@z Thu Jan  1 00:00:00 1970
From: Sasha Levin <levinsasha928@gmail.com>
Subject: Re: [PATCH 1/2] KVM: VMX: Notify if VMX is already in use
Date: Wed, 07 Dec 2011 16:18:41 +0200
Message-ID: <1323267521.4009.11.camel@lappy>
References: <1322764218-4698-1-git-send-email-levinsasha928@gmail.com>
	 <4EDF7590.5060701@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Cc: linux-kernel@vger.kernel.org, Joerg Roedel <joerg.roedel@amd.com>,
	Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
To: Avi Kivity <avi@redhat.com>
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <4EDF7590.5060701@redhat.com>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org

On Wed, 2011-12-07 at 16:17 +0200, Avi Kivity wrote:
> On 12/01/2011 08:30 PM, Sasha Levin wrote:
> > Currently we silently fail if VMX is already in use by a different
> > virtualization technology.
> >
> > This is bad since it's non-obvious for the user, and its not too uncommon
> > for users to have several of these installed on same host.
> >
> > This patch adds a message to notify the user of the problem.
> >
> 
> Does this actually happen?  With which hypervisor?

vbox

It turns VMX/SVM on when it loads, regardless of whether it's running a
guest or not.

-- 

Sasha.