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.
W
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
>>> virt
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 p
Juan Quintela wrote:
> - monitor: I need a way to get to the monitor when going through
> libvirt, in the past you couldn't allow this, but now it looks
> possible.
Now you can just start another monitor connection to qemu :-)
Previously I've used a multiplexing script which accepts multiple
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 mult
On Tue, Mar 23, 2010 at 11:50:57AM +0100, Juan Quintela 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 virbr
- 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
