From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MRRyJ-0002VO-J6
	for qemu-devel@nongnu.org; Thu, 16 Jul 2009 10:30:07 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MRRyE-0002PS-QG
	for qemu-devel@nongnu.org; Thu, 16 Jul 2009 10:30:07 -0400
Received: from [199.232.76.173] (port=44127 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MRRyE-0002P1-LW
	for qemu-devel@nongnu.org; Thu, 16 Jul 2009 10:30:02 -0400
Received: from mail2.shareable.org ([80.68.89.115]:50614)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <jamie@shareable.org>) id 1MRRyD-00019Q-KD
	for qemu-devel@nongnu.org; Thu, 16 Jul 2009 10:30:01 -0400
Date: Thu, 16 Jul 2009 15:29:58 +0100
From: Jamie Lokier <jamie@shareable.org>
Subject: Re: [Qemu-devel] CPUID feature bits not saved with migration
Message-ID: <20090716142958.GB16461@shareable.org>
References: <4A5DD0B0.7070700@amd.com> <4A5DE9E5.2080809@codemonkey.ws>
	<20090715151234.GA28724@shareable.org>
	<4A5ECEE9.8070708@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4A5ECEE9.8070708@redhat.com>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Dor Laor <dlaor@redhat.com>
Cc: Andre Przywara <andre.przywara@amd.com>, qemu-devel@nongnu.org

Dor Laor wrote:
> On 07/15/2009 06:12 PM, Jamie Lokier wrote:
> >Anthony Liguori wrote:
> >>It's unclear what to do about -cpu host.  If we did migrate cpuid
> >>values, then -cpu would effectively be ignored after an incoming 
> >>migration.
> 
> Actually, it might be better to build all of the guest configurations 
> (devices, cpu, etc) from the migration stream, without stating them in 
> the destination command line.
> 
> The destination command line should only contain host configuration.
> It will bypass any type of conflict between the src/dst pairs.

I agree, but this will be a lot simpler and more satisfying once
there's a machine configuration file which can be dumped from qemu and
reloaded into it, with host configuration from the command line merged
into the configuration file at load time.

-- Jamie