From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:48241) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZZIw6-0006sR-CY for qemu-devel@nongnu.org; Tue, 08 Sep 2015 09:27:47 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZZIw2-00085f-DD for qemu-devel@nongnu.org; Tue, 08 Sep 2015 09:27:46 -0400 Received: from mx1.redhat.com ([209.132.183.28]:52851) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZZIw2-00085E-87 for qemu-devel@nongnu.org; Tue, 08 Sep 2015 09:27:42 -0400 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (Postfix) with ESMTPS id D856CC0B986B for ; Tue, 8 Sep 2015 13:27:40 +0000 (UTC) Received: from dhcp129-213.brq.redhat.com (dhcp129-213.brq.redhat.com [10.34.129.213]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t88DRcGu002996 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Tue, 8 Sep 2015 09:27:40 -0400 Message-ID: <1441718858.14506.1.camel@redhat.com> From: Andrea Bolognani Date: Tue, 08 Sep 2015 15:27:38 +0200 Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Target vs architecture for QEMU binary List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Hi, at the moment, libvirt is using some ad-hoc logic to allow i686 guests to run on qemu-system-x86_64 (by using the CPU model qemu32); in all other cases, it's assumed that a $arch guest needs qemu-system-$arch to run. This is causing a problem right now with ppc64le guests because, even though qemu-system-ppc64 is perfectly capable of running them, libvirt will refuse to. We want to change the logic so that it reflects the actual capabilities of the QEMU binary, but AFAICT there isn't eg. a QMP command we can use to query the binary for the list of architectures it implements. Am I missing something? Is such an interface available? Failing that, we'll have to map QEMU targets with implemented guest architectures inside libvirt, in which case it would be great if you could point me towards either some up-to-date documentation or a reliable way to extract the information myself. Thank you for your help. -- Andrea Bolognani Software Engineer - Virtualization Team