From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NKuiR-0008Fn-9A for qemu-devel@nongnu.org; Wed, 16 Dec 2009 09:18:59 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NKuiM-0008Ct-Lj for qemu-devel@nongnu.org; Wed, 16 Dec 2009 09:18:58 -0500 Received: from [199.232.76.173] (port=44526 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NKuiM-0008Cf-5S for qemu-devel@nongnu.org; Wed, 16 Dec 2009 09:18:54 -0500 Received: from mx1.redhat.com ([209.132.183.28]:15655) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NKuiL-0001If-Pr for qemu-devel@nongnu.org; Wed, 16 Dec 2009 09:18:54 -0500 Date: Wed, 16 Dec 2009 16:18:49 +0200 From: Gleb Natapov Subject: Re: Proper support for PCI-based option rom loading (was Re: [Qemu-devel] Re: qdev property bug?) Message-ID: <20091216141849.GE11219@redhat.com> References: <4B27541F.9020603@redhat.com> <4B276197.1080606@redhat.com> <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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091216141516.GB29661@redhat.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: glommer@redhat.com, seabios@seabios.org, qemu-devel@nongnu.org, Alexander Graf , Kevin O'Connor , Gerd Hoffmann , Sebastian Herbszt 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? -- Gleb.