From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MwykT-0002mH-5N
	for qemu-devel@nongnu.org; Sun, 11 Oct 2009 09:46:09 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MwykO-0002fs-CU
	for qemu-devel@nongnu.org; Sun, 11 Oct 2009 09:46:08 -0400
Received: from [199.232.76.173] (port=37690 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MwykO-0002fl-9A
	for qemu-devel@nongnu.org; Sun, 11 Oct 2009 09:46:04 -0400
Received: from mx1.redhat.com ([209.132.183.28]:63572)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <gleb@redhat.com>) id 1MwykN-0005ZD-No
	for qemu-devel@nongnu.org; Sun, 11 Oct 2009 09:46:04 -0400
Date: Sun, 11 Oct 2009 15:45:59 +0200
From: Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH 2/3] qemu: make cirrus init value pci
	spec compliant
Message-ID: <20091011134559.GN16702@redhat.com>
References: <cover.1255013225.git.mst@redhat.com>
	<20091008145241.GC12275@redhat.com> <4ACE0559.5040206@redhat.com>
	<20091008160623.GA13710@redhat.com> <4ACE0FC6.3050908@redhat.com>
	<20091008184011.GA6576@shareable.org>
	<20091011133626.GA10229@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20091011133626.GA10229@redhat.com>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, Avi Kivity <avi@redhat.com>, kvm-devel <kvm@vger.kernel.org>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>

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. What really happens today I don't
know.

--
			Gleb.