From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH] qemu-kvm: Ask kernel about supported svm features Date: Thu, 22 Apr 2010 17:48:46 +0300 Message-ID: <4BD061CE.4060808@redhat.com> References: <1271933879-15849-1-git-send-email-joerg.roedel@amd.com> <4BD02DE2.9010106@redhat.com> <20100422120249.GW31537@amd.com> <4BD03D5A.6090905@redhat.com> <20100422122802.GA28773@8bytes.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Joerg Roedel , Anthony Liguori , kvm@vger.kernel.org To: Joerg Roedel Return-path: Received: from mx1.redhat.com ([209.132.183.28]:31217 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755212Ab0DVOsz (ORCPT ); Thu, 22 Apr 2010 10:48:55 -0400 In-Reply-To: <20100422122802.GA28773@8bytes.org> Sender: kvm-owner@vger.kernel.org List-ID: On 04/22/2010 03:28 PM, Joerg Roedel wrote: > >> Yes. -cpu host should take KVM_GET_SUPPORTED_CPUID output and loop it >> back to the vcpu configuration, others just take the qemu configuration, >> mask it with supported bits, and pass it back (see >> check_features_against_host()). >> > Hmm, the plan was to enable with -enable-nesting all kernel supported > svm features for the guest (and add switches later to remove them > individually) > If we activate nested svm with -cpu host in the future thats fine too > (closed-source hypervisors need that anyway). But we should also define > a cpu model in which we can migrate nested hypervisors between machines > were the cpu is not completly indentical. > You can use -cpu host, or -cpu kvm64,+svm,+npt,+other_feature... just as with all other features. -- error compiling committee.c: too many arguments to function