From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O6PSh-0002j3-Ma for qemu-devel@nongnu.org; Mon, 26 Apr 2010 10:39:03 -0400 Received: from [140.186.70.92] (port=46199 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O6PSe-0002hy-JB for qemu-devel@nongnu.org; Mon, 26 Apr 2010 10:39:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O6PSd-0003Wy-7e for qemu-devel@nongnu.org; Mon, 26 Apr 2010 10:39:00 -0400 Received: from mx1.redhat.com ([209.132.183.28]:17507) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O6PSc-0003Wh-Kw for qemu-devel@nongnu.org; Mon, 26 Apr 2010 10:38:59 -0400 Message-ID: <4BD5A57E.3060602@redhat.com> Date: Mon, 26 Apr 2010 17:38:54 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [libvirt] Libvirt debug API References: <4BD1971B.7060907@redhat.com> <4BD1A543.1050004@codemonkey.ws> <4BD1ADA2.2050605@redhat.com> <4BD1E723.6070005@codemonkey.ws> <4BD2BDE0.7020907@redhat.com> <4BD3B965.3060205@codemonkey.ws> <4BD42CDB.2030901@redhat.com> <4BD4F20D.8030901@codemonkey.ws> <20100426095949.GA1342@redhat.com> <4BD5915F.3060405@codemonkey.ws> <20100426133120.GD1342@redhat.com> <4BD59874.2000207@codemonkey.ws> <4BD59C9E.2000506@redhat.com> <4BD5A109.9060004@codemonkey.ws> <4BD5A263.3070908@redhat.com> <4BD5A2F2.7070805@codemonkey.ws> In-Reply-To: <4BD5A2F2.7070805@codemonkey.ws> 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: Anthony Liguori Cc: "libvir-list@redhat.com" , qemu-devel , Luiz Capitulino , Chris Lalancette , Jiri Denemark On 04/26/2010 05:28 PM, Anthony Liguori wrote: >> Or a library that the user-written launcher calls. Or a plugin that >> qemud calls. > > > A plugin would lose the security context. It could attempt to > recreate it that seems like a lot of unnecessary complexity. > A plugin would create the security context instead of the launcher. Currently security contexts are created by the login process. We could easily reuse that. Any other security context code would be custom written; so it can be written as a qemud plugin instead of a bit of code that goes before a qemu launch. -- error compiling committee.c: too many arguments to function