From mboxrd@z Thu Jan  1 00:00:00 1970
From: Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH 2/3] qemu: make cirrus init value pci
 spec compliant
Date: Mon, 12 Oct 2009 16:52:56 +0200
Message-ID: <20091012145256.GF3026@redhat.com>
References: <20091008160623.GA13710@redhat.com>
 <4ACE0FC6.3050908@redhat.com>
 <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>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	Jamie Lokier <jamie@shareable.org>,
	Avi Kivity <avi@redhat.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	kvm-devel <kvm@vger.kernel.org>
To: Gerd Hoffmann <kraxel@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:60248 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S932401AbZJLOx3 (ORCPT <rfc822;kvm@vger.kernel.org>);
	Mon, 12 Oct 2009 10:53:29 -0400
Content-Disposition: inline
In-Reply-To: <4AD3423B.3020908@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Mon, Oct 12, 2009 at 04:50:35PM +0200, Gerd Hoffmann wrote:
> On 10/12/09 15:53, Gleb Natapov wrote:
> >On Mon, Oct 12, 2009 at 03:45:47PM +0200, Gerd Hoffmann wrote:
> >>>>>>We should fix qemu to re-read bios from flash.
> >>>>>>Makes sense?
> >>>>>>
> >>>>>We have option_rom_setup_reset() already.
> >>>>
> >>>>We don't, anymore :)
> >>>We are fast! Well, we surely have something similar instead.
> >>
> >>Sure.  Try 'info roms'.  Everything listed there will be reloaded on
> >>reset (unless mem=rom, in which case the guest should not be able to
> >>modify the bits in the first place).  That includes vgabios,
> >>optionroms, -kernel images, ...
> >>
> >And what about bios? I don't see it there.
> 
> 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.

--
			Gleb.