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
01.06.2014 20:25, Alex Williamson цкщеу:
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
On Mon, 2014-06-02 at 14:32 +0400, Michael Tokarev wrote:
01.06.2014 20:25, Alex Williamson цкщеу:
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
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
Il 02/06/2014 16:42, Alex Williamson ha scritto:
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,
The capabilities are actually already
Il 02/06/2014 15:30, Alex Williamson ha scritto:
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
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.
On Mon, 2014-06-02 at 22:01 +0400, Michael Tokarev wrote:
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
Michael Tokarev m...@tls.msk.ru writes:
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
On Mon, 2014-06-02 at 15:03 -0400, Bandan Das wrote:
Michael Tokarev m...@tls.msk.ru writes:
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
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. This patch adds an option to easily allow the KVM
hypervisor
Il 01/06/2014 18:25, Alex Williamson ha scritto:
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. This patch adds
On Sun, 2014-06-01 at 20:29 +0200, Paolo Bonzini wrote:
Il 01/06/2014 18:25, Alex Williamson ha scritto:
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
13 matches
Mail list logo
