From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1O6Okf-0001JD-G2
	for qemu-devel@nongnu.org; Mon, 26 Apr 2010 09:53:33 -0400
Received: from [140.186.70.92] (port=54262 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1O6Okc-0001IJ-Ak
	for qemu-devel@nongnu.org; Mon, 26 Apr 2010 09:53:33 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <avi@redhat.com>) id 1O6OkQ-0003hA-UC
	for qemu-devel@nongnu.org; Mon, 26 Apr 2010 09:53:24 -0400
Received: from mx1.redhat.com ([209.132.183.28]:60837)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <avi@redhat.com>) id 1O6OkQ-0003gz-KR
	for qemu-devel@nongnu.org; Mon, 26 Apr 2010 09:53:18 -0400
Message-ID: <4BD59AC9.4090308@redhat.com>
Date: Mon, 26 Apr 2010 16:53:13 +0300
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: [libvirt] Libvirt debug API
References: <4BBF2E93.3020508@redhat.com>
	<20100409142717.GA11875@redhat.com>	<20100412122013.58894a64@redhat.com>
	<4BD09A3B.3090001@codemonkey.ws> <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> <4BD52B13.2040200@redhat.com>
	<4BD591AC.7090208@codemonkey.ws> <4BD597F1.2010205@redhat.com>
	<4BD59946.8040705@codemonkey.ws>
In-Reply-To: <4BD59946.8040705@codemonkey.ws>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Libvirt <libvir-list@redhat.com>, Jiri Denemark <jdenemar@redhat.com>, Chris Lalancette <clalance@redhat.com>, qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>

On 04/26/2010 04:46 PM, Anthony Liguori wrote:
>>> (3) The system management application can certainly create whatever 
>>> context it wants to launch a vm from.  It's comes down to who's 
>>> responsible for creating the context the guest runs under.  I think 
>>> doing that at the libvirt level takes away a ton of flexibility from 
>>> the management application.
>>
>> If you want to push the flexibility slider all the way to the right 
>> you get bare qemu.  It exposes 100% of qemu capabilities.  And it's 
>> not so bad these days.  But it's not something that can be remoted.
>
> As I mentioned earlier, remoting is not a very important use-case to me.
>
> Does RHEV-M actually use the remote libvirt interface?  I assume it'll 
> talk to vdsm via some protocol and vdsm will use the local libvirt API. 

Yes.

> I suspect most uses of libvirt are actually local uses.

I expect the same, though I'm sure a design goal was to make use of 
libvirt be reasonable through the remote API.  If we aren't able to 
fulfil it, much of the value of libvirt goes away.

-- 
error compiling committee.c: too many arguments to function