A live update keeps the passthrough device open while the VM is re-created. The device holds a reference to the kvm it was opened with, so the first VM is never destroyed until the device closes. Take that reference only for the drivers that read device->kvm.
Tested with this patch alone: 30 live updates of a vGPU VM (RTX 6000 Ada SR-IOV VF) under guest DMA load, then 4 live migrations between two such nodes: one KVM instance after every update, no "duplicate directory", and no DMA'd buffer differing from the pattern written into it. v2 -> v3: - Patch 2 (debugfs directory) dropped: with patch 1 nothing holds the old VM past exec. Traced: the VM fd release and kvm_destroy_vm() run at exec, 180 ms before the new QEMU creates its VM, so the directory is gone before the name can clash; the test above ran without it - Patch 1: "in open_device()" and "device->kvm stays NULL without the flag" in the comment and the message, how nvidia-vgpu-vfio was checked, Assisted-by moved here, blank line before Feature: v2: http://lore.virtuozzo.com/[email protected] v1: http://lore.virtuozzo.com/[email protected] Assisted-by: LLM Andrey Drobyshev (1): vfio: take the kvm reference only for drivers that read device->kvm drivers/gpu/drm/i915/gvt/kvmgt.c | 1 + drivers/s390/crypto/vfio_ap_ops.c | 1 + drivers/vfio/pci/vfio_pci_core.c | 1 + drivers/vfio/vfio_main.c | 6 ++++-- include/linux/vfio.h | 7 +++++++ 5 files changed, 14 insertions(+), 2 deletions(-) -- 2.47.1 _______________________________________________ Devel mailing list [email protected] https://lists.openvz.org/mailman/listinfo/devel
