From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Nu1YJ-0002rA-Ob
	for qemu-devel@nongnu.org; Tue, 23 Mar 2010 06:41:39 -0400
Received: from [199.232.76.173] (port=43113 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Nu1YI-0002qj-Ud
	for qemu-devel@nongnu.org; Tue, 23 Mar 2010 06:41:38 -0400
Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim
	4.60) (envelope-from <kraxel@redhat.com>) id 1Nu1YI-0005ZW-BX
	for qemu-devel@nongnu.org; Tue, 23 Mar 2010 06:41:38 -0400
Received: from mx1.redhat.com ([209.132.183.28]:54887)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <kraxel@redhat.com>) id 1Nu1YH-0005ZL-Ro
	for qemu-devel@nongnu.org; Tue, 23 Mar 2010 06:41:38 -0400
Message-ID: <4BA89AD5.5080908@redhat.com>
Date: Tue, 23 Mar 2010 11:41:25 +0100
From: Gerd Hoffmann <kraxel@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: Supporting hypervisor specific APIs in libvirt
References: <4BA7C40C.2040505@codemonkey.ws> <m3ocif2vz7.fsf@trasno.mitica>
In-Reply-To: <m3ocif2vz7.fsf@trasno.mitica>
Content-Type: text/plain; charset=ISO-8859-1; 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: Juan Quintela <quintela@redhat.com>
Cc: "libvir-list@redhat.com" <libvir-list@redhat.com>, qemu-devel <qemu-devel@nongnu.org>

> - networking: man, setting networking is a mess, libvirt just does it
>    for you.

+1

Even when not using libvirt for a reason or another I usually hook my 
virtual machines into virbr0 (libvirt default network).

cheers,
   Gerd