From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NKBXT-00073m-PF for qemu-devel@nongnu.org; Mon, 14 Dec 2009 09:04:39 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NKBXO-0006xO-V5 for qemu-devel@nongnu.org; Mon, 14 Dec 2009 09:04:39 -0500 Received: from [199.232.76.173] (port=42236 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NKBXO-0006x8-LB for qemu-devel@nongnu.org; Mon, 14 Dec 2009 09:04:34 -0500 Received: from mx1.redhat.com ([209.132.183.28]:44534) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NKBXN-0007px-C9 for qemu-devel@nongnu.org; Mon, 14 Dec 2009 09:04:33 -0500 Date: Mon, 14 Dec 2009 16:01:43 +0200 From: "Michael S. Tsirkin" Subject: Re: [Qemu-devel] Re: qdev property bug? Message-ID: <20091214140143.GO973@redhat.com> References: <20091213200259.GB25615@redhat.com> <4B260683.8000506@redhat.com> <20091214093414.GA30459@redhat.com> <4B26090B.8010707@redhat.com> <20091214094406.GB32140@redhat.com> <4B261082.4030806@redhat.com> <20091214105912.GA32355@redhat.com> <1913984B-EF3F-4974-830A-DF97B8410AA6@suse.de> <20091214132423.GB973@redhat.com> <4B263F23.2090601@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B263F23.2090601@suse.de> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: "glommer@redhat.com" , "qemu-devel@nongnu.org" , Kevin O'Connor , Gerd Hoffmann , Sebastian Herbszt On Mon, Dec 14, 2009 at 02:35:31PM +0100, Alexander Graf wrote: > Michael S. Tsirkin wrote: > > On Mon, Dec 14, 2009 at 12:55:28PM +0100, Alexander Graf wrote: > > > >> Am 14.12.2009 um 11:59 schrieb "Michael S. Tsirkin" : > >> > >> > >>> On Mon, Dec 14, 2009 at 11:16:34AM +0100, Gerd Hoffmann wrote: > >>> > >>>> On 12/14/09 10:44, Michael S. Tsirkin wrote: > >>>> > >>>>> No, it did not even start booting the kernel. Just gave me blank > >>>>> screen. > >>>>> > >>>> [ testing ] > >>>> > >>>> Oh. That is something completely different. A bug in the rom > >>>> loader. > >>>> It fails to fit both e1000 (default nic) and virtio-net boot roms > >>>> into > >>>> the option rom area and bails out (before loading seabios). vl.c > >>>> doesn't check the return value and happily continues (without bios). > >>>> Which doesn't work out very well ... > >>>> > >>>> With two identical nics the (single) rom fits and qemu boots. > >>>> > >>>> Hmm. Of course vl.c must be fixed to check the return value. > >>>> > >>> Yes. > >>> > >>> > >>>> Not sure how to deal with the rom size issue. The gPXE roms look > >>>> quit > >>>> big compared to the older roms we had. > >>>> > >>> Hmm, it's a regression then ... > >>> > >> How does real hw handle this? I'm pretty sure most servers these days > >> use more option rom space than this. They usually have some onboard raid > >> bios, external storage, on-board nic, pci nic, ... > >> > > > > Real hardware might do several things I know about > > - option rom is typically small. > > - option rom is not loaded always (BIOS option), or not for all cards. > > There are might be other tricks. > > > > There are probably other tricks. I was booting up a machine that had > like 5 options roms going through their initialization that all weren't > exactly small. This might boil down to better ROMs. E.g. maybe they request memory with PMM and then give it up after initialization? > >> So there must be some way to just have more option rom space. > >> > > > > What do you mean? > > > > Well, what's keeping us from having 5 MB of option roms? > > >> Implementing anything else would just be a waste of time. It'd break > >> again when ppl do device assignment. > >> > >> Alex > >> > > > > We need some solution for 0.12 though IMO. > > This does not need to address device assignment, > > but it must be simple. > > > > Agreed. If there is a solution that gives us the chance to support an > arbitrary number of option roms that wouldn't take forever to implement, > I'd rather take that one though. > > Alex