linux-kernel - Re: [PATCH 1/2] KVM: VMX: Notify if VMX is already in use

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1323268930.4009.19.camel@lappy>
Date:	Wed, 07 Dec 2011 16:42:10 +0200
From:	Sasha Levin <levinsasha928@...il.com>
To:	Avi Kivity <avi@...hat.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 Wed, 2011-12-07 at 16:26 +0200, Avi Kivity wrote:
> On 12/07/2011 04:24 PM, Sasha Levin wrote:
> > > 
> > > 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.
> >
> > I've seen it the day before I've sent those patches. vbox driver loaded,
> > kvm silently failed and rdmsr showed SVME turned on.
> >
> > Will resend.
> 
> Ah, maybe they do it differently on AMD.  Or they changed things.
> 
> btw, was it really silent?  Didn't modprobe complain?
> 
> The patch makes sense in any case.

Not totally silent, there was an error about KVM failing to enable
hardware virtualization, but it was generic and didn't really point to
the problem.

-- 

Sasha.

--
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/