From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NLgEu-0002AK-NY for qemu-devel@nongnu.org; Fri, 18 Dec 2009 12:03:40 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NLgEp-00024u-9X for qemu-devel@nongnu.org; Fri, 18 Dec 2009 12:03:39 -0500 Received: from [199.232.76.173] (port=48516 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NLgEo-00024l-S7 for qemu-devel@nongnu.org; Fri, 18 Dec 2009 12:03:34 -0500 Received: from mx1.redhat.com ([209.132.183.28]:2060) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NLgEo-0007sr-71 for qemu-devel@nongnu.org; Fri, 18 Dec 2009 12:03:34 -0500 Message-ID: <4B2BB5E0.9010701@redhat.com> Date: Fri, 18 Dec 2009 18:03:28 +0100 From: Gerd Hoffmann MIME-Version: 1.0 References: <1261134074-11795-1-git-send-email-kraxel@redhat.com> <4B2B9340.1020001@codemonkey.ws> <4B2BAF25.2070800@redhat.com> <4B2BB0E8.7060907@codemonkey.ws> In-Reply-To: <4B2BB0E8.7060907@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [SeaBIOS] [PATCH 0/8] option rom loading overhaul. List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: qemu-devel@nongnu.org On 12/18/09 17:42, Anthony Liguori wrote: >> Do we need to do something for -M pc-0.11? Like loading the pci roms >> via fw_cfg too so the guest doesn't see the new pci rom bar? > > Yes, we do. We can fix that problem as a stable-0.12 update though. > Right now, migration with pc-0.11 is broken in other areas too. Ok. When it is fine to defer this to stable-0.12 then I have no objections to merge it for 0.12 (assuming the seabios folks ack+merge the seabios changes). Note that I'll be offline for x-mas and newyear starting tomorrow, so I will not be able to work on that until January. > It's really unclear to me the best way to handle live migration. The > rom_offset is not enough because unfortunately it's not stable after > invocations of qemu. I think we're going to have to actually save the > some contents with the PCIDevices. With hotplug this will become a issue indeed. >> Is 0.11 -> 0.12 migration supposed to work? That could become quite >> nasty too. But maybe that is impossible anyway due to the switch to >> seabios? > > In theory, it should work. SeaBIOS should not be a guest visible change > because the guest should not depend on what BIOS we're using. Indeed. In theory even the switch of the option rom loading should work just fine. After migration old bios and roms are still in memory, the next reboot will be the world switch to new seabios, new roms, new way to deploy roms and everything. Lets see how this works out in practice ... cheers, Gerd