From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NKikd-00073n-Hh for qemu-devel@nongnu.org; Tue, 15 Dec 2009 20:32:27 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NKikY-0006zw-NI for qemu-devel@nongnu.org; Tue, 15 Dec 2009 20:32:27 -0500 Received: from [199.232.76.173] (port=43084 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NKikY-0006zt-Gp for qemu-devel@nongnu.org; Tue, 15 Dec 2009 20:32:22 -0500 Received: from mail-iw0-f197.google.com ([209.85.223.197]:43604) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NKikY-000534-8a for qemu-devel@nongnu.org; Tue, 15 Dec 2009 20:32:22 -0500 Received: by iwn35 with SMTP id 35so362774iwn.4 for ; Tue, 15 Dec 2009 17:32:21 -0800 (PST) Message-ID: <4B2838A2.4060701@codemonkey.ws> Date: Tue, 15 Dec 2009 19:32:18 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: Proper support for PCI-based option rom loading (was Re: [Qemu-devel] Re: qdev property bug?) References: <20091214203428.GI6150@redhat.com> <20091214203603.GJ6150@redhat.com> <4B26A3B2.2030006@codemonkey.ws> <20091214205141.GC6398@redhat.com> <4B26F678.4010603@codemonkey.ws> <4B27541F.9020603@redhat.com> <4B276197.1080606@redhat.com> <4B27E518.7060300@codemonkey.ws> <20091215211715.GF26712@redhat.com> <4B28026E.4060100@codemonkey.ws> <20091216003302.GK15084@x200.localdomain> In-Reply-To: <20091216003302.GK15084@x200.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: Chris Wright Cc: "Michael S. Tsirkin" , glommer@redhat.com, seabios@seabios.org, qemu-devel@nongnu.org, Alexander Graf , Kevin O'Connor , Gerd Hoffmann , Sebastian Herbszt Chris Wright wrote: > * Anthony Liguori (anthony@codemonkey.ws) wrote: > >> BTW, I'm pretty sure this style of option rom loading (from a PCI >> device) is going to be required for device passthrough if we want to >> support running those roms in the guests. >> > > I think so too. > > >> In fact, it should Just >> Work with my patches !CONFIG_OPTIONROMS_DEPLOYED in SeaBIOS. >> > > What would be the magic to boot from that ROM? > Setup device assignment, add -boot menu=on with my patches, and hit F12 when prompted. In theory, you should see an entry for the device. If not, the output with DEBUG_BIOS enabled in hw/pc.c would be very interesting. Regards, Anthony Liguori