From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [libvirt] [PATCH 0/3] sample: vfio mdev display devices. Date: Thu, 19 Apr 2018 16:54:23 +0200 Message-ID: References: <20180409103513.8020-1-kraxel@redhat.com> <20180418123153.0f4f037d@w520.home> <20180419084018.dnemdfl4fysg7gkj@sirius.home.kraxel.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, Erik Skultety , libvirt , Tina Zhang , kwankhede@nvidia.com, intel-gvt-dev@lists.freedesktop.org To: Gerd Hoffmann , Alex Williamson Return-path: In-Reply-To: <20180419084018.dnemdfl4fysg7gkj@sirius.home.kraxel.org> Content-Language: en-US List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: libvir-list-bounces@redhat.com Errors-To: libvir-list-bounces@redhat.com List-Id: kvm.vger.kernel.org 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