** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
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
We're looking very solid on kernel 3.8.0-30, under heavy load. I count
this as resolved.
Thanks again all.
--
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
We now have 12 hours with our entire KVM cluster running on 3.8.0-30
with no outage. Including our high Network I/O guests now.
I will post success/failure once more this week, for final load
verification.
--
You received this bug notification because you are a member of Kernel
Packages, which
I will be upgrading our development cluster of 3 hosts to 3.8.0-30
(proposed) this weekend; for further validation of this new kernel as a
solution.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
It looks like we are on 24 hours uptime, with only one guest. Our only
exception to norm; Friday was a pretty light use day, the office was
very quiet.
By mid-Monday, I will do some network load tests, and load up a dozen or
so VMs. So far 3.8.0-30 seems good..
--
You received this bug notific
I'm absolutely positive this problem does not exist in 3.8.0-26, we have
6 heavy use KVM/QEMU host servers on it.
The bridge network loss definitely occurs on any of these servers, once
upgraded to 3.8.0-27, and/or 3.8.0-29. And it happens pretty quickly,
~1-2 hours max.
I can give the 3.8.0-30
Also, the 3.8.0-30.43 kernel is now available in the -proposed
repository. Would it be possible for you to test this latest kernel and
post back if it resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed.
Thank you in advance!
-
I'd like to perform a bisect to figure out what commit caused this
regression. We need to identify the earliest kernel where the issue
started happening as well as the latest kernel that did not have this
issue.
Can you test the following kernels and post back? We are looking for the
first kernel
Do you not see this bug if you boot back into 3.8.0-26?
** Tags added: performing-bisect raring
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
Due to the nature of this networking-loss bug report, there is no crash
data, nor dump files. This failure occurs silently.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215051/+attachment/3780994/+files/lspci-vnvn.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/bu
11 matches
Mail list logo
