From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Williamson Subject: Re: [RFC PATCH] kvm: Enable -cpu option to hide KVM Date: Mon, 02 Jun 2014 08:42:12 -0600 Message-ID: <1401720132.9207.42.camel@ul30vt.home> References: <20140601162414.28708.22775.stgit@bling.home> <538B70FF.6050103@redhat.com> <1401657070.9207.6.camel@ul30vt.home> <538C233F.5030106@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org To: Paolo Bonzini Return-path: Received: from mx1.redhat.com ([209.132.183.28]:37766 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755016AbaFBOmO (ORCPT ); Mon, 2 Jun 2014 10:42:14 -0400 In-Reply-To: <538C233F.5030106@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Mon, 2014-06-02 at 09:09 +0200, Paolo Bonzini wrote: > Il 01/06/2014 23:11, Alex Williamson ha scritto: > >> > > >> > It's really a nit, but I think "kvm=no" is preferrable (more consistent > >> > with how hyper-v leaves are enabled). > > Happy to oblige, but I'm not sure what I'm looking for. We enably > > hyper-v leaves if hyperv_enabled(), which seems to boil down to the kvm > > kernel supporting KVM_CAP_HYPERV and one or more cpu->hyperv_foo > > features enabled. What's the commandline option I'm looking for that > > has some sort of hyper-v=on|off? Thanks, > > Same as your "no-kvm", just with the default flipped from false to true. Ah, easy enough. Do we want to limit the scope a bit by indicating exactly what is getting disabled, perhaps kvm-msr=on|off? Thanks, Alex