From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mx5EG-0006PM-90 for qemu-devel@nongnu.org; Sun, 11 Oct 2009 16:41:20 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mx5EB-0006Kl-96 for qemu-devel@nongnu.org; Sun, 11 Oct 2009 16:41:19 -0400 Received: from [199.232.76.173] (port=39158 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mx5EA-0006KM-UO for qemu-devel@nongnu.org; Sun, 11 Oct 2009 16:41:15 -0400 Received: from mx1.redhat.com ([209.132.183.28]:61719) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mx5EA-0007xx-GX for qemu-devel@nongnu.org; Sun, 11 Oct 2009 16:41:14 -0400 Message-ID: <4AD242E7.1080705@redhat.com> Date: Sun, 11 Oct 2009 22:41:11 +0200 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [PATCH 2/3] qemu: make cirrus init value pci spec compliant 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> <20091011181024.GA6411@redhat.com> In-Reply-To: <20091011181024.GA6411@redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: Anthony Liguori , "qemu-devel@nongnu.org" , Gleb Natapov , kvm-devel On 10/11/2009 08:10 PM, Michael S. Tsirkin wrote: > > 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. > Yes. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.