[Kernel-packages] [Bug 1153364] Re: trouble with guest network connectivity when host is using a bonded interface
[Expired for qemu-kvm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: qemu-kvm (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1153364 Title: trouble with guest network connectivity when host is using a bonded interface Status in linux package in Ubuntu: Expired Status in qemu-kvm package in Ubuntu: Expired Bug description: i'm seeing poor/intermittent/degrading network connectivity for guests, when the host is using a bonded interface. in a nutshell, the network configuration is as follows: the physical interfaces [eth0 and eth1] are bonded together as bond0 [i've tried various bond modes - see below]. a bridge interface [br0] is configured with bond0 attached to it. all guests use br0 as their "forward" interface. my tests have generally included a single host, with two guests running on it. both guests are running ubuntu 12.10. it depends slightly on the particulars of the configuration, but the most prevalent symptom is that a newly booted guest will at first respond to pings [with little to no loss], and the guest will be able to ping other hosts on the network, but as time passes, more and more packets are dropped. eventually, virtually all ping requests go unanswered. in some cases, it appears that restarting networking on the guest will fix this, partially and temporarily. the guest will begin to reply 4-5 packets after restarting networking, but does not respond consistently, eventually failing again as before. i've also noticed that in some cases where ping against the guest has not yet begun to fail, if i ping something else on the network from the guest, this causes the pings against the guest to abruptly fail. i know this is all quite abstract - i've spent quite a bit a time trying to isolate various variables, and while i've made some progress, i think some guidance would be helpful. what i have noticed specifically is if i attach a physical device [e.g. eth0 or eth1] to the bridge [instead of bond0], things seem to work ok. also, if i use active-backup as the bonding mode, things seem to work ok. i was initially using balance-alb as the bonding mode, and have also tested balance-rr as the bonding mode. both exhibit the above symptoms. i've also tried various network card models for the guests [realtek, e1000, and virtio]. this has not had any impact on the symptoms. lastly, the two guests have been able to ping each other, with no issues, regardless of the various network settings. at the moment, i have switched back to active-backup, so this is reflected in the below information. here is a bit of configuration info: host os/package info: >lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 >apt-cache policy qemu-kvm qemu-kvm: Installed: 1.2.0+noroms-0ubuntu2.12.10.3 Candidate: 1.2.0+noroms-0ubuntu2.12.10.3 Version table: *** 1.2.0+noroms-0ubuntu2.12.10.3 0 500 http://us.archive.ubuntu.com/ubuntu/ quantal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.2.0+noroms-0ubuntu2.12.10.2 0 500 http://security.ubuntu.com/ubuntu/ quantal-security/main amd64 Packages 1.2.0+noroms-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages >dpkg -l | grep -i virt ii libvirt-bin0.9.13-0ubuntu12.2 amd64programs for the libvirt library ii libvirt0 0.9.13-0ubuntu12.2 amd64library for interfacing with different virtualization systems ii python-libvirt 0.9.13-0ubuntu12.2 amd64libvirt Python bindings ii qemu-kvm 1.2.0+noroms-0ubuntu2.12.10.3 amd64Full virtualization on supported hardware ii virtinst 0.600.2-1ubuntu1 all Programs to create and clone virtual machines >dpkg -l | grep -i qemu ii qemu-common1.2.0+noroms-0ubuntu2.12.10.3 all qemu common functionality (bios, documentation, etc) ii qemu-kvm 1.2.0+noroms-0ubuntu2.12.10.3 amd64Full virtualization on supported hardware ii qemu-utils 1.2.0+noroms-0ubuntu2.12.10.3 amd64qemu utilities ii vgabios0.7a-3ubuntu2 all VGA BIOS software for the Bochs and Qemu emulated VGA card host network config: >egrep -v '(^[[:space:]]*#|^[[:space:]]*$)' /etc/network/interfaces auto lo iface lo inet loopback auto eth0 iface eth0 inet manual
[Kernel-packages] [Bug 1153364] Re: trouble with guest network connectivity when host is using a bonded interface
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1153364 Title: trouble with guest network connectivity when host is using a bonded interface Status in linux package in Ubuntu: Expired Status in qemu-kvm package in Ubuntu: Expired Bug description: i'm seeing poor/intermittent/degrading network connectivity for guests, when the host is using a bonded interface. in a nutshell, the network configuration is as follows: the physical interfaces [eth0 and eth1] are bonded together as bond0 [i've tried various bond modes - see below]. a bridge interface [br0] is configured with bond0 attached to it. all guests use br0 as their "forward" interface. my tests have generally included a single host, with two guests running on it. both guests are running ubuntu 12.10. it depends slightly on the particulars of the configuration, but the most prevalent symptom is that a newly booted guest will at first respond to pings [with little to no loss], and the guest will be able to ping other hosts on the network, but as time passes, more and more packets are dropped. eventually, virtually all ping requests go unanswered. in some cases, it appears that restarting networking on the guest will fix this, partially and temporarily. the guest will begin to reply 4-5 packets after restarting networking, but does not respond consistently, eventually failing again as before. i've also noticed that in some cases where ping against the guest has not yet begun to fail, if i ping something else on the network from the guest, this causes the pings against the guest to abruptly fail. i know this is all quite abstract - i've spent quite a bit a time trying to isolate various variables, and while i've made some progress, i think some guidance would be helpful. what i have noticed specifically is if i attach a physical device [e.g. eth0 or eth1] to the bridge [instead of bond0], things seem to work ok. also, if i use active-backup as the bonding mode, things seem to work ok. i was initially using balance-alb as the bonding mode, and have also tested balance-rr as the bonding mode. both exhibit the above symptoms. i've also tried various network card models for the guests [realtek, e1000, and virtio]. this has not had any impact on the symptoms. lastly, the two guests have been able to ping each other, with no issues, regardless of the various network settings. at the moment, i have switched back to active-backup, so this is reflected in the below information. here is a bit of configuration info: host os/package info: >lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 >apt-cache policy qemu-kvm qemu-kvm: Installed: 1.2.0+noroms-0ubuntu2.12.10.3 Candidate: 1.2.0+noroms-0ubuntu2.12.10.3 Version table: *** 1.2.0+noroms-0ubuntu2.12.10.3 0 500 http://us.archive.ubuntu.com/ubuntu/ quantal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.2.0+noroms-0ubuntu2.12.10.2 0 500 http://security.ubuntu.com/ubuntu/ quantal-security/main amd64 Packages 1.2.0+noroms-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages >dpkg -l | grep -i virt ii libvirt-bin0.9.13-0ubuntu12.2 amd64programs for the libvirt library ii libvirt0 0.9.13-0ubuntu12.2 amd64library for interfacing with different virtualization systems ii python-libvirt 0.9.13-0ubuntu12.2 amd64libvirt Python bindings ii qemu-kvm 1.2.0+noroms-0ubuntu2.12.10.3 amd64Full virtualization on supported hardware ii virtinst 0.600.2-1ubuntu1 all Programs to create and clone virtual machines >dpkg -l | grep -i qemu ii qemu-common1.2.0+noroms-0ubuntu2.12.10.3 all qemu common functionality (bios, documentation, etc) ii qemu-kvm 1.2.0+noroms-0ubuntu2.12.10.3 amd64Full virtualization on supported hardware ii qemu-utils 1.2.0+noroms-0ubuntu2.12.10.3 amd64qemu utilities ii vgabios0.7a-3ubuntu2 all VGA BIOS software for the Bochs and Qemu emulated VGA card host network config: >egrep -v '(^[[:space:]]*#|^[[:space:]]*$)' /etc/network/interfaces auto lo iface lo inet loopback auto eth0 iface eth0 inet manual bond-master
[Kernel-packages] [Bug 1153364] Re: trouble with guest network connectivity when host is using a bonded interface
I'm working through dormant bugs at the moment. It seems this was hard to work on in the past for its reproducibility. On the other hand I used setups like that in Xenial and later a lot and they worked fine, so we can at least somewhat assume it got better. That said I'm unsubscribing ubuntu-server and marking it incomplete for now. If that (after all the time) really still is an issue please let us know and if possibel recreate on a newer release. ** Changed in: qemu-kvm (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1153364 Title: trouble with guest network connectivity when host is using a bonded interface Status in linux package in Ubuntu: Incomplete Status in qemu-kvm package in Ubuntu: Incomplete Bug description: i'm seeing poor/intermittent/degrading network connectivity for guests, when the host is using a bonded interface. in a nutshell, the network configuration is as follows: the physical interfaces [eth0 and eth1] are bonded together as bond0 [i've tried various bond modes - see below]. a bridge interface [br0] is configured with bond0 attached to it. all guests use br0 as their "forward" interface. my tests have generally included a single host, with two guests running on it. both guests are running ubuntu 12.10. it depends slightly on the particulars of the configuration, but the most prevalent symptom is that a newly booted guest will at first respond to pings [with little to no loss], and the guest will be able to ping other hosts on the network, but as time passes, more and more packets are dropped. eventually, virtually all ping requests go unanswered. in some cases, it appears that restarting networking on the guest will fix this, partially and temporarily. the guest will begin to reply 4-5 packets after restarting networking, but does not respond consistently, eventually failing again as before. i've also noticed that in some cases where ping against the guest has not yet begun to fail, if i ping something else on the network from the guest, this causes the pings against the guest to abruptly fail. i know this is all quite abstract - i've spent quite a bit a time trying to isolate various variables, and while i've made some progress, i think some guidance would be helpful. what i have noticed specifically is if i attach a physical device [e.g. eth0 or eth1] to the bridge [instead of bond0], things seem to work ok. also, if i use active-backup as the bonding mode, things seem to work ok. i was initially using balance-alb as the bonding mode, and have also tested balance-rr as the bonding mode. both exhibit the above symptoms. i've also tried various network card models for the guests [realtek, e1000, and virtio]. this has not had any impact on the symptoms. lastly, the two guests have been able to ping each other, with no issues, regardless of the various network settings. at the moment, i have switched back to active-backup, so this is reflected in the below information. here is a bit of configuration info: host os/package info: >lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 >apt-cache policy qemu-kvm qemu-kvm: Installed: 1.2.0+noroms-0ubuntu2.12.10.3 Candidate: 1.2.0+noroms-0ubuntu2.12.10.3 Version table: *** 1.2.0+noroms-0ubuntu2.12.10.3 0 500 http://us.archive.ubuntu.com/ubuntu/ quantal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.2.0+noroms-0ubuntu2.12.10.2 0 500 http://security.ubuntu.com/ubuntu/ quantal-security/main amd64 Packages 1.2.0+noroms-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages >dpkg -l | grep -i virt ii libvirt-bin0.9.13-0ubuntu12.2 amd64programs for the libvirt library ii libvirt0 0.9.13-0ubuntu12.2 amd64library for interfacing with different virtualization systems ii python-libvirt 0.9.13-0ubuntu12.2 amd64libvirt Python bindings ii qemu-kvm 1.2.0+noroms-0ubuntu2.12.10.3 amd64Full virtualization on supported hardware ii virtinst 0.600.2-1ubuntu1 all Programs to create and clone virtual machines >dpkg -l | grep -i qemu ii qemu-common1.2.0+noroms-0ubuntu2.12.10.3 all qemu common functionality (bios, documentation, etc) ii qemu-kvm 1.2.0+noroms-0ubuntu2.12.10.3 amd64Full virtualization on supported hardware ii qemu-utils 1.2.0+noroms-0ubuntu2.12.10.3
[Kernel-packages] [Bug 1153364] Re: trouble with guest network connectivity when host is using a bonded interface
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qemu-kvm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1153364 Title: trouble with guest network connectivity when host is using a bonded interface Status in linux package in Ubuntu: Incomplete Status in qemu-kvm package in Ubuntu: Confirmed Bug description: i'm seeing poor/intermittent/degrading network connectivity for guests, when the host is using a bonded interface. in a nutshell, the network configuration is as follows: the physical interfaces [eth0 and eth1] are bonded together as bond0 [i've tried various bond modes - see below]. a bridge interface [br0] is configured with bond0 attached to it. all guests use br0 as their "forward" interface. my tests have generally included a single host, with two guests running on it. both guests are running ubuntu 12.10. it depends slightly on the particulars of the configuration, but the most prevalent symptom is that a newly booted guest will at first respond to pings [with little to no loss], and the guest will be able to ping other hosts on the network, but as time passes, more and more packets are dropped. eventually, virtually all ping requests go unanswered. in some cases, it appears that restarting networking on the guest will fix this, partially and temporarily. the guest will begin to reply 4-5 packets after restarting networking, but does not respond consistently, eventually failing again as before. i've also noticed that in some cases where ping against the guest has not yet begun to fail, if i ping something else on the network from the guest, this causes the pings against the guest to abruptly fail. i know this is all quite abstract - i've spent quite a bit a time trying to isolate various variables, and while i've made some progress, i think some guidance would be helpful. what i have noticed specifically is if i attach a physical device [e.g. eth0 or eth1] to the bridge [instead of bond0], things seem to work ok. also, if i use active-backup as the bonding mode, things seem to work ok. i was initially using balance-alb as the bonding mode, and have also tested balance-rr as the bonding mode. both exhibit the above symptoms. i've also tried various network card models for the guests [realtek, e1000, and virtio]. this has not had any impact on the symptoms. lastly, the two guests have been able to ping each other, with no issues, regardless of the various network settings. at the moment, i have switched back to active-backup, so this is reflected in the below information. here is a bit of configuration info: host os/package info: >lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 >apt-cache policy qemu-kvm qemu-kvm: Installed: 1.2.0+noroms-0ubuntu2.12.10.3 Candidate: 1.2.0+noroms-0ubuntu2.12.10.3 Version table: *** 1.2.0+noroms-0ubuntu2.12.10.3 0 500 http://us.archive.ubuntu.com/ubuntu/ quantal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.2.0+noroms-0ubuntu2.12.10.2 0 500 http://security.ubuntu.com/ubuntu/ quantal-security/main amd64 Packages 1.2.0+noroms-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages >dpkg -l | grep -i virt ii libvirt-bin0.9.13-0ubuntu12.2 amd64programs for the libvirt library ii libvirt0 0.9.13-0ubuntu12.2 amd64library for interfacing with different virtualization systems ii python-libvirt 0.9.13-0ubuntu12.2 amd64libvirt Python bindings ii qemu-kvm 1.2.0+noroms-0ubuntu2.12.10.3 amd64Full virtualization on supported hardware ii virtinst 0.600.2-1ubuntu1 all Programs to create and clone virtual machines >dpkg -l | grep -i qemu ii qemu-common1.2.0+noroms-0ubuntu2.12.10.3 all qemu common functionality (bios, documentation, etc) ii qemu-kvm 1.2.0+noroms-0ubuntu2.12.10.3 amd64Full virtualization on supported hardware ii qemu-utils 1.2.0+noroms-0ubuntu2.12.10.3 amd64qemu utilities ii vgabios0.7a-3ubuntu2 all VGA BIOS software for the Bochs and Qemu emulated VGA card host network config: >egrep -v '(^[[:space:]]*#|^[[:space:]]*$)' /etc/network/interfaces auto lo iface lo inet loopback auto eth0 iface eth0 inet manual bond-master bond0
