On 11/18/2013 07:13 PM, Richard Michael wrote:
Reopening this thread,
I confirm this is still broken in Final Fedora 20.
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.
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)...
What exactly *IS* our official setup for Bridging support??
We've failed hard in 19/20 on bridging and it's burnt me so much, I want to add a test case for Fedora 21 on this, where can I do this?
I've CC'd myself to : https://bugzilla.redhat.com/show_bug.cgi?id=1048351
Thanks, Shawn
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
I think someone needs to blog about it with screenshots, then we can link to it with all the fedora virt and upstream libvirt pages.
We've failed hard in 19/20 on bridging and it's burnt me so much, I want to add a test case for Fedora 21 on this, where can I do this?
Fedora test day test case template: http://fedoraproject.org/wiki/Template:QA/Test_Case
Maybe add a network manager bridge UI test case for the gnome test day, but you'll have to check with the folks who run it. Or if there's a networking test day.
I run the virt test day, and I've made a note to add test cases for setting up a bridge. I think there's an old one but it should be bumped and modernized.
- Cole
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?
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
I think someone needs to blog about it with screenshots, then we can link to it with all the fedora virt and upstream libvirt pages.
We've failed hard in 19/20 on bridging and it's burnt me so much, I want to add a test case for Fedora 21 on this, where can I do this?
Fedora test day test case template: http://fedoraproject.org/wiki/Template:QA/Test_Case
Maybe add a network manager bridge UI test case for the gnome test day, but you'll have to check with the folks who run it. Or if there's a networking test day.
I run the virt test day, and I've made a note to add test cases for setting up a bridge. I think there's an old one but it should be bumped and modernized.
It would be nice to try and ensure NM and virt-manager are singing from the same hymn sheet and there's some nice documentation somewhere about the "Proper Way" to set up bridging with modern virt-manager and NetworkManager, indeed. Shouldn't it be possible to just pointy-clicky it from virt-manager by now, in an Ideal World?
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.
Sorry that is all non-descript but it was one of those things that I expected wasn't _supposed_ to work so I never prodded for details.
I don't doubt that using the old network service on a server works fine, RHEL folks would scream if it didn't work.
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
I think someone needs to blog about it with screenshots, then we can link to it with all the fedora virt and upstream libvirt pages.
We've failed hard in 19/20 on bridging and it's burnt me so much, I want to add a test case for Fedora 21 on this, where can I do this?
Fedora test day test case template: http://fedoraproject.org/wiki/Template:QA/Test_Case
Maybe add a network manager bridge UI test case for the gnome test day, but you'll have to check with the folks who run it. Or if there's a networking test day.
I run the virt test day, and I've made a note to add test cases for setting up a bridge. I think there's an old one but it should be bumped and modernized.
It would be nice to try and ensure NM and virt-manager are singing from the same hymn sheet and there's some nice documentation somewhere about the "Proper Way" to set up bridging with modern virt-manager and NetworkManager, indeed. Shouldn't it be possible to just pointy-clicky it from virt-manager by now, in an Ideal World?
The virt-manager UI has been there for a few years, but it basically maps to creating a sysconfig script for a bridge, which NetworkManager didn't understand up until the past year or so. So NM would ignore the bridge and try to get an IP for your NIC, ruining the whole thing. You can NM_CONTROLLED=no those files, but then network manager thinks you have no network access, desktop apps complain, etc.
At this point, libvirt should add an interface driver that talks directly to networkmanager for this type of case, but since network manager has first class support for bridges these days the whole exercise is kind of irrelevant from virt-manager's POV. It would be nice if there was just a 'allow my virtual machines to share this host interface' checkbox in some NM UI that would do everything for us.
- Cole
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.
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 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.
Thanks, Shawn.
I think someone needs to blog about it with screenshots, then we can link to it with all the fedora virt and upstream libvirt pages.
We've failed hard in 19/20 on bridging and it's burnt me so much, I want to add a test case for Fedora 21 on this, where can I do this?
Fedora test day test case template: http://fedoraproject.org/wiki/Template:QA/Test_Case
Maybe add a network manager bridge UI test case for the gnome test day, but you'll have to check with the folks who run it. Or if there's a networking test day.
I run the virt test day, and I've made a note to add test cases for setting up a bridge. I think there's an old one but it should be bumped and
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:
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
-
Adam Williamson -
Cole Robinson -
Shawn Starr