From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: KVM_SET_MP_STATE is undocumented Date: Mon, 26 Apr 2010 16:21:45 +0300 Message-ID: <4BD59369.2040703@redhat.com> References: <4BD084E7.3020609@cs.helsinki.fi> <4BD43AF6.4020901@redhat.com> <4BD54558.4000704@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]:7624 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751093Ab0DZNVy (ORCPT ); Mon, 26 Apr 2010 09:21:54 -0400 In-Reply-To: <4BD54558.4000704@cs.helsinki.fi> Sender: kvm-owner@vger.kernel.org List-ID: On 04/26/2010 10:48 AM, Pekka Enberg wrote: > Two more interesting but undocumented ioctls: > > - KVM_SET_IDENTITY_MAP_ADDR > - KVM_SET_BOOT_CPU_ID I'll post patches. > Little background: we're debugging a KVM_EXIT_UNKNOWN problem for the > "largest bug-free kernel" on Core i5 machine. I've been looking at > plain QEMU sources but it seems "qemu-kvm" that the person is using > does much more during initialization. Do we have a known good list of > mandatory steps required to properly initialize KVM on all CPUs? KVM_GET_API_VERSION (unless you're sure you aren't running on 2.6.20 or 2.6.21) KVM_CREATE_VM KVM_SET_USER_MEMORY_REGION KVM_CREATE_VCPU KVM_SET_TSS_ADDR KVM_SET_IDENTITY_MAP_ADDR (really only needed on EPT machines, but recommended to invoke on all hosts) KVM_CREATE_IRQCHIP (optional; if you want in-kernel lapic/ioapic/pic) KVM_SET_CPUID2 KVM_RUN qemu also initializes all the vcpu state from its own values and has elaborate memory setup. -- error compiling committee.c: too many arguments to function