SCIENTIFIC-LINUX-USERS Archives

April 2012

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Lamar Owen <[log in to unmask]>
Reply To:
Lamar Owen <[log in to unmask]>
Date:
Mon, 9 Apr 2012 17:57:29 -0400
Content-Type:
Text/Plain
Parts/Attachments:
Text/Plain (19 lines)
On Monday, April 09, 2012 03:24:33 PM you wrote:
> Sadly, last time I saw every guide on how to setup virtual machines
> (KVM) in bridge configuration started with "turn off network manager"..

Sadly, this is true even of the official upstream documentation.

The NetworkManager bug report for bridging is:
https://bugzilla.gnome.org/show_bug.cgi?id=546197

and for bonding is:
https://bugzilla.gnome.org/show_bug.cgi?id=540995

(trunking is a different item, at least from the point of view of network switches, where trunking is specific to transporting multiple VLAN's over a single interface).

Ideally one would have a multiple ethernet devices and route them to individual VM's for best performance, but that's difficult on smaller hosts where having two NICs is the norm, and thus bridging is the ideal.  Would be nice to have a solution similar to the VMware embedded Cisco Nexus vswitch, but that's probably a pipe dream....

In any case, disabling NM on an interface-by-interface basis with NM_CONTROLLED is recommended in the upstream documents. (reference:
https://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Host_Configuration_and_Guest_Installation_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt.html 

ATOM RSS1 RSS2