From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=54229 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OgKvN-0008WM-Rt for qemu-devel@nongnu.org; Tue, 03 Aug 2010 13:05:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OgKvM-0003am-KO for qemu-devel@nongnu.org; Tue, 03 Aug 2010 13:05:09 -0400 Received: from mx1.redhat.com ([209.132.183.28]:47081) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OgKvM-0003ac-AJ for qemu-devel@nongnu.org; Tue, 03 Aug 2010 13:05:08 -0400 Received: from int-mx05.intmail.prod.int.phx2.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.18]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o73H57wM023279 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 3 Aug 2010 13:05:07 -0400 Received: from cleopatra.tlv.redhat.com (cleopatra.tlv.redhat.com [10.35.255.11]) by int-mx05.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id o73H56OL028622 for ; Tue, 3 Aug 2010 13:05:07 -0400 Message-ID: <4C584C41.2050108@redhat.com> Date: Tue, 03 Aug 2010 20:05:05 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] Anyone seeing huge slowdown launching qemu with Linux 2.6.35? References: <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> <4C584851.8070105@redhat.com> <20100803170050.GA13789@amd.home.annexia.org> In-Reply-To: <20100803170050.GA13789@amd.home.annexia.org> 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: "Richard W.M. Jones" Cc: qemu-devel@nongnu.org On 08/03/2010 08:00 PM, Richard W.M. Jones wrote: > On Tue, Aug 03, 2010 at 07:48:17PM +0300, Avi Kivity wrote: >> On 08/03/2010 07:44 PM, Avi Kivity wrote: >>> 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. >>> >> Even better would be to use virtio-9p. You don't even need an image >> in this case. > We don't want to expose the whole host filesystem, just selected > files, and we want to use our own configuration files (basically > that's what is in the skeleton part that we do ship). True. The guest might landmine its disks with something that the libguestfs kernel would step on an be exploited. You might hardlink the needed files into a private directory tree. > Of course, if we can use virtio-9p, then excellent. Is there good > documentation about virtio-9p? What I can find is fragmentary or > based on reading qemu -help ... Not to my knowledge. -- error compiling committee.c: too many arguments to function