From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MxOGD-0002Nb-0a for qemu-devel@nongnu.org; Mon, 12 Oct 2009 13:00:37 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MxOG9-0002Gl-2k for qemu-devel@nongnu.org; Mon, 12 Oct 2009 13:00:36 -0400 Received: from [199.232.76.173] (port=53443 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MxOG8-0002GO-M3 for qemu-devel@nongnu.org; Mon, 12 Oct 2009 13:00:32 -0400 Received: from mx1.redhat.com ([209.132.183.28]:5697) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MxOG8-0005wT-3d for qemu-devel@nongnu.org; Mon, 12 Oct 2009 13:00:32 -0400 Date: Mon, 12 Oct 2009 18:57:57 +0200 From: "Michael S. Tsirkin" Subject: Re: [Qemu-devel] Re: [PATCH 2/3] qemu: make cirrus init value pci spec compliant Message-ID: <20091012165757.GA19380@redhat.com> References: <20091008184011.GA6576@shareable.org> <20091009064359.GA9942@redhat.com> <20091009070049.GG19692@redhat.com> <20091009101259.GA12027@redhat.com> <20091009114903.GI19692@redhat.com> <4AD3330B.4090506@redhat.com> <20091012135318.GB3026@redhat.com> <4AD3423B.3020908@redhat.com> <20091012145256.GF3026@redhat.com> <4AD34EAB.5020501@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4AD34EAB.5020501@redhat.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: Anthony Liguori , Gleb Natapov , kvm-devel , "qemu-devel@nongnu.org" , Avi Kivity On Mon, Oct 12, 2009 at 05:43:39PM +0200, Gerd Hoffmann wrote: > On 10/12/09 16:52, Gleb Natapov wrote: >> On Mon, Oct 12, 2009 at 04:50:35PM +0200, Gerd Hoffmann wrote: >>> pc.c does some magic here to map the complete bios into high memory >>> and the legacy part at 0xe0000, thats why it is loaded in a >>> different way. It gets loaded to IO_MEM_ROM memory though, so the >>> guest should not be able to corrupt it. >>> >> But KVM doesn't support it (memory is always writable). And we want to reload >> BIOS on reboot for migration purposes. > > Then it should be switched over to the new rom loader. Also the logic > which does *not* reload stuff which goes to IO_MEM_ROM must be turned > off for kvm them. I think it needs to be turned off anyway. Since ROM is sent over for migration, it might get out of sync with file even if it is read-only. > cheers, > Gerd