From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mx2uM-0005XI-Gy for qemu-devel@nongnu.org; Sun, 11 Oct 2009 14:12:38 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mx2uH-0005Ro-Sl for qemu-devel@nongnu.org; Sun, 11 Oct 2009 14:12:37 -0400 Received: from [199.232.76.173] (port=44089 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mx2uH-0005Rh-Qc for qemu-devel@nongnu.org; Sun, 11 Oct 2009 14:12:33 -0400 Received: from mx1.redhat.com ([209.132.183.28]:32889) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mx2uH-0002NN-DM for qemu-devel@nongnu.org; Sun, 11 Oct 2009 14:12:33 -0400 Date: Sun, 11 Oct 2009 20:10:24 +0200 From: "Michael S. Tsirkin" Subject: Re: [Qemu-devel] Re: [PATCH 2/3] qemu: make cirrus init value pci spec compliant Message-ID: <20091011181024.GA6411@redhat.com> References: <4AD1F173.8040401@redhat.com> <20091011161232.GA10132@redhat.com> <4AD206BE.3050904@redhat.com> <20091011163334.GA6248@redhat.com> <4AD209BD.5020300@redhat.com> <20091011163909.GA6261@redhat.com> <4AD20C62.9010809@redhat.com> <20091011171843.GA6297@redhat.com> <4AD2157F.5040301@redhat.com> <4AD215AD.7050308@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4AD215AD.7050308@redhat.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Anthony Liguori , "qemu-devel@nongnu.org" , Gleb Natapov , kvm-devel On Sun, Oct 11, 2009 at 07:28:13PM +0200, Avi Kivity wrote: > On 10/11/2009 07:27 PM, Avi Kivity wrote: >> So we are fine then? After reset new BIOS will get used? >> >> Yes. >> > > I meant, we are fine for upgrade, and no, the new BIOS will not be used. > The file is only read once. So this is what happens: - after migration from old qemu to new old BIOS is used until reset - after reset new BIOS is used - after upgrade from old version of qemu upgrade does not have any effect until qemu is restarted If this is a fair summary, the only issue with fixing BIOS bug is migration from new qemu to old qemu, and we do not care much. > -- > Do not meddle in the internals of kernels, for they are subtle and quick to panic.