On 19/04/2018 10:40, Gerd Hoffmann wrote:
> So I was ready to return and suggest that maybe libvirt should
probe
> the device to know about these ancillary configuration details, but
> then I remembered that both mdev vGPU vendors had external dependencies
> to even allow probing the device. KVMGT will fail to open the device
> if it's not associated with an instance of KVM and NVIDIA vGPU, I
> believe, will fail if the vGPU manager process cannot find the QEMU
> instance to extract the VM UUID. (Both of these were bad ideas)
Oops. I've trapped into the kvm issue too. Wondering what the reason
is, shouldn't this work with tcg too?
As far as I understand, KVMGT requires KVM support in order to track
writes to guest memory. It's a kernel API provided by the kvm.ko
module, so no TCG support.
Paolo