public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [RFC PATCH] kvm: Enable -cpu option to hide KVM
Date: Mon, 02 Jun 2014 22:01:49 +0400	[thread overview]
Message-ID: <538CBC0D.8000704@msgid.tls.msk.ru> (raw)
In-Reply-To: <1401715821.9207.20.camel@ul30vt.home>

02.06.2014 17:30, Alex Williamson wrote:
> On Mon, 2014-06-02 at 14:32 +0400, Michael Tokarev wrote:
>> 01.06.2014 20:25, Alex Williamson wrote:
>>> 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.
> 
> Then they'll be pissing off more users and driving them to AMD by doing
> so.  In any case, having the ability to hide the hypervisor seems to
> stand on it's own.  What if we want to test whether a guest behavior is
> the result of a paravirtual interface?  What if a user wants to hide the
> hypervisor in order to further reduce the exposure surface to the VM?
> There are reasons beyond an arms race with Nvidia to want a feature like
> this.  Thanks,

You answer as if I were strongly against the change.  I'm not.
What I'm against is about the reasoning.  This way you're just
accepting the arm race.

Thanks,

/mjt

  parent reply	other threads:[~2014-06-02 18:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-01 16:25 [RFC PATCH] kvm: Enable -cpu option to hide KVM Alex Williamson
2014-06-01 18:29 ` Paolo Bonzini
2014-06-01 21:11   ` Alex Williamson
2014-06-02  7:09     ` Paolo Bonzini
2014-06-02 14:42       ` Alex Williamson
2014-06-02 15:55         ` Paolo Bonzini
2014-06-02 10:32 ` Michael Tokarev
2014-06-02 13:30   ` Alex Williamson
2014-06-02 15:55     ` Paolo Bonzini
2014-06-02 18:01     ` Michael Tokarev [this message]
2014-06-02 18:37       ` Alex Williamson
2014-06-02 19:03       ` Bandan Das
2014-06-02 19:18         ` Alex Williamson

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=538CBC0D.8000704@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=alex.williamson@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox