kernel-packages team mailing list archive

[Ron <1215051@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

We have experienced problems on Raring with bridged KVM/QEMU guests
loosing network connection after upgrading any host server to kernel
3.8.0-27, and 3.8.0-29.  This has occurred on 4 separate host machines.

This tends to happen sooner / more often, to guests which generate more
traffic than others.  The only way to recover networking is to shutdown
or force-stop the guest, and restart it.  We have attempted to do a
live-migration of a guest in this condition, which resulted in the
source-host server kernel panicing.

All host diagnostics including: ifconfig, "virsh domiflist", and "brctl
show" outputs look identical to working guests.  On the guest, the
interface appears up, there are no syslog errors, the guest can ping
it's own address, but any outgoing communication fails.

This looks just like Ubuntu Precise bug #997978, which affected us last
year as well..

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: Confirmed

** Attachment added: "version.log"
   https://bugs.launchpad.net/bugs/1215051/+attachment/3780993/+files/version.log

-- 
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/1215051

Title:
  KVM/QEMU guest bridged network loss on kernels 3.8.0-27, and 29

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  We have experienced problems on Raring with bridged KVM/QEMU guests
  loosing network connection after upgrading any host server to kernel
  3.8.0-27, and 3.8.0-29.  This has occurred on 4 separate host
  machines.

  This tends to happen sooner / more often, to guests which generate
  more traffic than others.  The only way to recover networking is to
  shutdown or force-stop the guest, and restart it.  We have attempted
  to do a live-migration of a guest in this condition, which resulted in
  the source-host server kernel panicing.

  All host diagnostics including: ifconfig, "virsh domiflist", and
  "brctl show" outputs look identical to working guests.  On the guest,
  the interface appears up, there are no syslog errors, the guest can
  ping it's own address, but any outgoing communication fails.

  This looks just like Ubuntu Precise bug #997978, which affected us
  last year as well..

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215051/+subscriptions