From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Evans Subject: [PATCH V2 06/23] kvm tools: Don't die if KVM_CAP_NR_VCPUS isn't available Date: Fri, 09 Dec 2011 17:54:01 +1100 Message-ID: <4EE1B089.8060509@ozlabs.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: penberg@kernel.org, asias.hejun@gmail.com, levinsasha928@gmail.com, gorcunov@gmail.com To: kvm@vger.kernel.org, kvm-ppc@vger.kernel.org Return-path: In-Reply-To: Sender: kvm-ppc-owner@vger.kernel.org List-Id: kvm.vger.kernel.org We die() if we can't read KVM_CAP_NR_VCPUS, but the API docs suggest to assume the value 4 in this case. This is pertinent to PPC KVM, which currently does not support this CAP. Signed-off-by: Matt Evans --- tools/kvm/kvm.c | 6 +++++- 1 files changed, 5 insertions(+), 1 deletions(-) diff --git a/tools/kvm/kvm.c b/tools/kvm/kvm.c index 0356d74..0bbe9ba 100644 --- a/tools/kvm/kvm.c +++ b/tools/kvm/kvm.c @@ -266,7 +266,11 @@ int kvm__recommended_cpus(struct kvm *kvm) ret = ioctl(kvm->sys_fd, KVM_CHECK_EXTENSION, KVM_CAP_NR_VCPUS); if (ret <= 0) - die_perror("KVM_CAP_NR_VCPUS"); + /* + * api.txt states that if KVM_CAP_NR_VCPUS does not exist, + * assume 4. + */ + return 4; return ret; }