From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:35880)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1V9GW2-00020s-Lu
	for qemu-devel@nongnu.org; Tue, 13 Aug 2013 11:28:20 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1V9GVu-0001ha-7G
	for qemu-devel@nongnu.org; Tue, 13 Aug 2013 11:28:10 -0400
Received: from mail-wg0-x22a.google.com ([2a00:1450:400c:c00::22a]:58298)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1V9GVu-0001hM-1g
	for qemu-devel@nongnu.org; Tue, 13 Aug 2013 11:28:02 -0400
Received: by mail-wg0-f42.google.com with SMTP id j13so2740478wgh.1
	for <qemu-devel@nongnu.org>; Tue, 13 Aug 2013 08:28:01 -0700 (PDT)
Sender: Paolo Bonzini <paolo.bonzini@gmail.com>
Message-ID: <520A5059.10009@redhat.com>
Date: Tue, 13 Aug 2013 17:27:21 +0200
From: Paolo Bonzini <pbonzini@redhat.com>
MIME-Version: 1.0
References: <20130813125349.GA28317@redhat.com> <87a9klllyz.fsf@codemonkey.ws>
	<520A48C0.5000205@redhat.com> <520A4C8C.7090202@suse.de>
In-Reply-To: <520A4C8C.7090202@suse.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Subject: Re: [Qemu-devel] [PATCH for-1.6] pc: fix up pc initialization
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: =?ISO-8859-1?Q?Andreas_F=E4rber?= <afaerber@suse.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>, "Michael S. Tsirkin" <mst@redhat.com>, marcel.a@redhat.com, Michael Roth <mdroth@linux.vnet.ibm.com>, qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>, Igor Mammedov <imammedo@redhat.com>

Il 13/08/2013 17:11, Andreas Färber ha scritto:
> 
> mst suggested to patch stable-1.5 to disable it there, too. I am not
> against but have doubts as to how well that works with migration, since
> 1.5.3 is still a bit off and I would expect 1.5.2 -> 1.6.0 migration to
> work without guest-visible changes... We could argue that having to use
> -M pc-i440fx-1.5 we can also expect users to add -device pvpanic;
> question would be how to convey that knowledge of
> if-you-use-pc-x.y-then-you-also-need-to-do-Z to users, which
> compat_props usually handle under the hood. We could misuse
> pvpanic.ioport=0 for that purpose until we have a better solution.

pvpanic has no vmstate though, has it?  So it won't break migration
(needs testing of course).

All that should happen is that after migration you will not get panic
notifications on the destination.

Paolo