Upgrade QEMU to version 2.11.2 in Ubuntu 18.04.1

Bug #1815477 reported by bugproxy
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
The Ubuntu-power-systems project
Invalid
High
Unassigned
qemu (Ubuntu)
Fix Released
Medium
Unassigned
Bionic
Incomplete
Medium
Unassigned

Bug Description

[Impact]

 * qemu Upstream maintains stable branches to collect considered
   to be safe patches - we are at 2.11.1 atm and requested to consider
   the most recent 2.11.2

[Test Case]

 * Being a stable but full minor release means there is no single good
   test to verify. Instead we will pass plenty of regression checks on it
   before calling it good.
 * The biggest single change is on intel-iommu which we will test
   explicitly using manual passthrough tests

[Regression Potential]

 * Due to the nature of the change (more than a single fix, affecting
   multiple areas of qemu) the chances are higher to hit a regression.
   To avoid hitting any in the field I'll run the full qemu regression
   suite we have but also would want to leave it longer in proposed and
   e.g. ask the Openstack Team to give it a test before releasing.
 * In regard to "327d4645 spapr: make pseries-2.11 the default machine
   type" and its siblings as well as VSMT which caused trouble in the past
   we will need IBM to re-check for PPC if the resulting build is ok
   according to their testing as well.

[Other Info]

 * Lets make sure we catched all pre-checks:
   #1 DONE - Openstack to test the PPA
   #2 TBD - IBM to confirm no new issues on ppc/s390x platforms
   #3 DONE - Canonical migration and general Virt regression checks
   Only once those are all confirmed we will put it into SRU review and
   there retest #3 and the passthrough cases.

---

== Comment: #0 - Leonardo Augusto Guimaraes Garcia <email address hidden> - 2019-02-01 13:00:47 ==
Since June 2018 QEMU has a more recent stable version (2.11.2) than the one provided in Ubuntu 18.04.1 (2.11.1). This new version comes with a number of bug fixes, which should be incorporated to Ubuntu 18.04.1.

bugproxy (bugproxy)
tags: added: architecture-all bugnameltc-175215 severity-high targetmilestone-inin18041
Changed in ubuntu:
assignee: nobody → Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
affects: ubuntu → qemu (Ubuntu)
Changed in qemu (Ubuntu):
status: New → Triaged
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hi Leonardo,
I'm generally for that, but we are still in a freeze for 18.04.2 being released and even then there is a qemu in the SRU queue that has to clear first.
I'll work on that once these blockers are removed, if there is any extra urgency behind it let me know.

Changed in qemu (Ubuntu):
importance: Undecided → Medium
Frank Heimes (fheimes)
Changed in ubuntu-power-systems:
status: New → Triaged
importance: Undecided → Medium
Manoj Iyer (manjo)
Changed in qemu (Ubuntu):
assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) → Christian Ehrhardt  (paelzer)
Changed in ubuntu-power-systems:
assignee: nobody → Christian Ehrhardt  (paelzer)
Revision history for this message
Andrew Cloke (andrew-cloke) wrote :

Adjusting "Importance" to reflect tagging.

Changed in ubuntu-power-systems:
importance: Medium → High
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

FYI - The currently ongoing SRU is IMHO ready to be released, but gated by some tests (not broken by qemu but needing cleanup). Furthermore the 2.11.2 changes need the same machine type cleanup as in our former discussion about the same topic - but that I can do on my own.
Just to let you know why this takes a while this time, but IIRC this isn't of a particular urgency right now (let me know you think different) - I checked CVEs all that are contained we have already.

description: updated
Changed in qemu (Ubuntu):
status: Triaged → Fix Released
Changed in qemu (Ubuntu Bionic):
status: New → Triaged
assignee: nobody → Christian Ehrhardt  (paelzer)
Changed in qemu (Ubuntu):
assignee: Christian Ehrhardt  (paelzer) → nobody
Changed in qemu (Ubuntu Bionic):
importance: Undecided → Medium
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

