Include QEMU 2.6.1 stable into Ubuntu 16.10

Bug #1617055 reported by bugproxy
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
qemu (Ubuntu)
Fix Released
Medium
Taco Screen team

Bug Description

QEMU 2.6.1 has important fixes for Power, such as:

d917e88d85a147a99f38a62a4f95cac21e366d51 vfio: Fix broken EEH

Hence, we would like to request QEMU in Ubuntu 16.10 to use the latest stable version available, which is currently QEMU 2.6.1.

---

2.6.1 is full of bugfixes only, mostly one liners. I don't see any new features, or compat breaks.

CVE References

bugproxy (bugproxy)
tags: added: architecture-ppc64le bugnameltc-145587 severity-critical targetmilestone-inin1610
Changed in ubuntu:
assignee: nobody → Taco Screen team (taco-screen-team)
affects: ubuntu → qemu (Ubuntu)
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

The intent is to update qemu as soon as it hits debian.

Changed in qemu (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2016-09-06 10:50 EDT-------
Serge,

It seems that qemu 2.6.1 will not make 16.10. If that is try, can Canonical cherry pick this patch then?

Thanks

Revision history for this message
Nish Aravamudan (nacc) wrote :

Hi Breno,

So 2.6.1 seems unlikely to make it in at this point, given that Debian has not updated yet.

Is the only patch needed d917e88d85a147a99f38a62a4f95cac21e366d51? Can you provide a description of the bug it fixes?

Changed in qemu (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Breno Leitão (breno-leitao) wrote :

Hi Nish,

I understand that the major issue is this only patch. Leonardo can confirm here.
This patch fixes a QEMU bug. The backend vfio_eeh_container_op() communicates with host kernel for all EEH operations including retrieving PE's state. The function returns 0 (normal state) unconditionally when retrieving PE's state. That's why the frozen PE can't be detected by guest kernel.

Since this is an EEH issue, this is very POWER specific.

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

I dunno, I'd try for 2.6.1 to be included, it has so many good things in it for POWER and for s390x.

summary: - Include QEMU 2.6.1 stable into Ubuntu 16.10
+ [FFe] Include QEMU 2.6.1 stable into Ubuntu 16.10
summary: - [FFe] Include QEMU 2.6.1 stable into Ubuntu 16.10
+ Include QEMU 2.6.1 stable into Ubuntu 16.10
Changed in qemu (Ubuntu):
status: Incomplete → Confirmed
description: updated
Revision history for this message
Dimitri John Ledkov (xnox) wrote :
Changed in qemu (Ubuntu):
status: Confirmed → In Progress
Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2016-09-10 21:07 EDT-------
(In reply to comment #7)
> Hi Nish,
>
> I understand that the major issue is this only patch. Leonardo can confirm
> here.

Yes, this patch is definitely required because it fixes an important bug fix for the EEH feature. Without it EEH would be broken.

However, if possible, I would like to have 2.6.1 in Ubuntu 16.10. It is a bug fix only release on top of 2.6. Releasing 2.6 instead of 2.6.1 means a user is getting something with lots of known issues already fixed by the community.

Revision history for this message
Steve Langasek (vorlon) wrote :

Since this is a bugfix-only release, no FFe is required. Please make sure you test it rigorously.

Changed in qemu (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package qemu - 1:2.6.1+dfsg-0ubuntu1

---------------
qemu (1:2.6.1+dfsg-0ubuntu1) yakkety; urgency=medium

  * New upstream release. LP: #1617055.
  * Revert fix for CVE-2016-5403, causes regression see USN-3047-2.

 -- Dimitri John Ledkov <email address hidden> Fri, 09 Sep 2016 23:33:57 +0100

Changed in qemu (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.