** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/785668
Title:
bonding inside a bridge does not update ARP
Hello,
Now I am dazed and confused (and trying to continue)
I have tested most of the combination of bonding modes with appropriate
switch settings and here is what I get :
Bonding modeswitch configurationresult(ping from Container)
With STP
I read the mail and did a first round of test before I could check the
setting of the switch. Here are the transcript of the test with
balance-rr.
Container : LXC container with fixed IP
VMhost : The host where the LXC container runs. configured with br0 bond0
remote_host : another host on the
I sent an email to bonding-devel, and got this response:
http://sourceforge.net/mailarchive/forum.php?thread_name=21866.1306527811%40deathforum_name
=bonding-devel
Assuming that your switch is in fact set up for Etherchannel, can you go
ahead and gather the tcpdump data?
--
You received this
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/785668
Title:
bonding inside a bridge does not update ARP
** Changed in: qemu-kvm (Ubuntu)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/785668
Title:
bonding inside a bridge
I can reproduce this just using lxc, which simply attaches an endpoint
of a veth tunnel to the bridge. With balance-rr mode, i can't dhcp in
the guest. With balance-alb, I can.
That means this is not actually qemu-kvm, but a bug in the kernel or
(unlikely) ifenslave.
** Changed in: linux
My next steps will be to test on maverick and natty, look through
linux-2.6/drivers/net/bonding and linux-2.6/net/bridge/ and perhaps go
to the https://lists.linux-
foundation.org/pipermail/bridge/2011-May/thread.html list to ask for
help if it is still broken in natty.
--
You received this bug
Maverick gives me the same result. (Except I don't seem able, in
maverick, to auto-setup the bond+bridge setup with
/etc/network/interfaces, keep having to do it by hand. Hoping I did
something wrong myself,a nd it's not a maverick bug)
--
You received this bug notification because you are a
Natty is still affected.
Since qemu isn't needed to show the bug, you can now trivially test this
inside a natty kvm container by giving it two NICs, setting up
/etc/network interfaces as shown above, and using lxc as follows:
apt-get install lxc debootstrap
mkdir /cgroup
mount -t
Following your suggestions, I modified my /etc/network/interfaces
added the STP options to my test environment. Following that, I am now
able to ping to the remote system using the following bonding modes :
* 802.3ad (4)
* tlb (5)
* alb (6)
For unknown reasons, I'm still unable to use
Regarding your request for /etc/modprove.d/bonding.conf, there is no
such file on my test system. Let me know if you still require the xml
dump of the VM.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
Quoting Louis Bouchard (louis.bouch...@canonical.com):
Regarding your request for /etc/modprove.d/bonding.conf, there is no
such file on my test system.
Right, sorry, that's obsolete as of hardy, sorry.
Let me know if you still require the xml
dump of the VM.
Thanks, no, as I'm able to
** Description changed:
Binary package hint: qemu-kvm
Description: Ubuntu 10.4.2
Release: 10.04
-
- When setting a KVM host with a bond0 interface made of eth0 and eth1 and
using this bond0 interface for a bridge to KVM VMs, the ARP tables do not get
updated correctly and
+ When
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/785668
Title:
bonding inside a bridge does not update ARP
Thanks for reporting this bug and the detailed reproduction
instructions. I would mark it high, but since you offer a workaround
I'll mark it medium instead.
What does your /etc/modprobe.d/bonding show?
I've not used this combination myself, but from those who have, a few
things do appear
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/785668
Title:
bonding inside a bridge does not update
Actually, I may be wrong about this being a kernel issue.
Are you always able to ping the remote host from the kvm host, even when
you can't do so from the VM?
In addition to kvmhost's /etc/modprove.d/bonding.conf, can you also
please provide the configuration info for the KVM vm? (If a libvirt
Yup, I can reproduce this 100%.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/785668
Title:
bonding inside a bridge does not update ARP correctly when bridged net
accessed from
I'm setting up networking as described above, and then starting virtual
machines with:
sudo tunctl -u 1000 -g 1000 -t tap0
sudo /sbin/ifconfig $1 0.0.0.0 up
sudo brctl addif br0 tap0
kvm -drive file=disk.img,if=virtio,cache=none,boot=on -m 1024 -vnc :1
-net nic,model=virtio -net
Following the advice toward the bottom of
http://forum.proxmox.com/archive/index.php/t-2676.html?s=e8a9cfc9a128659e4a61efec0b758d3e
I was able to get this to work with balance-rr by changing a few bridge
properties. The following was my /etc/network/interfaces:
# This file describes the
21 matches
Mail list logo
