From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: qemu oddness with isolinux vesamenu.c32 Date: Mon, 21 Jul 2008 05:51:06 -0700 Message-ID: <4884863A.2030609@zytor.com> References: <48800A9D.1080403@zytor.com> <4880C3F3.6010202@zytor.com> <488199AB.4020109@qumranet.com> <488232A4.1010706@zytor.com> <488298A3.9050502@zytor.com> <48845A2C.4050306@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Matt_Domsch@Dell.com, pjones@redhat.com, kvm@vger.kernel.org, Anthony Liguori To: Avi Kivity Return-path: Received: from terminus.zytor.com ([198.137.202.10]:53271 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751087AbYGUMza (ORCPT ); Mon, 21 Jul 2008 08:55:30 -0400 In-Reply-To: <48845A2C.4050306@qumranet.com> Sender: kvm-owner@vger.kernel.org List-ID: Avi Kivity wrote: > H. Peter Anvin wrote: >> H. Peter Anvin wrote: >>> >>> Yes, although simulating the memory "pre-shadowed" works just as >>> well; then it should be marked readonly by the BIOS immediately prior >>> to running INT 19h. >> >> On top of this, getting proper DDIM support and PCI expansion ROM into >> the BIOS would be a good thing. A PCI expansion ROM is attached to a >> PCI device as a BAR and mapped into high memory, it is then copied to >> shadowed RAM by the BIOS and its initialization stub is run. This is >> done one device at a time, so that the initialization code can be >> discarded, per the DDIM spec. > > I imagine it's necessary for proper pci device assignment. > Well, if nothing else it would permit PCI device ROMs to work unmodified. I was rather disappointed when I found out I couldn't simulate PXE ROMs, even from devices which we can emulate. -hpa