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 changed:

  [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
+  * 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
+  * 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.
+  * 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 TBD - Openstack to test the PPA
-    #2 TBD - IBM to confirm no issues around HTM / VSMT being added
-    #3 TBD - 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.
+ 
+  * Lets make sure we catched all pre-checks:
+    #1 TBD - Openstack to test the PPA
+    #2 TBD - IBM to confirm no issues around HTM being added
+    #3 TBD - 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 protected]> - 
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.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815477

Title:
  Upgrade QEMU to version 2.11.2 in Ubuntu 18.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1815477/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to