[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4EDF76D6.7020800@redhat.com>
Date: Wed, 07 Dec 2011 16:23:18 +0200
From: Avi Kivity <avi@...hat.com>
To: Sasha Levin <levinsasha928@...il.com>
CC: linux-kernel@...r.kernel.org, Joerg Roedel <joerg.roedel@....com>,
Marcelo Tosatti <mtosatti@...hat.com>, kvm@...r.kernel.org
Subject: Re: [PATCH 1/2] KVM: VMX: Notify if VMX is already in use
On 12/07/2011 04:18 PM, Sasha Levin wrote:
> 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.
That's odd. IIRC when we discussed this with them, they were executing
VMXON/VMXOFF dynamically. Looks like they changed this.
Anyway, please adjust according to Joerg's comment (and add the word
"using"), and I'll apply.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists