From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:53986)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <divan@santanas.co.za>) id 1bvWcl-0000Tj-2o
	for qemu-devel@nongnu.org; Sat, 15 Oct 2016 17:36:11 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <divan@santanas.co.za>) id 1bvWch-0003t2-Vb
	for qemu-devel@nongnu.org; Sat, 15 Oct 2016 17:36:11 -0400
Received: from outmail148107.authsmtp.com ([62.13.148.107]:54075)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <divan@santanas.co.za>) id 1bvWch-0003s0-FN
	for qemu-devel@nongnu.org; Sat, 15 Oct 2016 17:36:07 -0400
Received: from mail-c232.authsmtp.com (mail-c232.authsmtp.com [62.13.128.232])
	by punt22.authsmtp.com (8.14.2/8.14.2/) with ESMTP id u9FL5TwK022898
	for <qemu-devel@nongnu.org>; Sat, 15 Oct 2016 22:05:29 +0100 (BST)
Received: from mail.santanas.co.za ([196.192.182.3]) (authenticated bits=0)
	by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id u9FL5PjU038316
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <qemu-devel@nongnu.org>; Sat, 15 Oct 2016 22:05:27 +0100 (BST)
Received: from authenticated-user (mail.santanas.co.za [196.192.182.3])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by mail.santanas.co.za (Postfix) with ESMTPSA id DF32E20336
	for <qemu-devel@nongnu.org>; Sat, 15 Oct 2016 23:05:23 +0200 (SAST)
From: Divan Santana <divan@santanas.co.za>
Date: Sat, 15 Oct 2016 23:05:22 +0200
Message-ID: <87twcdnx0t.fsf@santanas.co.za>
MIME-Version: 1.0
Content-Type: text/plain
Subject: Re: [Qemu-devel] [libvirt] inconsistent handling of "qemu64" CPU
 model
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel/>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

> In your case, you should be able to use
>
>     <cpu mode'custom' match='exact'>
>         <model>qemu64</model>
>         <feature name='svm' policy='disable'/>
>     </cpu>
>
> to get the same CPU model you'd get by default (if not, you may need to
> also add <feature name='vmx' policy='require'/>).
>
> Alternatively
>
>     <cpu mode'custom' match='exact'>
>         <model>qemu64</model>
>         <feature name='svm' policy='force'/>
>     </cpu>
>
> should work too (and it would be better in case you use it on an AMD
> host).

Does anyone know how one can one make the above the default behavior on
a system, using libvirt?

The reason, is that I make use on some vagrant boxes, which have this
issue. I understand that the boxes have incorrectly configured and
hence I have this issue.

I'd prefer to set the above as default on my system, rather then editing
all the vagrant boxes I'm using