From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=44739 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Oh2T9-0006Wa-3P for qemu-devel@nongnu.org; Thu, 05 Aug 2010 11:34:56 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Oh2T8-0004f0-3F for qemu-devel@nongnu.org; Thu, 05 Aug 2010 11:34:54 -0400 Received: from mail-yw0-f45.google.com ([209.85.213.45]:56784) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Oh2T8-0004ef-0w for qemu-devel@nongnu.org; Thu, 05 Aug 2010 11:34:54 -0400 Received: by ywt2 with SMTP id 2so2754770ywt.4 for ; Thu, 05 Aug 2010 08:34:53 -0700 (PDT) Message-ID: <4C5ABFFF.4010108@codemonkey.ws> Date: Thu, 05 Aug 2010 08:43:27 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Anyone seeing huge slowdown launching qemu with Linux 2.6.35? References: <20100803190525.GB16570@redhat.com> <4C586AB9.5040302@codemonkey.ws> <4C586CF9.7030206@redhat.com> <4C588804.5060803@redhat.com> <4C590046.2020705@redhat.com> <4C591D48.9080301@redhat.com> <4C592218.3000901@redhat.com> <4C596549.1070109@codemonkey.ws> <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> In-Reply-To: <4C5A6839.2070700@redhat.com> 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: Gerd Hoffmann Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, Avi Kivity , Gleb Natapov , "Richard W.M. Jones" On 08/05/2010 02:28 AM, 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. Well, extboot doesn't hijack int19, it hijacks int13. It'll appear as the disk 0x80. It would be better though to do a BCV rom such that the extboot disk appeared as an independent disk instead of hijacking disk 0x80. linuxboot/multiboot should be BEV roms, no doubt. Regards, Anthony Liguori > cheers, > Gerd >