From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=35125 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OgfJY-0001zd-O8 for qemu-devel@nongnu.org; Wed, 04 Aug 2010 10:51:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OgfJW-0003DA-T3 for qemu-devel@nongnu.org; Wed, 04 Aug 2010 10:51:28 -0400 Received: from sj-iport-1.cisco.com ([171.71.176.70]:12168) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OgfJW-0003Cn-Ng for qemu-devel@nongnu.org; Wed, 04 Aug 2010 10:51:26 -0400 Message-ID: <4C597E6D.1040609@cisco.com> Date: Wed, 04 Aug 2010 08:51:25 -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: <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> <4C584982.5000108@codemonkey.ws> <4C584B66.5070404@redhat.com> <4C5854F1.3000905@codemonkey.ws> <4C5858B2.9090801@redhat.com> <4C585F5B.5070502@codemonkey.ws> <4C58635B.7020407@redhat.com> In-Reply-To: <4C58635B.7020407@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: qemu-devel@nongnu.org, Gleb Natapov , kvm@vger.kernel.org, "Richard W.M. Jones" On 08/03/10 12:43, Avi Kivity wrote: > libguestfs does not depend on an x86 architectural feature. > qemu-system-x86_64 emulates a PC, and PCs don't have -kernel. We should > discourage people from depending on this interface for production use. That is a feature of qemu - and an important one to me as well. Why should it be discouraged? You end up at the same place -- a running kernel and in-ram filesystem; why require going through a bootloader just because the hardware case needs it? David