Comment 10 for bug 865515

Serge Hallyn writes ("[Bug 865515] Re: virtual machines should not have nat on servers"):
> How would you suggest configuring out of the box on install for a
> server?

eth0 should be bridged. Specifically, for a vm host, the primary
network interface (by which I mean the one used for the original
installation, and set up automatically by the installer) should be
enslaved to a new bridge.

> I don't believe it is reasonable to assume we can bridge eth0 and have
> that be the right thing to do.

On a server VM host system with one in-use network interface, it is
exactly the right thing to do.

> Perhaps we could find the nic for the default route, but that could
> be fragile especially in esoteric setups.

If there are multiple in-service network interfaces then obviously
we don't know what to do. In that case the software shouldn't do
anything automatically.

But that's OK because if there are multiple in-service network
interfaces on a server, the admin has _already_ done some manual
setup. So they will know how they want to organise the VM networking
and it is fine to expect them to tell the VM system what to do.

Specifically, in that case it is fine for the VM setup to ask them
"please tell me which bridge to use".

> Also, adding a NATed bridge is safe to do at any time, but taking the
> primary nic and turning it into a bridge during upgrade is not safe.

The question of what to do during upgrade, and what to do during
install, are somewhat different.

> Is there an alternative?
>
> ** Changed in: libvirt (Ubuntu)
> Status: Confirmed => Incomplete

Can you please stop changing the status of this bug ?

Ian.