From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:58766) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RbChZ-0006Pf-Ky for qemu-devel@nongnu.org; Thu, 15 Dec 2011 09:54:33 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RbChT-0006K0-P2 for qemu-devel@nongnu.org; Thu, 15 Dec 2011 09:54:29 -0500 Received: from mx1.redhat.com ([209.132.183.28]:30804) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RbChT-0006JX-IG for qemu-devel@nongnu.org; Thu, 15 Dec 2011 09:54:23 -0500 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id pBFEsMj6027448 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 15 Dec 2011 09:54:22 -0500 Date: Thu, 15 Dec 2011 15:54:15 +0100 From: Jiri Denemark Message-ID: <20111215145415.GA265695@orkuz.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [Qemu-devel] Modern CPU models cannot be used with libvirt List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: libvir-list@redhat.com, qemu-devel@nongnu.org Hi, Recently I realized that all modern CPU models defined in /etc/qemu/target-x86_64.conf are useless when qemu is used through libvirt. That's because we start qemu with -nodefconfig which results in qemu ignoring that file with CPU model definitions. We have a very good reason for using -nodefconfig because we need to control the ABI presented to a guest OS and we don't want any configuration file that can contain lots of things including device definitions to be read by qemu. However, we would really like the new CPU models to be understood by qemu even if used through libvirt. What would be the best way to solve this? I suspect this could have been already discussed in the past but obviously a workable solution was either not found or just not implemented. Jirka