From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Problem with KVM guest switching to x86 long mode Date: Sun, 11 Apr 2010 14:48:56 +0300 Message-ID: <4BC1B728.4040507@redhat.com> References: <4BBE2213.6020802@redhat.com> <4BBE277B.1090908@cs.helsinki.fi> <4BBE2EF3.6010304@redhat.com> <4BC16CA3.8060804@cs.helsinki.fi> <4BC1936F.5060009@redhat.com> <4BC19AF6.6030407@cs.helsinki.fi> <4BC19D71.2060703@redhat.com> <4BC19E22.7050602@cs.helsinki.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: KVM General To: Pekka Enberg Return-path: Received: from mx1.redhat.com ([209.132.183.28]:44604 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751054Ab0DKLtJ (ORCPT ); Sun, 11 Apr 2010 07:49:09 -0400 In-Reply-To: <4BC19E22.7050602@cs.helsinki.fi> Sender: kvm-owner@vger.kernel.org List-ID: On 04/11/2010 01:02 PM, Pekka Enberg wrote: >> It should work without 80000008 set up - failure should happen only >> if it is setup incorrectly: >> >> int cpuid_maxphyaddr(struct kvm_vcpu *vcpu) >> { >> struct kvm_cpuid_entry2 *best; >> >> best = kvm_find_cpuid_entry(vcpu, 0x80000008, 0); >> if (best) >> return best->eax & 0xff; >> return 36; >> } > > > Well, like I said, if I don't add an entry for it in struct kvm_cpuid2 > that's passed to KVM_SET_CPUID2 ioctl, I see a triple fault on Core 2 > Duo CPU that doesn't seem to have native 0x80000008. Do you have a function 8, though? Looks like a bug in kvm may confuse the two. -- error compiling committee.c: too many arguments to function