From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NKAxJ-0004uP-GP for qemu-devel@nongnu.org; Mon, 14 Dec 2009 08:27:17 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NKAxE-0004om-MA for qemu-devel@nongnu.org; Mon, 14 Dec 2009 08:27:16 -0500 Received: from [199.232.76.173] (port=53950 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NKAxE-0004oC-Ap for qemu-devel@nongnu.org; Mon, 14 Dec 2009 08:27:12 -0500 Received: from mx1.redhat.com ([209.132.183.28]:7093) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NKAxD-0003JQ-Fz for qemu-devel@nongnu.org; Mon, 14 Dec 2009 08:27:11 -0500 Date: Mon, 14 Dec 2009 15:24:23 +0200 From: "Michael S. Tsirkin" Subject: Re: [Qemu-devel] Re: qdev property bug? Message-ID: <20091214132423.GB973@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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1913984B-EF3F-4974-830A-DF97B8410AA6@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" , Sebastian Herbszt , Gerd Hoffmann , "qemu-devel@nongnu.org" 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. > So there must be some way to just have more option rom space. What do you mean? > 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. -- MST