From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Nz8Fa-0008Mm-Sd
	for qemu-devel@nongnu.org; Tue, 06 Apr 2010 08:51:26 -0400
Received: from [140.186.70.92] (port=57998 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Nz8FZ-0008KC-Ex
	for qemu-devel@nongnu.org; Tue, 06 Apr 2010 08:51:26 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <agraf@suse.de>) id 1Nz8FY-0000r1-0F
	for qemu-devel@nongnu.org; Tue, 06 Apr 2010 08:51:25 -0400
Received: from cantor.suse.de ([195.135.220.2]:53978 helo=mx1.suse.de)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <agraf@suse.de>) id 1Nz8FX-0000qt-NH
	for qemu-devel@nongnu.org; Tue, 06 Apr 2010 08:51:23 -0400
Message-ID: <4BBB2E4A.90608@suse.de>
Date: Tue, 06 Apr 2010 14:51:22 +0200
From: Alexander Graf <agraf@suse.de>
MIME-Version: 1.0
References: <B88AE7FC-34E0-4CF2-88BC-0A11071925D8@suse.de>
	<4BBA60CC.5050008@redhat.com>
	<2B33FC0A-344D-4A4D-8B2D-7E8FFBB038EF@suse.de>
	<4BBB2474.6010204@redhat.com> <4BBB2900.9010309@suse.de>
	<4BBB2BDE.4040500@redhat.com>
In-Reply-To: <4BBB2BDE.4040500@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Re: libvirt vs. in-qemu management
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: Avi Kivity <avi@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel Developers <qemu-devel@nongnu.org>

Avi Kivity wrote:
> On 04/06/2010 03:28 PM, Alexander Graf wrote:
>>> Note things like network setup are a bottomless pit.  Pretty soon you
>>> need to setup vlans and bonding etc.  If a user needs one of these and
>>> qemud doesn't provide it, then qemud becomes useless to them.  But the
>>> same problem applies to libvirt.
>>>      
>> If they are a bottomless pit then they are a bottomless pit. There's
>> nothing we can do about it. This pit needs to be dug either way, whether
>> it's in libvirt or in qemud.
>>    
>
> Agreed.  The only difference is who's doing the digging.
>
> One way to avoid it is to have a rich plugin API so if some needs some
> to, say, set up traffic control on the interface, they can write a
> plugin to do that.

Another way would be to have an active open source community that just
writes the support for traffic control upstream if they need it. I
actually prefer that to a plugin API.


Alex