From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46598) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XyINO-0003ab-B1 for qemu-devel@nongnu.org; Tue, 09 Dec 2014 05:50:48 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XyINH-0001t7-Gd for qemu-devel@nongnu.org; Tue, 09 Dec 2014 05:50:42 -0500 Received: from mx1.redhat.com ([209.132.183.28]:48271) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XyINH-0001sx-5t for qemu-devel@nongnu.org; Tue, 09 Dec 2014 05:50:35 -0500 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id sB9AoXcB019855 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Tue, 9 Dec 2014 05:50:33 -0500 Date: Tue, 9 Dec 2014 11:50:31 +0100 From: Kashyap Chamarthy Message-ID: <20141209105031.GA13012@tesla.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [Qemu-devel] Cubietruck: cannot create KVM guests: "kvm_init_vcpu failed: Invalid argument" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: rjones@redhat.com Booting a minimal KVM guest throws the below error on Cubietruck: "kvm_init_vcpu failed: Invalid argument" More context and an easy reproducer in this QEMU bug[1] for Fedora. Context quoting Rich Jones from comment #2: "For some reason I thought this had been fixed upstream, but now that I've finally got my CT working again, I see that I am still carrying that patch in my custom qemu. diff --git a/target-arm/cpu.c b/target-arm/cpu.c index 5ce7350..04d69d1 100644 --- a/target-arm/cpu.c +++ b/target-arm/cpu.c @@ -858,7 +858,7 @@ static void cortex_a15_initfn(Object *obj) set_feature(&cpu->env, ARM_FEATURE_DUMMY_C15_REGS); set_feature(&cpu->env, ARM_FEATURE_CBAR_RO); set_feature(&cpu->env, ARM_FEATURE_LPAE); - cpu->kvm_target = QEMU_KVM_ARM_TARGET_CORTEX_A15; + cpu->kvm_target = QEMU_KVM_ARM_TARGET_CORTEX_A7; cpu->midr = 0x412fc0f1; cpu->reset_fpsid = 0x410430f0; cpu->mvfr0 = 0x10110222; So that's the answer really, it's a qemu bug. Actually it looks as if qemu contains some code to try to get the host CPU type, but it doesn't work, or maybe we need to pass a -cpu option ..." [1] https://bugzilla.redhat.com/show_bug.cgi?id=1171501 -- Cubietruck: cannot create KVM guests: "kvm_init_vcpu failed: Invalid argument" -- /kashyap