From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 2E80D1381F3 for ; Wed, 31 Jul 2013 12:12:19 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E2EABE0A8A; Wed, 31 Jul 2013 12:12:09 +0000 (UTC) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id E682CE0A61 for ; Wed, 31 Jul 2013 12:12:08 +0000 (UTC) Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 85C1B21042 for ; Wed, 31 Jul 2013 08:12:08 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Wed, 31 Jul 2013 08:12:08 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.co.uk; h= message-id:date:from:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; s=mesmtp; bh=2ozYw0gm0yccqq4tuzLU0yT4n2s=; b=FoSYyI3d9Oqh2y7FRXjLzpl1iTMA ejEFsyrfq6B4nJi4ZvHCWZ8gZ6L1Lp8VvZ04DhhOozqrWU4K1gecUv5QnQG6/lhH T8cL3ltV3IE4/bxrAHWPJrmpfiQPXk568cZsxJeTOwGKPNzbXMri147nk/n8CzFZ 5n7x0kfbxj8Bl90= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=2ozYw0gm0yccqq4tuzLU0y T4n2s=; b=O26ZulHMSaT5nLs4i9BxKCUsqv30ZBr2jQHESdakBb1MEX0pmrpOgX 3gbHQrVK21bD8uKnYSQajxtBY5nP/mOd+6Nau4Kz1StkiX9L9GBo3kVPnt/z8Oit +E/rkqwIQK7ei+dx9WRx5dxDbCNt1tKepEVhpdlgmeUXjzIIiFTA8= X-Sasl-enc: FU3kgJ8VNLeUs80THfjEYRxfvBBGe+GND+dvC9OfJQ8P 1375272728 Received: from [192.168.1.100] (unknown [94.170.82.148]) by mail.messagingengine.com (Postfix) with ESMTPA id 3676AC00E7F for ; Wed, 31 Jul 2013 08:12:08 -0400 (EDT) Message-ID: <51F8FF11.1010401@fastmail.co.uk> Date: Wed, 31 Jul 2013 13:12:01 +0100 From: Kerin Millar User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Recommendation for CPU type in QEMU? References: <20130731101124.GB26440@waltdnes.org> <20130731133142.570697ee@marcec.hunte.us> In-Reply-To: <20130731133142.570697ee@marcec.hunte.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: e20c9a36-1c8b-4a3e-bd3d-3c7379f3cb82 X-Archives-Hash: a6d1be23ff53d979d3345ec7f650fb4d On 31/07/2013 12:31, Marc Joliet wrote: [snip] > > There's also "-cpu host", which simply passes your CPU through to the guest. > That's what I use for my 32 bit WinXP VM. You can use it if you don't mind not > being able to migrate your guest, but it sounds to me like you're doing this on > a desktop machine, so I suspect guest migration doesn't matter to you. > I thought the same until very recently but it's not the case. The -cpu host feature exposes all feature bits supported by qemu. Those may include features that aren't supported in hardware by the host CPU, in which case qemu has to resort to (slow) emulation if they are used. --Kerin