From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NKuLg-00056W-W2 for qemu-devel@nongnu.org; Wed, 16 Dec 2009 08:55:29 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NKuLc-000542-Vq for qemu-devel@nongnu.org; Wed, 16 Dec 2009 08:55:28 -0500 Received: from [199.232.76.173] (port=60720 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NKuLc-00053z-Qp for qemu-devel@nongnu.org; Wed, 16 Dec 2009 08:55:24 -0500 Received: from mx1.redhat.com ([209.132.183.28]:19891) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NKuLc-00062t-8Q for qemu-devel@nongnu.org; Wed, 16 Dec 2009 08:55:24 -0500 Date: Wed, 16 Dec 2009 15:52:34 +0200 From: "Michael S. Tsirkin" Subject: Re: Proper support for PCI-based option rom loading (was Re: [Qemu-devel] Re: qdev property bug?) Message-ID: <20091216135234.GA29589@redhat.com> References: <20091214203603.GJ6150@redhat.com> <4B26A3B2.2030006@codemonkey.ws> <20091214205141.GC6398@redhat.com> <4B26F678.4010603@codemonkey.ws> <4B27541F.9020603@redhat.com> <4B276197.1080606@redhat.com> <4B27DF1A.3030000@codemonkey.ws> <4B28CC7A.7000100@redhat.com> <20091216123944.GA29289@redhat.com> <4B28E3DB.2030106@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B28E3DB.2030106@redhat.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: glommer@redhat.com, qemu-devel@nongnu.org, Alexander Graf , Kevin O'Connor , Sebastian Herbszt On Wed, Dec 16, 2009 at 02:42:51PM +0100, Gerd Hoffmann wrote: > Hi, > >> What will happen when we find a bug in one of ROMs >> I wonder? I think we will need to keep the old ROM >> around, and put it in as part of compat machine type? > > What do you want? > Old way to load the rom? > Old rom binaries (i.e. etherboot)? > Both? > > The new way to load the roms is a guest-visible change (devices get a > rom bar they had not before), so we might want to have a backward > compatibility property for that. Not sure whenever this is a problem. > > Allowing old ROMs isn't easy as they don't support BEV. > > cheers, > Gerd 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. -- MST