From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=38382 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Ogf5a-0000zQ-70
	for qemu-devel@nongnu.org; Wed, 04 Aug 2010 10:37:04 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <gleb@redhat.com>) id 1Ogf5Y-00010z-VI
	for qemu-devel@nongnu.org; Wed, 04 Aug 2010 10:37:02 -0400
Received: from mx1.redhat.com ([209.132.183.28]:26952)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <gleb@redhat.com>) id 1Ogf5Y-00010V-Ii
	for qemu-devel@nongnu.org; Wed, 04 Aug 2010 10:37:00 -0400
Date: Wed, 4 Aug 2010 17:36:55 +0300
From: Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] Anyone seeing huge slowdown launching qemu with
	Linux 2.6.35?
Message-ID: <20100804143655.GW10499@redhat.com>
References: <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>
	<4C5975A9.1070108@codemonkey.ws>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4C5975A9.1070108@codemonkey.ws>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, "Richard W.M. Jones" <rjones@redhat.com>, Avi Kivity <avi@redhat.com>, kvm@vger.kernel.org, Gerd Hoffmann <kraxel@redhat.com>

On Wed, Aug 04, 2010 at 09:14:01AM -0500, Anthony Liguori wrote:
> >Unmapping device and mapping it at the same place is easy. Enumerating
> >pci devices from multiboot.bin looks like unneeded churn though.
> >
> >>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?
> 
> No, I forgot just how small they are.  R/O usb mass storage device?
> CDROM?  I'm beginning thing that loading such a large initrd through
> fwcfg is simply a dead end.
> 
Well, libguestfs can use CDROM by itself to begin with.

--
			Gleb.