Currently, TDX QEMU always configure TD_PARAMS.MAX_VCPUS as the number of actual vcpus it has created for the TD.
So in the TDG.VP.INFO, the returned value of NUM_VCPUS and MAX_VCPUS in R8 are always same.
However, TDX QEMU + KVM are going to set a big value for TD_PARAMS.MAX_VCPUS than actual created TD vcpus, which triggers the issue and find the bug.
Description
Currently, TDX QEMU always configure TD_PARAMS.MAX_VCPUS as the number of actual vcpus it has created for the TD. So in the TDG.VP.INFO, the returned value of NUM_VCPUS and MAX_VCPUS in R8 are always same.
However, TDX QEMU + KVM are going to set a big value for TD_PARAMS.MAX_VCPUS than actual created TD vcpus, which triggers the issue and find the bug.