From: Paolo Bonzini <pbonzini@redhat.com>
To: poma <pomidorabelisima@gmail.com>
Cc: kvm-devel <kvm@vger.kernel.org>,
Joerg Roedel <joerg.roedel@amd.com>, Avi Kivity <avi@redhat.com>,
Cole Robinson <crobinso@redhat.com>,
"Richard W.M. Jones" <rjones@redhat.com>
Subject: Re: KVM SVM(AMD) nested - disabled by default?
Date: Sat, 23 Jan 2016 22:05:32 +0100 [thread overview]
Message-ID: <56A3EB1C.5020605@redhat.com> (raw)
In-Reply-To: <56A39729.8020106@gmail.com>
On 23/01/2016 16:07, poma wrote:
> "KVM: SVM: enable nested svm by default"
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/arch/x86/kvm?id=4b6e4dc
> "Nested SVM is (in my experience) stable enough to be enabled by default. So omit the requirement to pass a module parameter."
>
> I tried to get an explanation of the eventual -default- change here:
> https://bugzilla.redhat.com/show_bug.cgi?id=1298244
>
> but "... I am *thinking* of changing it ..." ain't explanation, man.
>
> I've tested "Nested SVM" myself and it works surprisingly well,
> therefore what is the -actual- reason to switch it off by default?
Neither nested VMX nor nested SVM have ever been audited for security;
they could have bugs that let a malicious guest escape L0. In fact I
would be surprised if they don't. :(
Paolo
next prev parent reply other threads:[~2016-01-23 21:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-23 15:07 KVM SVM(AMD) nested - disabled by default? poma
2016-01-23 21:05 ` Paolo Bonzini [this message]
2016-01-25 18:31 ` poma
2016-01-26 9:09 ` Paolo Bonzini
2016-01-26 11:00 ` poma
2016-01-26 21:17 ` Jidong Xiao
2016-01-26 21:28 ` Andrew Honig
2016-01-27 19:08 ` Jidong Xiao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56A3EB1C.5020605@redhat.com \
--to=pbonzini@redhat.com \
--cc=avi@redhat.com \
--cc=crobinso@redhat.com \
--cc=joerg.roedel@amd.com \
--cc=kvm@vger.kernel.org \
--cc=pomidorabelisima@gmail.com \
--cc=rjones@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.