From mboxrd@z Thu Jan 1 00:00:00 1970 From: poma Subject: KVM SVM(AMD) nested - disabled by default? Date: Sat, 23 Jan 2016 16:07:21 +0100 Message-ID: <56A39729.8020106@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: kvm-devel , Joerg Roedel , Avi Kivity , Cole Robinson , "Richard W.M. Jones" To: Paolo Bonzini Return-path: Received: from mail-wm0-f51.google.com ([74.125.82.51]:36386 "EHLO mail-wm0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753175AbcAWPHY (ORCPT ); Sat, 23 Jan 2016 10:07:24 -0500 Received: by mail-wm0-f51.google.com with SMTP id l65so16919043wmf.1 for ; Sat, 23 Jan 2016 07:07:24 -0800 (PST) Sender: kvm-owner@vger.kernel.org List-ID: "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?