From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tokarev Subject: Re: [RFC PATCH] kvm: Enable -cpu option to hide KVM Date: Mon, 02 Jun 2014 14:32:15 +0400 Message-ID: <538C52AF.4010105@msgid.tls.msk.ru> References: <20140601162414.28708.22775.stgit@bling.home> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: kvm@vger.kernel.org To: Alex Williamson , qemu-devel@nongnu.org Return-path: In-Reply-To: <20140601162414.28708.22775.stgit@bling.home> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org List-Id: kvm.vger.kernel.org 01.06.2014 20:25, Alex Williamson =D1=86=D0=BA=D1=89=D0=B5=D1=83: > The latest Nvidia driver (337.88) specifically checks for KVM as the > hypervisor and reports Code 43 for the driver in a Windows guest when > found. Removing or changing the KVM signature is sufficient to allow > the driver to load. Hmm.. Why does it do such thing? Is it in order to prevent the driver to work in a virtualized windows, ie to prevent vga passthough to work? If that's the case, I think it is a lost game. Because they'll be adding more, cleverer, checks in the next version. Thanks, /mjt