From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43414) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z7m6G-0006tF-5E for qemu-devel@nongnu.org; Wed, 24 Jun 2015 10:56:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z7m6C-0007XZ-Qo for qemu-devel@nongnu.org; Wed, 24 Jun 2015 10:56:28 -0400 Received: from mx1.redhat.com ([209.132.183.28]:36595) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z7m6C-0007XN-LX for qemu-devel@nongnu.org; Wed, 24 Jun 2015 10:56:24 -0400 Message-ID: <558AC512.1000601@redhat.com> Date: Wed, 24 Jun 2015 16:56:18 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <20150608201835.GM3525@orkuz.home> <558951C0.3050806@suse.de> <20150623150828.GD3134@thinpad.lan.raisama.net> <20150623173048-mutt-send-email-mst@redhat.com> <20150623155832.GE3134@thinpad.lan.raisama.net> <55898637.6080804@suse.de> <20150623162555.GL30318@redhat.com> <20150623183115-mutt-send-email-mst@redhat.com> <20150623164204.GM30318@redhat.com> <20150623231818-mutt-send-email-mst@redhat.com> <20150624141651.GS3134@thinpad.lan.raisama.net> <558AC0FB.6090608@redhat.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 0/2] target-i386: "custom" CPU model + script to dump existing CPU models List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Michael Mueller , "Michael S. Tsirkin" , QEMU Developers , Alexander Graf , Christian Borntraeger , Igor Mammedov , Jiri Denemark , Richard Henderson , =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= , Eduardo Habkost On 24/06/2015 16:54, Peter Maydell wrote: > > It's certainly okay for libvirt and OpenStack to use the host CPU > > features in order to check whether a node will run a given VM. However, > > libvirt should trust that QEMU developers will not prevent a VM from > > running on a previously viable host, just because you change the machine > > type. > > Note that this might be true for x86 but isn't (in full generality) > necessarily so for other architectures like ARM. For instance if > you have a host machine with a GICv3 with no v2-back-compatibility > support, then you can run a VM whose machine type specifies a GICv3, > but not machine types that require a GICv2... Hmm, that was too terse. Just because you change the machine type *to a newer version* with the same chipset. Paolo