On 2/18/26 17:06, Ani Sinha wrote:
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.


The guest is SEV-SNP and has 2 cpus.

[root@vm12 ~]# dmesg  | grep SEV
[    0.544608] Memory Encryption Features active: AMD SEV SEV-ES SEV-SNP
[    0.545580] SEV: Status: SEV SEV-ES SEV-SNP
[    0.663592] SEV: APIC: wakeup_secondary_cpu() replaced with 
wakeup_cpu_via_vmgexit()
[    0.719630] SEV: Using SNP CPUID table, 32 entries present.
[    0.719636] SEV: SNP running at VMPL0.
[    1.043748] SEV: SNP guest platform devices initialized.
[    4.530555] sev-guest sev-guest: Initialized SEV guest driver (using 
vmpck_id 0)
vmpck_id 0)
[root@vm12 ~]# lscpu
Architecture:                x86_64
  CPU op-mode(s):            32-bit, 64-bit
  Address sizes:             40 bits physical, 48 bits virtual
  Byte Order:                Little Endian
CPU(s):                      2
  On-line CPU(s) list:       0,1
Vendor ID:                   AuthenticAMD
  BIOS Vendor ID:            QEMU
  Model name:                AMD EPYC-v4 Processor
    BIOS Model name:         pc-q35-11.0
    ....


Reply via email to