linux-image-3.13.0-29-generic - soft lockup in kvm guests

Bug #1333553 reported by Volkmar Glauche on 2014-06-24
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux-lts-trusty (Ubuntu)
Undecided
Unassigned

Bug Description

# lsb_release -rd
Description: Ubuntu 14.04 LTS
Release: 14.04

# apt-cache policy linux-image-generic
linux-image-generic:
  Installiert: 3.13.0.29.35
  Installationskandidat: 3.13.0.29.35
  Versionstabelle:
 *** 3.13.0.29.35 0
        500 http://de.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     3.13.0.24.28 0
        500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

This bug shows on a Fujitsu Primergy RX300 S6 server, upgraded from Ubuntu 12.04 Server (x86_64) to 14.04 Server (x86_64). When running linux-image-3.13.0-29-generic kernel on the server, kvm guests (Windows Server 2008R2, Ubuntu 14.04 Server, Gentoo) show poor performance ~3-4 hours after system boot. In some of the guests, there are messages about cpu soft lockups. This coincides with high load reported by kvm/libvirt for the guests.
The problem does not appear when booting the server with mainline kernel linux-image-3.15.1-031501-generic from Ubuntu kernel PPA.

Matt Symonds (msymonds) wrote :

I am seeing a simular issue on 3.13.0-30 on the host.

It hasn't got as far as a cpu soft lockup but I do get network issues.

64 bytes from 10.3.0.2: icmp_seq=59 ttl=64 time=0.717 ms
64 bytes from 10.3.0.2: icmp_seq=60 ttl=64 time=0.706 ms
64 bytes from 10.3.0.2: icmp_seq=61 ttl=64 time=0.454 ms
64 bytes from 10.3.0.2: icmp_seq=62 ttl=64 time=0.635 ms
64 bytes from 10.3.0.2: icmp_seq=63 ttl=64 time=0.707 ms
64 bytes from 10.3.0.2: icmp_seq=64 ttl=64 time=2333 ms # Starts here
64 bytes from 10.3.0.2: icmp_seq=65 ttl=64 time=856 ms
64 bytes from 10.3.0.2: icmp_seq=66 ttl=64 time=350 ms
64 bytes from 10.3.0.2: icmp_seq=67 ttl=64 time=80.1 ms
64 bytes from 10.3.0.2: icmp_seq=68 ttl=64 time=12.5 ms
64 bytes from 10.3.0.2: icmp_seq=69 ttl=64 time=2.71 ms
64 bytes from 10.3.0.2: icmp_seq=70 ttl=64 time=1.71 ms
64 bytes from 10.3.0.2: icmp_seq=71 ttl=64 time=0.597 ms
64 bytes from 10.3.0.2: icmp_seq=72 ttl=64 time=0.729 ms
64 bytes from 10.3.0.2: icmp_seq=73 ttl=64 time=0.727 ms
64 bytes from 10.3.0.2: icmp_seq=74 ttl=64 time=0.642 ms
64 bytes from 10.3.0.2: icmp_seq=75 ttl=64 time=0.715 ms
64 bytes from 10.3.0.2: icmp_seq=76 ttl=64 time=0.715 ms
64 bytes from 10.3.0.2: icmp_seq=77 ttl=64 time=0.776 ms
64 bytes from 10.3.0.2: icmp_seq=78 ttl=64 time=0.742 ms
64 bytes from 10.3.0.2: icmp_seq=79 ttl=64 time=0.770 ms

I've since upgraded to the 3.14.1 kernel that will be in ubuntu 14.04.01 which has fixed the problem.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-lts-trusty (Ubuntu):
status: New → Confirmed
Jérôme Poulin (jeromepoulin) wrote :

Probably in relation or duplicate of bug #1307473.

I am not sure whether this bug is really a duplicate of #1307473.

I experienced the problems described in this bug report without CPU pinning being used. I might add that I had the impression that Windows guests (Windows Server 2012 R2) were more severly affected than Linux guests. However, Linux guests seemed to be more affected if also running the 3.13 kernel.

In my case, I experienced the problem after upgrading a VM host from Precise (using kernel 3.5.0-52) to Trusty (using kernel 3.13.0-30). For now, I downgraded back to Precise which made the problems go away.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers