From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756207Ab0CXOAj (ORCPT ); Wed, 24 Mar 2010 10:00:39 -0400 Received: from mx1.redhat.com ([209.132.183.28]:39920 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755567Ab0CXOAh (ORCPT ); Wed, 24 Mar 2010 10:00:37 -0400 Message-ID: <4BAA1ADD.9090502@redhat.com> Date: Wed, 24 Mar 2010 15:59:57 +0200 From: Avi Kivity User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100301 Fedora/3.0.3-1.fc12 Thunderbird/3.0.3 MIME-Version: 1.0 To: Alexander Graf CC: Joerg Roedel , Anthony Liguori , Ingo Molnar , Pekka Enberg , "Zhang, Yanmin" , Peter Zijlstra , Sheng Yang , linux-kernel@vger.kernel.org, kvm@vger.kernel.org, Marcelo Tosatti , Jes Sorensen , Gleb Natapov , ziteng.huang@intel.com, Arnaldo Carvalho de Melo , Fr?d?ric Weisbecker , Gregory Haskins Subject: Re: [RFC] Unify KVM kernel-space and user-space code into a single project References: <4BA7B9E0.5080009@codemonkey.ws> <20100322192739.GE21919@elte.hu> <4BA7C96D.2020702@redhat.com> <4BA7E9D9.5060800@codemonkey.ws> <20100323140608.GJ1940@8bytes.org> <4BA8EEDE.8070309@redhat.com> <20100323182153.GA14800@8bytes.org> <4BA99BCB.5080501@redhat.com> <20100324115900.GB14800@8bytes.org> <4BAA00B1.20407@redhat.com> <20100324125043.GC14800@8bytes.org> <4BAA0DFE.1080700@redhat.com> <4BAA1946.6060703@suse.de> In-Reply-To: <4BAA1946.6060703@suse.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/24/2010 03:53 PM, Alexander Graf wrote: > >> Someone needs to know about the new guest to fetch its symbols. Or do >> you want that part in the kernel too? >> > > How about we add a virtio "guest file system access" device? The guest > would then expose its own file system using that device. > > On the host side this would simply be a -virtioguestfs > unix:/tmp/guest.fs and you'd get a unix socket that gives you full > access to the guest file system by using commands. I envision something > like: > The idea is to use a dedicated channel over virtio-serial. If the channel is present the file server can serve files over it. > SEND: GET /proc/version > RECV: Linux version 2.6.27.37-0.1-default (geeko@buildhost) (gcc version > 4.3.2 [gcc-4_3-branch revision 141291] (SUSE Linux) ) #1 SMP 2009-10-15 > 14:56:58 +0200 > > Now all we need is integration in perf to enumerate virtual machines > based on libvirt. If you want to run qemu-kvm directly, just go with > --guestfs=/tmp/guest.fs and perf could fetch all required information > automatically. > > This should solve all issues while staying 100% in user space, right? > Yeah, needs a fuse filesystem to populate the host namespace (kind of sshfs over virtio-serial). -- error compiling committee.c: too many arguments to function