From mboxrd@z Thu Jan  1 00:00:00 1970
From: Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] Anyone seeing huge slowdown launching qemu with
 Linux 2.6.35?
Date: Wed, 04 Aug 2010 09:39:12 -0500
Message-ID: <4C597B90.30602@codemonkey.ws>
References: <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> <20100804140011.GR10499@redhat.com> <4C5977B7.9020008@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Gleb Natapov <gleb@redhat.com>, Avi Kivity <avi@redhat.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	"Richard W.M. Jones" <rjones@redhat.com>, qemu-devel@nongnu.org,
	kvm@vger.kernel.org
To: Paolo Bonzini <pbonzini@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mail-qy0-f181.google.com ([209.85.216.181]:64559 "EHLO
	mail-qy0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S932838Ab0HDOjR (ORCPT <rfc822;kvm@vger.kernel.org>);
	Wed, 4 Aug 2010 10:39:17 -0400
Received: by qyk7 with SMTP id 7so1785946qyk.19
        for <kvm@vger.kernel.org>; Wed, 04 Aug 2010 07:39:16 -0700 (PDT)
In-Reply-To: <4C5977B7.9020008@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On 08/04/2010 09:22 AM, Paolo Bonzini wrote:
> On 08/04/2010 04:00 PM, Gleb Natapov wrote:
>>> Maybe we're just being too fancy here.
>>>
>>> We could rewrite -kernel/-append/-initrd to just generate a floppy
>>> image in RAM, and just boot from floppy.
>>>
>> May be. Can floppy be 100M?
>
> Well, in theory you can have 16384 bytes/sector, 256 tracks, 255 
> sectors, 2 heads... that makes 2^(14+8+8+1) = 2 GB. :)  Not sure the 
> BIOS would read such a beast, or SYSLINUX.
>
> By the way, if libguestfs insists for an initrd rather than a CDROM 
> image, it could do something in between and make an ISO image with 
> ISOLINUX and the required kernel/initrd pair.
>
> (By the way, a network installation image for a typical distribution 
> has a 120M initrd, so it's not just libguestfs.  It is very useful to 
> pass the network installation images directly to qemu via 
> -kernel/-initrd).

We could make kernel an awful lot smarter but unless we've got someone 
just itching to write 16-bit option rom code, I think our best bet is to 
try to leverage a standard bootloader and expose a disk containing the 
kernel/initrd.

Otherwise, we just stick with what we have and deal with the performance 
as is.

Regards,

Anthony Liguori

>
> Paolo