From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NKus9-0002UK-S7
	for qemu-devel@nongnu.org; Wed, 16 Dec 2009 09:29:02 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NKus5-0002Sp-18
	for qemu-devel@nongnu.org; Wed, 16 Dec 2009 09:29:01 -0500
Received: from [199.232.76.173] (port=41836 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NKus3-0002SW-5l
	for qemu-devel@nongnu.org; Wed, 16 Dec 2009 09:28:56 -0500
Received: from mx1.redhat.com ([209.132.183.28]:57576)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <gleb@redhat.com>) id 1NKus2-00025S-PC
	for qemu-devel@nongnu.org; Wed, 16 Dec 2009 09:28:55 -0500
Date: Wed, 16 Dec 2009 16:28:49 +0200
From: Gleb Natapov <gleb@redhat.com>
Subject: Re: Proper support for PCI-based option rom loading (was Re:
	[Qemu-devel] Re: qdev property bug?)
Message-ID: <20091216142849.GF11219@redhat.com>
References: <4B27DF1A.3030000@codemonkey.ws> <4B28CC7A.7000100@redhat.com>
	<20091216123944.GA29289@redhat.com> <4B28E3DB.2030106@redhat.com>
	<20091216135234.GA29589@redhat.com>
	<20091216141221.GA27942@morn.localdomain>
	<20091216141711.GD11219@redhat.com>
	<20091216141516.GB29661@redhat.com>
	<20091216141849.GE11219@redhat.com>
	<20091216142459.GC29661@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20091216142459.GC29661@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: glommer@redhat.com, seabios@seabios.org, qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>, Kevin O'Connor <kevin@koconnor.net>, Gerd Hoffmann <kraxel@redhat.com>, Sebastian Herbszt <herbszt@gmx.de>

On Wed, Dec 16, 2009 at 04:24:59PM +0200, Michael S. Tsirkin wrote:
> On Wed, Dec 16, 2009 at 04:18:49PM +0200, Gleb Natapov wrote:
> > On Wed, Dec 16, 2009 at 04:15:16PM +0200, Michael S. Tsirkin wrote:
> > > On Wed, Dec 16, 2009 at 04:17:11PM +0200, Gleb Natapov wrote:
> > > > On Wed, Dec 16, 2009 at 09:12:21AM -0500, Kevin O'Connor wrote:
> > > > > On Wed, Dec 16, 2009 at 03:52:34PM +0200, Michael S. Tsirkin wrote:
> > > > > > I am mostly concerned with migrating between qemu versions with
> > > > > > different roms, while guest was in the middle of running ROM.
> > > > > > This might be solved if we migrated ROM content together with
> > > > > > the device and put some padding in ROM content so that
> > > > > > size can be kept constant.
> > > > > 
> > > > > SeaBIOS will always copy the roms into the 0xc0000-0xf0000 memory area
> > > > > (regardless of CONFIG_OPTIONROMS_DEPLOYED).  So, if one migrates a
> > > > > machine while running a rom, the memory holding the rom should get
> > > > > migrated with everything else.
> > > > > 
> > > > Yes, but if migration happens in the middle of the copying...
> > > 
> > > Yes. This is not a new bug though.
> > > 
> > How so?
> 
> BIOS already reads roms from devices, does it not?
No it doesn't.

> If we migrate in the middle of this process to
> a device with a different ROM, tough.
> 
> > --
> > 			Gleb.

--
			Gleb.