From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NMcka-0002Rw-N0 for qemu-devel@nongnu.org; Mon, 21 Dec 2009 02:32:16 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NMckU-0002Qb-VU for qemu-devel@nongnu.org; Mon, 21 Dec 2009 02:32:14 -0500 Received: from [199.232.76.173] (port=37860 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NMckT-0002QQ-Q5 for qemu-devel@nongnu.org; Mon, 21 Dec 2009 02:32:10 -0500 Received: from mx1.redhat.com ([209.132.183.28]:29078) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NMckT-0007iQ-FU for qemu-devel@nongnu.org; Mon, 21 Dec 2009 02:32:09 -0500 Date: Mon, 21 Dec 2009 09:32:04 +0200 From: Gleb Natapov Subject: Re: [Qemu-devel] Re: [SeaBIOS] [PATCH 0/8] option rom loading overhaul. Message-ID: <20091221073204.GS4490@redhat.com> References: <4B2E3BA0.7080004@codemonkey.ws> <20091220150751.GL4490@redhat.com> <4B2E3E96.7090708@codemonkey.ws> <20091220152346.GM4490@redhat.com> <4B2E42A2.6030600@codemonkey.ws> <20091220153347.GN4490@redhat.com> <4B2E453A.3060004@codemonkey.ws> <20091220155201.GP4490@redhat.com> <4B2E6364.9060903@codemonkey.ws> <20091221015948.GA23556@morn.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091221015948.GA23556@morn.localdomain> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kevin O'Connor Cc: Gerd Hoffmann , qemu-devel@nongnu.org On Sun, Dec 20, 2009 at 08:59:48PM -0500, Kevin O'Connor wrote: > On Sun, Dec 20, 2009 at 11:48:20AM -0600, Anthony Liguori wrote: > > I think we have two ways to view firmware. The first would be to treat > > guest firmware as part of the guest. What that means it that we should > > store all firmware in an nvram file, migrate the nvram file during > > migration > [...] > > The other option would be to treat guest firmware as part of the machine > > state. > > How about mixing the two? Store the firmware in an nvram file and > migrate it during migration, but clear the nvram and reload the > firmware on each start-up and qemu reset. > That's precisely what I propose. > [...] > >The second mechanism is > > appealing from an ease of use perspective but the semantics of doing a > > live migration and getting a different firmware after reset/shutdown is > > rather scary from a support perspective. > > I'm not sure I see the problem with upgrading firmware on a reboot. I > think it would be a pretty severe bug if a new firmware broke the OS > or if an OS was heavily dependent on a specific firmware across > reboots. After all, normal users update their bios and reboot into > pre-existing OSs all the time. > Exactly. -- Gleb.