On Thursday, October 27, 2022 11:27 PM, Sean Christopherson wrote: > Yeah, just allocate the max for now, though the array still needs to be > dynamically allocated based on the actual maximum number of vCPUs. Oh, duh, > we can do the easy thing and just bump KVM_MAX_VCPUS to 1024 to match > KVM. And then assert that > kvm_check_cap(KVM_CAP_MAX_VCPUS) == KVM_CAP_MAX_VCPUS in > kvm_create_max_vcpus.c. Right. I thought about the same thing, we should update KVM_MAX_VCPUS anyway.
