From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NuLUw-0004WH-4M
	for qemu-devel@nongnu.org; Wed, 24 Mar 2010 03:59:30 -0400
Received: from [140.186.70.92] (port=49962 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NuLUt-0004W9-S2
	for qemu-devel@nongnu.org; Wed, 24 Mar 2010 03:59:28 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <kraxel@redhat.com>) id 1NuLUs-0006Da-CX
	for qemu-devel@nongnu.org; Wed, 24 Mar 2010 03:59:27 -0400
Received: from mx1.redhat.com ([209.132.183.28]:54525)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <kraxel@redhat.com>) id 1NuLUs-0006DK-5U
	for qemu-devel@nongnu.org; Wed, 24 Mar 2010 03:59:26 -0400
Message-ID: <4BA9C651.6020802@redhat.com>
Date: Wed, 24 Mar 2010 08:59:13 +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>	<4BA89AD5.5080908@redhat.com>
	<20100323231311.GB20130@shareable.org>
In-Reply-To: <20100323231311.GB20130@shareable.org>
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: Jamie Lokier <jamie@shareable.org>
Cc: "libvir-list@redhat.com" <libvir-list@redhat.com>, qemu-devel <qemu-devel@nongnu.org>, Juan Quintela <quintela@redhat.com>

On 03/24/10 00:13, Jamie Lokier wrote:
> Gerd Hoffmann wrote:
>>> - 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).
>
> I had the opposite problem.  Needed to use multiple bridges and have
> some VMs behind NAT without a bridge (private IPs), and some using
> separately firewalled bridges (needed to behave like real attached
> hardware with their original MACs, but be firewalled).

No problem in theory.  libvirt should detect existing bridges and allow 
you to attach virtual machines to them.  So you can setup bridges and 
firewalling for them using usual distro tools and use them for virtual 
machines.

In practice I've seen this not working correctly in the past, i.e. my 
br0 didn't pop up in the virt-manager nic setup page.

cheers,
   Gerd