[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Re: Supporting hypervisor specific APIs in libvirt

From: Cole Robinson
Subject: Re: [Qemu-devel] Re: Supporting hypervisor specific APIs in libvirt
Date: Wed, 24 Mar 2010 09:52:53 -0400
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100301 Fedora/3.0.3-1.fc12 Thunderbird/3.0.3

On 03/24/2010 03:59 AM, Gerd Hoffmann wrote:
> 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.

Please file a bug: virt-manager has had bridge detection for years, so
something must be going wrong. In f13 we will use netcf for this, so
even bridge enumeration on remote hosts should work.

Additionally I recently made a change upstream to allow users to
manually enter a bridge name, since netcf isn't supported for all
distros yet.

- Cole

reply via email to

[Prev in Thread] Current Thread [Next in Thread]