From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NN6BD-0004y9-Op for qemu-devel@nongnu.org; Tue, 22 Dec 2009 09:57:43 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NN6B9-0004wv-50 for qemu-devel@nongnu.org; Tue, 22 Dec 2009 09:57:43 -0500 Received: from [199.232.76.173] (port=47644 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NN6B8-0004ws-Vu for qemu-devel@nongnu.org; Tue, 22 Dec 2009 09:57:39 -0500 Received: from mail-gx0-f223.google.com ([209.85.217.223]:46623) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NN6B8-0000tz-KQ for qemu-devel@nongnu.org; Tue, 22 Dec 2009 09:57:38 -0500 Received: by gxk23 with SMTP id 23so6535844gxk.2 for ; Tue, 22 Dec 2009 06:57:38 -0800 (PST) Message-ID: <4B30DE56.2070507@codemonkey.ws> Date: Tue, 22 Dec 2009 08:57:26 -0600 From: Anthony Liguori MIME-Version: 1.0 References: <20091221073204.GS4490@redhat.com> <4B2FA518.7000905@codemonkey.ws> <20091221164351.GW4490@redhat.com> <4B2FAFB4.8050102@codemonkey.ws> <20091221174312.GD21163@redhat.com> <1DB151B654AF44C981FA3327A3A514E6@FSCPC> <4B2FC9C3.7040503@codemonkey.ws> <20091221195331.GH21163@redhat.com> <20091222075833.GZ4490@redhat.com> In-Reply-To: <20091222075833.GZ4490@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [SeaBIOS] [PATCH 0/8] option rom loadingoverhaul. List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gleb Natapov Cc: qemu-devel@nongnu.org, Kevin O'Connor , Gerd Hoffmann , Sebastian Herbszt On 12/22/2009 01:58 AM, Gleb Natapov wrote: >> Your cable TV provider does likely also control what beside the FW (if anything) >> runs on your set-top-box. So he can verify the FW upgrade doesn't break anything >> in the field. That pre-deployment verification is not possible in non closed >> environments. >> >> > Yet it doesn't stop HW manufacturers to require FW update as the first > step of their support procedure. They don't do it automatically only > because they can't. > Let's put correctness aside for a moment. Right now, if you replace the contents of pc-bios while you have a guest running, heck, even if you rm -rf, the guest will continue functioning until you do a hard power off. Changing this behavior feels like a regression to me. It really seems to me like it makes things a lot more brittle. The only benefit I can see is that you'll use a new rom after migration after the first reset. Maybe that's desirable behavior although I'm not sure. I'd feel a lot better about something that read the real rom contents at start-up, and then replaced migrated roms after reset or something like that. That gives us the use-case without making qemu depend on rereading things while it's running. Regards, Anthony Liguori