KVM: selftests: Make sure kvm_create_max_vcpus test won't hit RLIMIT_NOFILE
authorVitaly Kuznetsov <vkuznets@redhat.com>
Tue, 23 Nov 2021 13:59:53 +0000 (14:59 +0100)
committerPaolo Bonzini <pbonzini@redhat.com>
Fri, 26 Nov 2021 13:14:20 +0000 (08:14 -0500)
commit908fa88e420f30dde6d80f092795a18ec72ca6d3
tree35b40b49385269e6771ba28382841b6bfc66dab9
parentfeb627e8d6f69c9a319fe279710959efb3eba873
KVM: selftests: Make sure kvm_create_max_vcpus test won't hit RLIMIT_NOFILE

With the elevated 'KVM_CAP_MAX_VCPUS' value kvm_create_max_vcpus test
may hit RLIMIT_NOFILE limits:

 # ./kvm_create_max_vcpus
 KVM_CAP_MAX_VCPU_ID: 4096
 KVM_CAP_MAX_VCPUS: 1024
 Testing creating 1024 vCPUs, with IDs 0...1023.
 /dev/kvm not available (errno: 24), skipping test

Adjust RLIMIT_NOFILE limits to make sure KVM_CAP_MAX_VCPUS fds can be
opened. Note, raising hard limit ('rlim_max') requires CAP_SYS_RESOURCE
capability which is generally not needed to run kvm selftests (but without
raising the limit the test is doomed to fail anyway).

Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Message-Id: <20211123135953.667434-1-vkuznets@redhat.com>
[Skip the test if the hard limit can be raised. - Paolo]
Reviewed-by: Sean Christopherson <seanjc@google.com>
Tested-by: Sean Christopherson <seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
tools/testing/selftests/kvm/kvm_create_max_vcpus.c