From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=36729 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OgKkV-0004XZ-9a for qemu-devel@nongnu.org; Tue, 03 Aug 2010 12:54:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OgKk3-0001f1-K6 for qemu-devel@nongnu.org; Tue, 03 Aug 2010 12:53:28 -0400 Received: from mail-qy0-f180.google.com ([209.85.216.180]:36966) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OgKk3-0001ep-EP for qemu-devel@nongnu.org; Tue, 03 Aug 2010 12:53:27 -0400 Received: by qyk31 with SMTP id 31so1352798qyk.4 for ; Tue, 03 Aug 2010 09:53:26 -0700 (PDT) Message-ID: <4C584982.5000108@codemonkey.ws> Date: Tue, 03 Aug 2010 11:53:22 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Anyone seeing huge slowdown launching qemu with Linux 2.6.35? References: <20100803111306.GA21886@amd.home.annexia.org> <20100803113302.GT24773@redhat.com> <20100803121000.GV13789@amd.home.annexia.org> <20100803123714.GU24773@redhat.com> <20100803124808.GW13789@amd.home.annexia.org> <4C58176B.2050306@redhat.com> <20100803140506.GD22211@amd.home.annexia.org> <4C5829E1.60004@redhat.com> <20100803145337.GF22211@amd.home.annexia.org> <4C583F6A.7030600@redhat.com> <20100803162857.GX13789@amd.home.annexia.org> <4C584781.9040609@redhat.com> <4C5847CD.9080107@codemonkey.ws> <4C5848C7.3090806@redhat.com> In-Reply-To: <4C5848C7.3090806@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: Avi Kivity Cc: kvm@vger.kernel.org, "Richard W.M. Jones" , Gleb Natapov , qemu-devel@nongnu.org On 08/03/2010 11:50 AM, Avi Kivity wrote: > On 08/03/2010 07:46 PM, Anthony Liguori wrote: >>> It doesn't appear to support live migration, or hiding the feature >>> for -M older. >>> >>> It's not a good path to follow. Tomorrow we'll need to load 300MB >>> initrds and we'll have to rework this yet again. Meanwhile the >>> kernel and virtio support demand loading of any image size you'd >>> want to use. >> >> >> firmware is totally broken with respect to -M older FWIW. >> > > Well, then this is adding to the brokenness. > > fwcfg dma is going to have exactly one user, libguestfs. Much better > to have libguestfs move to some other interface and improve are > users-to-interfaces ratio. You mean, only one class of users cares about the performance of loading an initrd. However, you've also argued in other threads how important it is not to break libvirt even if it means we have to do silly things (like change help text). So... why is it that libguestfs has to change itself and yet we should bend over backwards so libvirt doesn't have to change itself? Regards, Anthony Liguori