From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: Re: [Qemu-devel] Re: [PATCH 2/3] qemu: make cirrus init value pci spec compliant Date: Sun, 11 Oct 2009 16:35:35 +0200 Message-ID: <20091011143535.GA10401@redhat.com> References: <20091008145241.GC12275@redhat.com> <4ACE0559.5040206@redhat.com> <20091008160623.GA13710@redhat.com> <4ACE0FC6.3050908@redhat.com> <20091008184011.GA6576@shareable.org> <20091011133626.GA10229@redhat.com> <20091011134559.GN16702@redhat.com> <20091011135240.GA10277@redhat.com> <20091011135748.GO16702@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jamie Lokier , Avi Kivity , Anthony Liguori , "qemu-devel@nongnu.org" , kvm-devel To: Gleb Natapov Return-path: Received: from mx1.redhat.com ([209.132.183.28]:29711 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753083AbZJKOiN (ORCPT ); Sun, 11 Oct 2009 10:38:13 -0400 Content-Disposition: inline In-Reply-To: <20091011135748.GO16702@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Sun, Oct 11, 2009 at 03:57:48PM +0200, Gleb Natapov wrote: > On Sun, Oct 11, 2009 at 03:52:40PM +0200, Michael S. Tsirkin wrote: > > On Sun, Oct 11, 2009 at 03:45:59PM +0200, Gleb Natapov wrote: > > > On Sun, Oct 11, 2009 at 03:36:26PM +0200, Michael S. Tsirkin wrote: > > > > > No, I think Avi was right the first time. > > > > > > > > > > Migrating from an older qemu will be fine at first, but at the next > > > > > reset _following_ migration, it'll be running the old BIOS on a new > > > > > qemu and fail. > > > > > > > > > > -- Jamie > > > > > > > > So after discussion with Gleb, it seems that what will happen > > > > after migration to new qemu, old BIOS is shadowed, but memory > > > > is already enabled. After reset, new BIOS will be shadowed > > > > and it will enable memory. Makes sense? > > > > > > > I don't see how you made this conclusion after the discussion. > > > What should happen is after migration old bios should be used until reboot. > > > After reboot new bios should be used. > > > > I think that's what I said. > > > First shadowing bios has nothing to do with it. Second what do you mean > by "will happen"? That is how code works now or that is how it should > work? I am not sure this is how it works. No, this is not how it works, I think. Currently BIOS ROM is loaded only on init, directly into qemu memory. BTW, I don't think it's write-protected and it probably should be? > > -- > Gleb.