On 01/27/2014 10:02 PM, Shawn Starr wrote: > On January 27, 2014 10:04:14 AM Cole Robinson wrote: > >> On 01/26/2014 11:39 PM, Shawn Starr wrote: > >> >> On 11/18/2013 07:13 PM, Richard Michael wrote: > >> >> Hello, > >> >> > >> >> I've just installed F20 beta x64 and applied all updates. > >> >> > >> >> I'm attempting to create a bridge network interface in virt-manager > >> >> (0.10.0). I complete the "Configure network interface" dialog, and > >> >> when I click "Finish" I receive an "Input Error" with message: > >> >> > >> >> 'str' object has no attribute 'XMLDesc' > >> > >> I missed the original mail, but that bit is just a virt-manager issue, fix > >> is upstream and waiting for backport now. It's tracked at the bug you > >> mention below: > >> > >> https://bugzilla.redhat.com/show_bug.cgi?id=1048351 > >> > >> > Worse, NetworkManager bridge is broken in that the bridge interface never > >> > gets the IP address and if libvirtd tries to bring up a VM instance it > >> > never gets network connectivity. > >> > >> Can't blame networkmanager here, this is just more example of > >> virt-manager/libvirt/netcf not playing nice with NetworkManager which has > >> been a recurring problem. > >> > >> NetworkManager grew more explicit support for bridges in the past few fedora > >> cycles, so maybe something that used to work has regressed. > >> > >> > One additional bad thing (which I just fixed), was my original working > >> > bridge setup. libvirtd silently fails to autostart a KVM instance until I > >> > destroyed my bridge setup, recreated it via: > >> > > >> > > >> > > >> > # nmcli connection add con-name Bridge type bridge ifname bridge0 > >> > > >> > # nmcli connection add con-name Slave type ethernet mac AA:BB:CC:DD:EE:FF > >> > > >> > > >> > > >> > This alone will not set/bind the IP on the bridge0 interface but on the > >> > actual interface, so while libvirt now autostarts the KVM VM instance, > >> > the VM has no external network connectivity as the bridge0 interface has > >> > no IP assigned to it... > >> > > >> > > >> > > >> > I've encountered various problems with bridge networking and > >> > libvirtd/NetworkManager/virt-manager and now with systemd-networkd (which > >> > does bridging)... > >> > >> 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. > >> > >> Nowadays there should be a NetworkManager UI solution but it hasn't been > >> advertised very much and isn't entirely straightforward: > >> > >> https://lists.fedoraproject.org/pipermail/devel/2014-January/194003.html > >> > > > > Cole, > > > > wrt to this above, so you should *NOT* have both the interface AND the bridge > set to ONBOOT=yes? If that's the case, I guess that could explain why enp0s25 > gets the IP before bridge0 does (if the order is interfaces before bridges). > > I don't know the details, sorry. > > I know when I use virt-manager it sets up the bridge correctly first time, but > after rebooting, it all unravels and nmcli says it doesn't know what those > connections are and fails. When I go back into virt-manager it loses track of > what was created and won't bring up the network and then I have to fix it in > commandline from scratch. > > > > This is with NetworkManager enabled. > My understanding was that bridged networking and NetworkManager also conflicted to create an unusable setup, which is why all existing the documentation explicitly talks about disabling NetworkManager. But maybe things have gotten even worse. We should follow up in a bug. - Cole -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
