From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=39133 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OnSmI-0008Gf-Jz for qemu-devel@nongnu.org; Mon, 23 Aug 2010 04:53:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OnSmG-0000eZ-Sw for qemu-devel@nongnu.org; Mon, 23 Aug 2010 04:53:14 -0400 Received: from mx1.redhat.com ([209.132.183.28]:64532) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OnSmG-0000eP-LW for qemu-devel@nongnu.org; Mon, 23 Aug 2010 04:53:12 -0400 Message-ID: <4C7236E8.2090908@redhat.com> Date: Mon, 23 Aug 2010 10:52:56 +0200 From: Gerd Hoffmann MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH - V3] Port codes from qemu-kvm to support booting from SCSI disk image References: <201008181608.55759.paul@codesourcery.com> <632E0D52-7618-4184-990D-2918E51A61BC@suse.de> <4C6E327B.4060505@redhat.com> <4C6E8647.9090509@codemonkey.ws> <4C6E8C80.3020903@redhat.com> <4C6E938E.80704@codemonkey.ws> <20100821142058.GA17139@morn.localdomain> In-Reply-To: <20100821142058.GA17139@morn.localdomain> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kevin O'Connor Cc: Paul Brook , Hai Shan Bai , qemu-devel@nongnu.org, Alexander Graf On 08/21/10 16:20, Kevin O'Connor wrote: > On Fri, Aug 20, 2010 at 09:39:10AM -0500, Anthony Liguori wrote: >> On 08/20/2010 09:09 AM, Gerd Hoffmann wrote: >>> Been there, tried that. It isn't *that* easy. The PCI ID in the >>> option rom header doesn't match the PCI ID of the emulated lsi, so >>> seabios refuses to load it from the rom bar. >> >> Heh, I was wondering why it didn't work unless I put rombar=0 :-) >> >> Is this fixable in a reasonable way or does PCI ID in the option rom >> represent a much newer device that would trigger issues with guest >> drivers? > > The PCI spec requires that the PCI IDs match - this is done so that a > single rom can store multiple optionroms. > > One could place the optionrom in fw_cfg with a "file" name of > "pciXXXX,YYYY.rom". SeaBIOS will then deploy that rom for every > device that has the given vendor/devid. (It wont require matching PCI > IDs ids in the rom.) Yea, this is exactly what "rombar=0" (property for pci devices) does: load the rom via fw_cfg instead of using the pci option rom bar ;) cheers, Gerd