On 2/9/26 06:44, Ani Sinha wrote:
On 9 Feb 2026, at 9:37 AM, Ani Sinha <[email protected]> wrote:
On Mon, Feb 9, 2026 at 3:38 AM Cédric Le Goater <[email protected]> wrote:
On 2/8/26 15:39, Ani Sinha wrote:
On Tue, Jan 27, 2026 at 10:47 AM Ani Sinha <[email protected]> wrote:
Normally the vfio pseudo device file descriptor lives for the life of the VM.
However, when the kvm VM file descriptor changes, a new file descriptor
for the pseudo device needs to be generated against the new kvm VM descriptor.
Other existing vfio descriptors needs to be reattached to the new pseudo device
descriptor. This change performs the above steps.
I have not been able to test this change. Can someone suggest a way to
add a functional test and/or test this manually?
Automated VFIO testing [*] is tough because it depends on a "real"
physical PCI device.
I have tested you series using a sev-snp guest with an assigned device
(SATA controller) and verified that the guest could reboot. The SATA
controller has no disks connected, so further testing is required.
However, a 'system_reset' command issued from the QEMU monitor leaves
the guest hanging. May be this is expected ?
I do not think so. On non-coco, I just tried it and it reboots fine
with x-change-vmfd-on-reset turned on.
Sorry I had some issues with my testing. Neither non-coco reset not coco reset
was using vmfd change path when the QMP reset command was used.
In non-coco, it was the normal reset which obviously works.
I fixed it. See
https://gitlab.com/anisinha/qemu/-/commit/c5514dbb2b52d474397220cfa3a0b8faa26cda0c
Please use this patch and test. I have tasted this on SNP and seems to work. I
will make it part of next spin-up.
Looks to me.
Thanks,
C.
