From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:34990) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RPb8G-0005SR-T0 for qemu-devel@nongnu.org; Sun, 13 Nov 2011 09:34:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RPb8F-000813-Rg for qemu-devel@nongnu.org; Sun, 13 Nov 2011 09:34:04 -0500 Received: from mx1.redhat.com ([209.132.183.28]:2841) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RPb8F-00080o-HY for qemu-devel@nongnu.org; Sun, 13 Nov 2011 09:34:03 -0500 Message-ID: <4EBFD555.6020208@redhat.com> Date: Sun, 13 Nov 2011 16:33:57 +0200 From: Avi Kivity MIME-Version: 1.0 References: <20111112092227.54142a7a@zooty> <20111112171935.GU16972@garlic.redhat.com> <4EBF9BED.1090308@redhat.com> <20111113124133.GF3624@garlic.redhat.com> <4EBFBCA0.1000809@redhat.com> <20111113140042.GG3624@garlic.redhat.com> <4EBFCE4C.3040606@redhat.com> <20111113141704.GH3624@garlic.redhat.com> In-Reply-To: <20111113141704.GH3624@garlic.redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [fedora-virt] Windows KVM thinks hardware changed when ported to f16? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Tom Horsley , Fedora Virt , Gerd Hoffmann , qemu-devel On 11/13/2011 04:17 PM, Alon Levy wrote: > > > Going after each distribution that packages qemu? No way to do this, I > > > can just hope any packager who encounters this problem comes to > > > spice-devel/qemu-devel. > > > > > > > > > > I'm talking about guests. Images created with 0.15 know that rev=3, > > with 1.0 (or 0.15.next) they'll be back to rev=2. > > > > Ok, my mistake. So yes, there will now be both pc-0.14 with rev 3 and > 2. For migrations there is no problem since the revision is migrated > (since it could be set from the command line anyway). Otherwise, doing > a shutdown, upgrading qemu, and starting the vm again - yes. Other then > "this should never have happened" any suggestions? > No. Clever ideas welcome. Also about "this will never happen again". -- error compiling committee.c: too many arguments to function