On Sun, 2017-04-16 at 08:51 +0200, Evgeni Golov wrote: > > The solution is for people to configure a bridge or Open vSwitch (OVS) > > in /etc/network/interfaces. (Notice OVS can be configured[4] in the > > interfaces file). Maybe it would be useful to offer one or both of > > these options at install time, or even configure a standard (non-OVS) > > bridge by default in case the user decides to try KVM in future? > > IMHO the above implements option 1? > > > Are there other use cases apart from KVM that would benefit from this? > > I also use LXC on the same bridge, just for the fact that it is already set > up and provides DHCP, DNS and NAT. I used to have a similar setup but eventually migrated to a systemd based setup with systemd-networkd. With s-networkd, I have an independent bridge, which serves KVM/Libvirt, User Mode Linux and systemd-nspawn. VBox, running in bridged mode, used to have a network bug. I am not sure if that still applies. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775266 -- Given the large number of mailing lists I follow, I request you to CC me in replies for quicker response
Attachment:
signature.asc
Description: This is a digitally signed message part