[Bug 997978] Re: KVM images lose connectivity with bridged network
Another update: multiple KVM VM failures over the past couple of days, the lxc-container is working without issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997978 Title: KVM images lose connectivity with bridged network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/997978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997978] [NEW] KVM images lose connectivity with bridged network
Public bug reported: System: --- Dell R410 Dual processor 2.4Ghz w/16G RAM Distributor ID: Ubuntu Description:Ubuntu 12.04 LTS Release:12.04 Codename: precise Setup: - We're running 3 KVM guests, all Ubuntu 12.04 LTS using bridged networking. >From the host: # cat /etc/network/interfaces auto br0 iface br0 inet static address 212.XX.239.98 netmask 255.255.255.240 gateway 212.XX.239.97 bridge_ports eth0 bridge_fd 9 bridge_hello 2 bridge_maxage 12 bridge_stp off # ifconfig eth0 eth0 Link encap:Ethernet HWaddr d4:ae:52:84:2d:5a UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:11278363 errors:0 dropped:3128 overruns:0 frame:0 TX packets:14437384 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:4115980743 (4.1 GB) TX bytes:5451961979 (5.4 GB) Interrupt:36 Memory:da00-da012800 # ifconfig br0 br0 Link encap:Ethernet HWaddr d4:ae:52:84:2d:5a inet addr:212.XX.239.98 Bcast:212.XX.239.111 Mask:255.255.255.240 inet6 addr: fe80::d6ae:52ff:fe84:2d5a/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1720861 errors:0 dropped:0 overruns:0 frame:0 TX packets:1708622 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:210152198 (210.1 MB) TX bytes:300858508 (300.8 MB) # brctl show bridge name bridge id STP enabled interfaces br0 8000.d4ae52842d5a no eth0 I have no default network configured to autostart in libvirt as we're using bridged networking: # virsh net-list --all Name State Autostart - default inactive no # arp Address HWtype HWaddress Flags MaskIface mailer03..com ether 52:54:00:82:5f:0f C br0 mailer01..com ether 52:54:00:d2:f7:31 C br0 mailer02..com ether 52:54:00:d3:8f:91 C br0 dxi-gw2..comether 00:1a:30:2a:b1:c0 C br0 >From one of the guests: mailer01 d41d1355-84e8-ae23-e84e-227bc0231b97 2097152 2097152 1 hvm destroy restart destroy /usr/bin/kvm libvirt-d41d1355-84e8-ae23-e84e-227bc0231b97 libvirt-d41d1355-84e8-ae23-e84e-227bc0231b97 >From within the guest: # cat /etc/network/interfaces # The primary network interface auto eth0 iface eth0 inet static address 212.XX.239.100 netmask 255.255.255.240 network 212.XX.239.96 broadcast 212.XX.239.111 gateway 212.XX.239.97 # ifconfig eth0 Link encap:Ethernet HWaddr 52:54:00:d2:f7:31 inet addr:212.XX.239.100 Bcast:212.XX.239.111 Mask:255.255.255.240 inet6 addr: fe80::5054:ff:fed2:f731/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5631830 errors:0 dropped:0 overruns:0 frame:0 TX packets:6683416 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2027322829 (2.0 GB) TX bytes:2076698690 (2.0 GB) A commandline which starts the KVM guest: /usr/bin/kvm -S -M pc-1.0 -enable-kvm -m 2048 -smp 1,sockets=1,cores=1,threads=1 -name mailer01 -uuid d41d1355-84e8-ae23-e84e-227bc0231b97 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/mailer01.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -drive file=/dev/mapper/vg_main-mailer01--root,if=none,id=drive-ide0-0-0,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -drive file=/dev/mapper/vg_main-mailer01--swap,if=none,id=drive-ide0-0-1,format=raw -device ide-drive,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 -netdev tap,fd=18,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:d2:f7:31,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -vnc 127.0.0.1:0 -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 Problem: Periodically (at least once a day), one or more of the guests lose network connectivity. Ping responds with 'host unreachable', even from the dom host. Logging in via the serial console shows no problems: eth0 is up, can ping the local host, but no outside connectivity. Restart
[Bug 997978] Re: KVM images lose connectivity with bridged network
This happens to one of the VMs at any one time (on Wednesday two failed, about 2 hours apart). There's no discernible pattern in terms of time of day or length of a VMs uptime. The next time one fails (they've been stable today), I'll do a route -n and post the output. For record, currently (with a working VM), route -n shows: $ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 212.XX.239.97 0.0.0.0 UG10000 eth0 212.XX.239.96 0.0.0.0 255.255.255.240 U 0 00 eth0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997978 Title: KVM images lose connectivity with bridged network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/997978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997978] Re: KVM images lose connectivity with bridged network
I tried building the container this morning using both your file above, and the following: lxc.network.type=veth lxc.network.link=br0 lxc.network.flags=up lxc.network.ipv4=212.XX.239.103/28 lxc.network.name=eth0 # lxc-create -t ubuntu -f lxc.conf -n lxc1 debootstrap is /usr/sbin/debootstrap Checking cache download in /var/cache/lxc/precise/rootfs-amd64 ... Copy /var/cache/lxc/precise/rootfs-amd64 to /var/lib/lxc/lxc1/rootfs ... Copying rootfs to /var/lib/lxc/lxc1/rootfs ... ## # The default user is 'ubuntu' with password 'ubuntu'! # Use the 'sudo' command to run tasks as root in the container. ## 'ubuntu' template installed 'lxc1' created But it fails to start: # lxc-start -n lxc1 lxc-start: failed to spawn 'lxc1' /var/log/syslog shows: May 12 09:47:12 dom0 kernel: [ 1107.903216] device vethHzjri2 entered promiscuous mode May 12 09:47:12 dom0 kernel: [ 1107.905151] ADDRCONF(NETDEV_UP): vethHzjri2: link is not ready ifconfig shows a load of virtual devices and brctl shows: # brctl show bridge name bridge id STP enabled interfaces br0 8000.0649d9be1876 no eth0 veth4bkC47 vethHzjri2 vethNBwjzP vethZo4vwt vethhzluzM vethidQWcJ vethmtoeDY vethuPj7Qk vethuxztRp vnet1 (I've tried starting the contain a few times). I'm happy to debug this with you, but lxc isn't software I'm familiar with, unfortunately. Any ideas? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997978 Title: KVM images lose connectivity with bridged network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/997978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997978] Re: KVM images lose connectivity with bridged network
Installed yesterday and rebooted the dom0 machine and thus all virtual machines. Will report back if there are any problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997978 Title: KVM images lose connectivity with bridged network To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/997978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997978] Re: KVM images lose connectivity with bridged network
It took a few days, but we've finally had a failure of VM instance 2. It died 2.5 hours ago. Logging into the dom0 host shows the arp table dead for that host: mailer02..com (incomplete) br0 Logging into the machine itself via console: root:~# ifconfig eth0 Link encap:Ethernet HWaddr 52:54:00:d3:8f:91 inet addr:212.XX.239.101 Bcast:212.XX.239.111 Mask:255.255.255.240 inet6 addr: fe80::5054:ff:fed3:8f91/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:6893246 errors:0 dropped:0 overruns:0 frame:0 TX packets:8242152 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2290922658 (2.2 GB) TX bytes:3314395798 (3.3 GB) root:~# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 212.XX.239.97 0.0.0.0 UG10000 eth0 212.XX.239.96 0.0.0.0 255.255.255.240 U 0 00 eth0 Restarting the network on the vm (/etc/init.d/networking restart) does nothing. Rebooting the VM brings it back to life. I'm happy to try with the container again, but using the instructions provided (even with some additional research online), I can't get it running. Please advise. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997978 Title: KVM images lose connectivity with bridged network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/997978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997978] Re: KVM images lose connectivity with bridged network
Hey, There is no DHCP server for that network, which is why I set up the static IPs. The cgroup-bin package wasn't installed, I installed that and then grep showed some output: root:~# grep cgroup /proc/self/mounts cgroups /sys/fs/cgroup tmpfs rw,relatime,mode=755 0 0 cgroup /sys/fs/cgroup/cpu cgroup rw,relatime,cpu 0 0 cgroup /sys/fs/cgroup/cpuacct cgroup rw,relatime,cpuacct 0 0 cgroup /sys/fs/cgroup/devices cgroup rw,relatime,devices 0 0 cgroup /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0 cgroup /sys/fs/cgroup/freezer cgroup rw,relatime,freezer 0 0 The container has now started. I'll configure it so it's running the same software as the other VMs and let's see what happens over the coming days. Thanks for your help so far. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997978 Title: KVM images lose connectivity with bridged network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/997978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997978] Re: KVM images lose connectivity with bridged network
An update: had a different KVM VM die today (same symptoms/resolution as previously); the LXC instance remains working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997978 Title: KVM images lose connectivity with bridged network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/997978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997978] Re: KVM images lose connectivity with bridged network
This bug is considered fixed for me. Not a single network glitch since installing the package from PPA. Many thanks to the development team! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997978 Title: KVM images lose connectivity with bridged network To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/997978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