I've got all changes applied fine, tomorrow I'll create PPAs to test

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

There is a test PPA [1] available that we can use to pre-check this before the actual SRU.
Since there are quite some changes I'll run all my checks on the PPA, but I'd ask you to please test ppc64el before I bring that to the SRU Team.

I'll also in a mail poll for Openstack tests.

Setting incomplete until all the safety checks are in.

[1]: https://launchpad.net/~paelzer/+archive/ubuntu/qemu-bionic-1815477-1818264

description: updated
description: updated
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Migration and an assortment of Misc regression checks look good as well.

prep (x86_64) : Pass 20 F/S/N 0/0/0 - RC 0 (15 min 58011 lin)
migrate (x86_64) : Pass 174 F/S/N 0/0/0 - RC 1 (65 min 94379 lin)
cross (x86_64) : Pass 24 F/S/N 0/0/0 - RC 0 (26 min 33911 lin)
misc (x86_64) : Pass 103 F/S/N 0/0/0 - RC 0 (28 min 37689 lin)
qemu (x86_64) : Pass 1 F/S/N 0/0/0 - RC 0 (36 min 2307 lin)

prep (s390x) : Pass 20 F/S/N 0/0/0 - RC 0 (64 min 27361 lin)
migrate (s390x) : Pass 176 F/S/N 0/0/0 - RC 0 (330 min 73152 lin)
cross (s390x) : Pass 24 F/S/N 0/0/0 - RC 0 (397 min 31275 lin)
misc (s390x) : Pass 67 F/S/N 0/0/0 - RC 0 (92 min 20749 lin)

prep (ppc64le) : Pass 20 F/S/N 0/0/0 - RC 0 (67 min 50901 lin)
migrate (ppc64le): Pass 176 F/S/N 0/0/0 - RC 0 (49 min 91964 lin)
cross (ppc64le) : Pass 24 F/S/N 0/0/0 - RC 0 (37 min 34381 lin)
misc (ppc64le) : Pass 73 F/S/N 0/0/0 - RC 0 (36 min 24398 lin)

Just waiting on IBM now (ppc and s390x pre-check) to go on with this.

Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2019-03-20 18:45 EDT-------
After further discussion, IBM is withdrawing this request.

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

@lagarcia - That is unfortunate to hear, as I'm sure people would benefit in general from the fixes in the stable release - if we can ensure well enough that there are no new issues introduced.

So for now I'd ask you to imagine somebody else has requested it and I still would want to get an ack from IBM for ppc64el and s390x prechecking the PPA I provided in comment #5.

If you have clear reasons to abstain (e.g. known issues in 2.11.2) please state them, then we will stop considering 2.11.2 for now.
But if not, please try if you can allocate some test resources and let me know of a ETA when such tests could conclude.

description: updated
Revision history for this message
Frank Heimes (fheimes) wrote :

This ticket was discussed in a call with the outcome that it will be handled differently. Hopefully there was not too much effort that got already spent.
Since this is no longer needed, we think it's best to mention it and drop it now and not wait until the SRU process already started ...

Changed in qemu (Ubuntu Bionic):
status: Triaged → Invalid
status: Invalid → New
status: New → Invalid
Changed in ubuntu-power-systems:
status: Triaged → Invalid
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Sad but ok for now - thanks Frank for the info.
For the coming SRu I'll strip 2.11.2 out and only fix the so far bundled qemu-img fix.

@IBM - I'll leave the PPA up and when you someday think you could verify 2.11.2 on both of your architectures that would be great as we could then revive this effort here.

Changed in qemu (Ubuntu Bionic):
status: Invalid → Incomplete
assignee: Christian Ehrhardt  (paelzer) → nobody
Changed in ubuntu-power-systems:
assignee: Christian Ehrhardt  (paelzer) → nobody
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

And sorry for dragging in even the Openstack team into this who even did their verification in the first day I asked.

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.