From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43537) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V9GyQ-0003H2-6v for qemu-devel@nongnu.org; Tue, 13 Aug 2013 11:57:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V9GyI-0004qx-MT for qemu-devel@nongnu.org; Tue, 13 Aug 2013 11:57:30 -0400 Received: from cantor2.suse.de ([195.135.220.15]:56327 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V9GyI-0004qs-GN for qemu-devel@nongnu.org; Tue, 13 Aug 2013 11:57:22 -0400 Message-ID: <520A575F.7040302@suse.de> Date: Tue, 13 Aug 2013 17:57:19 +0200 From: =?ISO-8859-1?Q?Andreas_F=E4rber?= MIME-Version: 1.0 References: <20130813125349.GA28317@redhat.com> <87a9klllyz.fsf@codemonkey.ws> <520A48C0.5000205@redhat.com> <520A4C8C.7090202@suse.de> <520A5059.10009@redhat.com> In-Reply-To: <520A5059.10009@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH for-1.6] pc: fix up pc initialization List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Anthony Liguori , "Michael S. Tsirkin" , marcel.a@redhat.com, Michael Roth , qemu-devel@nongnu.org, Gerd Hoffmann , Igor Mammedov Am 13.08.2013 17:27, schrieb Paolo Bonzini: > Il 13/08/2013 17:11, Andreas F=E4rber 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, sinc= e >> 1.5.3 is still a bit off and I would expect 1.5.2 -> 1.6.0 migration t= o >> work without guest-visible changes... We could argue that having to us= e >> -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=3D0 for that purpose until we have a better solution. >=20 > pvpanic has no vmstate though, has it? So it won't break migration > (needs testing of course). Just checked, you're right, it doesn't. I somehow assumed it would. > All that should happen is that after migration you will not get panic > notifications on the destination. Well, how does the Linux driver cope with pvpanic device present on boot but not present on panic? ISA PIO is not usually expected to be hot-unplugged. ;) Andreas --=20 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend=F6rffer; HRB 16746 AG N=FCrnbe= rg