From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=51537 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Oh246-0004pe-Le for qemu-devel@nongnu.org; Thu, 05 Aug 2010 11:09:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Oh23h-0004bc-G8 for qemu-devel@nongnu.org; Thu, 05 Aug 2010 11:08:58 -0400 Received: from mx1.redhat.com ([209.132.183.28]:55866) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Oh23h-0004Us-7K for qemu-devel@nongnu.org; Thu, 05 Aug 2010 11:08:37 -0400 Date: Thu, 5 Aug 2010 10:59:50 +0300 From: Gleb Natapov Subject: Re: [Qemu-devel] Anyone seeing huge slowdown launching qemu with Linux 2.6.35? Message-ID: <20100805075950.GI10499@redhat.com> References: <20100804130709.GL10499@redhat.com> <4C5967D8.7080707@codemonkey.ws> <20100804133401.GP10499@redhat.com> <4C5970AC.6060105@codemonkey.ws> <4C5995B4.90505@redhat.com> <4C5996F4.6010205@redhat.com> <4C5998F1.4030001@codemonkey.ws> <4C5A6839.2070700@redhat.com> <20100805073447.GH10499@redhat.com> <4C5A6EC4.2050007@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C5A6EC4.2050007@redhat.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, Gerd Hoffmann , "Richard W.M. Jones" On Thu, Aug 05, 2010 at 10:56:52AM +0300, Avi Kivity wrote: > On 08/05/2010 10:34 AM, Gleb Natapov wrote: > >On Thu, Aug 05, 2010 at 09:28:57AM +0200, Gerd Hoffmann wrote: > >> Hi, > >> > >>>The option rom stuff has a number of short comings. Because we hijack > >>>int19, extboot doesn't get to run. That means that if you use -kernel to > >>>load a grub (the Ubuntu guys for their own absurd reasons) then grub > >>>does not see extboot backed disks. The solution for them is the same, > >>>generate a proper disk and boot from that disk. > >>Oh, having extboot + linuxboot + multiboot register a BEV (correct > >>acronym?) entry instead of hijacking int19 would fix that too. > >>Additional bonus will be that they are selectable in the boot menu. > >> > >Good idea except that we are not good at communicating to seabios where > >do we want to boot from by default. > > We have the firmware configuration interface for that, if we can > tolerate its speed. > To pass default boot device, sure :) The question is what to pass so that seabios will be able to unambiguously determine what device to boot from. -- Gleb.