On Wed, Feb 18, 2026 at 9:00 PM Cédric Le Goater <[email protected]> wrote: > > On 2/18/26 16:07, Ani Sinha wrote: > > > > > >> On 18 Feb 2026, at 7:37 PM, Cédric Le Goater <[email protected]> wrote: > >> > >> On 2/18/26 12:42, Ani Sinha 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. > >>> Tested-by: Cédric Le Goater <[email protected]> > >> > >> There is a regression since last version. > >> > >> > >> 'reboot' from the guest and command 'system_reset' from the QEMU > >> monitor now generate these outputs: > >> > >> qemu-system-x86_64: info: virtual machine state has been rebuilt with > >> new guest file handle. > >> qemu-system-x86_64: info: virtual machine state has been rebuilt with > >> new guest file handle. > >> qemu-system-x86_64: info: virtual machine state has been rebuilt with > >> new guest file handle. > >> ... > >> > >> and QEMU exits after a while. > > > > I have only seen this in SEV-ES with more than one vcpus. Never with TDX or > > SEV-SNP (single or multiple cpus). > > On which host/guest type did you see this? > > SEV-SNP on a RHEL9 host. Same guest I used before and host says : > > [1816531.409591] kvm_amd: SEV-ES guest requested termination: 0x0:0x0
Ok so the guest is SEV-ES. most likely you are also using > 1 vcpu. Try with one vcpu and/or enabling SEV-SNP.
