From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=35062 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OgkEz-0005xu-C1 for qemu-devel@nongnu.org; Wed, 04 Aug 2010 16:07:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OgkEy-0002Cx-6R for qemu-devel@nongnu.org; Wed, 04 Aug 2010 16:07:05 -0400 Received: from sj-iport-5.cisco.com ([171.68.10.87]:37399) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OgkEy-0002CW-1P for qemu-devel@nongnu.org; Wed, 04 Aug 2010 16:07:04 -0400 Message-ID: <4C59C862.60608@cisco.com> Date: Wed, 04 Aug 2010 14:06:58 -0600 From: "David S. Ahern" 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> <721C3046-D6A7-47B2-A18C-4E59F2B68797@suse.de> <4C599B45.6030808@redhat.com> <966B1FAB-7E03-4EA6-AC74-767FC400A9CC@suse.de> <4C599FF3.5070208@redhat.com> <3A326B27-9204-4733-A9B6-25EC44291499@suse.de> <4C59A491.7020904@redhat.com> In-Reply-To: <4C59A491.7020904@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Alexander Graf , kvm@vger.kernel.org, Gleb Natapov , qemu-devel@nongnu.org, "Richard W.M. Jones" , Gerd Hoffmann On 08/04/10 11:34, Avi Kivity wrote: >> And it's awesome for fast prototyping. Of course, once that fast >> becomes dog slow, it's not useful anymore. > > For the Nth time, it's only slow with 100MB initrds. 100MB is really not that large for an initrd. Consider the deployment of stateless nodes - something that virtualization allows the rapid deployment of. 1 kernel, 1 initrd with the various binaries to be run. Create nodes as needed by launching a shell command - be it for more capacity, isolation, etc. Why require an iso or disk wrapper for a binary blob that is all to be run out of memory? The -append argument allows boot parameters to be specified at launch. That is a very powerful and simple design option. David