From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:45567) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YqMx6-0003i2-1A for qemu-devel@nongnu.org; Thu, 07 May 2015 10:39:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YqMx2-0001wH-KH for qemu-devel@nongnu.org; Thu, 07 May 2015 10:39:03 -0400 Received: from mx1.redhat.com ([209.132.183.28]:57359) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YqMx2-0001w0-Er for qemu-devel@nongnu.org; Thu, 07 May 2015 10:39:00 -0400 Message-ID: <554B7901.7070607@redhat.com> Date: Thu, 07 May 2015 10:38:57 -0400 From: Cole Robinson MIME-Version: 1.0 References: <00d901d0880d$d795b750$86c125f0$@samsung.com> <012701d08827$4f771250$ee6536f0$@samsung.com> <00bc01d08890$3883bc10$a98b3430$@samsung.com> In-Reply-To: <00bc01d08890$3883bc10$a98b3430$@samsung.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] Fix default CPU model for ARM64 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Pavel Fedin , 'Peter Maydell' Cc: 'QEMU Developers' On 05/07/2015 02:36 AM, Pavel Fedin wrote: > Hello! > >> Yes. qemu-system-aarch64 -cpu cortex-a15 gets you a 32-bit Cortex-A15. This is >> exactly like the x86 QEMU, where you can emulate all the 32-bit x86 CPUs in >> qemu-system-x86_64. > > And what is the default in x86_64 ? I believe it's 64-bit CPU, and not i686, isn't it ? > I agree that -cpu cortex-a15 might work with qemu-system-aarch64. But isn't it expected to get the "native" CPU by default ? This behavior of qemu causes weird thing with libvirt/virt-manager. I create a VM, specify "aarch64" as architecture, and set "hypervisor default" as CPU model. With "hypervisor default" libvirt does not pass any -cpu option to qemu, leaving it up to the emulator (exactly as expected). So, i supply 64-bit kernel and rootfs, and nothing works. I have to explicitly change the CPU to "cortex-a57". Isn't it confusing to have such a default ? > This is even more confusing since currently i don't know any implementation of aarch64 except A57 and A53 (which are the same from software point of view). So, i believe, A57 is quite a reasonable default. > FWIW virt-manager 1.2.0 (just released) will do the following when creating a new VM: - aarch64 + kvm : -cpu host - aarch64 + tcg : -cpu cortex-a57 - arm32 + kvm : -cpu host - arm32 + tcg : defer to qemu Though if you explicitly request 'hypervisor default' then we won't specify any -cpu and defer to qemu, which will hit the cortex-a15 default for aarch64 - Cole