On Mon, 2014-01-27 at 15:29 -0500, Cole Robinson wrote: > On 01/27/2014 03:13 PM, Adam Williamson wrote: > > On Mon, 2014-01-27 at 10:04 -0500, Cole Robinson wrote: > > > >> This is all news to me, please put all the details in a bug report and CC > >> me. > >> You can start with filing it against libvirt and we can triage from there. > >> > >>> > >>> What exactly *IS* our official setup for Bridging support?? > >>> > >> > >> What was it ever, really? You could do it with virt-manager but that could > >> also fall over in multiple ways. You could do it with sysconfig scripts but > >> that required stopping NetworkManager which is basically impossible on a > >> modern desktop. > > > > It's not at all difficult, AFAIK. My 'vmhost' machine which runs all my > > production server VMs uses the old 'network' service (and has bridging > > set up the really-old-skool way). I haven't done any ninja magic to turn > > off NetworkManager, I haven't even removed it. All I did, years ago, > > was: > > > > systemctl disable NetworkManager.service > > systemctl enable network.service > > > > that's worked, ever since, across multiple updates, upgrades and system > > restarts. I've never had a problem. > > > > Is there some problem I'm unaware of which means it's not this easy to > > turn off NM in some situation that doesn't match mine? > > > > Do you use that machine for desktop usage (I said 'modern desktop' above)? In > the few times I've ever tried to stop networkmanager with gnome shell, 'bad > things happened'. Heard the same thing from others as well.
Ah, no, indeed. In that case you might need to mask NetworkManager.service instead of just disabling it, I think - I haven't tried it for a while. Or remove NM entirely - I think you can do that. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
