On Mon, Oct 28, 2013 at 07:41:59PM -0400, SilverTip257 wrote:
On Mon, Oct 28, 2013 at 2:05 PM, Nux! nux@li.nux.ro wrote:
On 28.10.2013 17:52, Fred Smith wrote:
I'm investigating how to setup KVM so I can run VMs without having to use VirtualBox or VMware, or etc.
All the HOWTOs I see tell you to disable NM.
There is no reason to disable NM entirely.
But you can disable NM per interface with: NM_CONTROLLED="no"
Yes, so I've learned today. thanks for the tip though.
I've seen it is common practice to disable NM on bridge and other interfaces at times.
I expect this excerpt from [0] is why I've seen NM disabled "per interface" in various write-ups. And in my case I never needed or wanted NM fiddling with most interfaces on my headless servers. ;)
Sure. makes sense. But I'm hoping to use this on my main (home) desktop machine, so I need to still have desktop-likke services available.
- The NM_CONTROLLED=no should be added to the Ethernet interface to
prevent *NetworkManager* from altering the file. It can also be added to the bridge configuration file in case future versions of *NetworkManager* support bridge configuration.
thanks for the info!