From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56946) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XyJCB-0002y6-8g for qemu-devel@nongnu.org; Tue, 09 Dec 2014 06:43:17 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XyJC2-0000aa-SV for qemu-devel@nongnu.org; Tue, 09 Dec 2014 06:43:11 -0500 Received: from mail-lb0-f181.google.com ([209.85.217.181]:33257) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XyJC2-0000aP-M9 for qemu-devel@nongnu.org; Tue, 09 Dec 2014 06:43:02 -0500 Received: by mail-lb0-f181.google.com with SMTP id l4so339154lbv.12 for ; Tue, 09 Dec 2014 03:43:01 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <20141209112543.GZ15695@redhat.com> References: <20141209105031.GA13012@tesla.redhat.com> <20141209112543.GZ15695@redhat.com> From: Peter Maydell Date: Tue, 9 Dec 2014 11:42:41 +0000 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [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: "Richard W.M. Jones" Cc: QEMU Developers , Kashyap Chamarthy On 9 December 2014 at 11:25, Richard W.M. Jones wrote: > I really think that qemu should just "do the right thing" though. Tricky, because you have to use the same CPU as the host if you want to use KVM, and that conflicts with wanting to do the same thing on all host platforms for a given set of command line options. If you have some concrete suggestions for improving things that don't break backwards-compatibility I'm happy to hear them, though. -- PMM