* Sasha Levin <levinsasha928@xxxxxxxxx> wrote: > The patch raises the hard limit of VCPU count to 254. > > This will allow developers to easily work on scalability > and will allow users to test high VCPU setups easily without > patching the kernel. > > To prevent possible issues with current setups, KVM_CAP_NR_VCPUS > now returns the recommended VCPU limit (which is still 64) - this > should be a safe value for everybody, while a new KVM_CAP_MAX_VCPUS > returns the hard limit which is now 254. > > Cc: Avi Kivity <avi@xxxxxxxxxx> > Cc: Ingo Molnar <mingo@xxxxxxx> > Cc: Marcelo Tosatti <mtosatti@xxxxxxxxxx> > Cc: Pekka Enberg <penberg@xxxxxxxxxx> > Suggested-by: Pekka Enberg <penberg@xxxxxxxxxxxxxx> > Signed-off-by: Sasha Levin <levinsasha928@xxxxxxxxx> It would be nice to document the various internal limits that are present (255, etc.) and which prevent further raising of KVM_MAX_VCPUS. This information got mapped out in this discussion, but the commit loses it so it would be nice to preserve it somewhere (at least in the changelog). Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
