[Bug 1779162] Please test proposed package

[Corey Bryant]

Hello bugproxy, or anyone else affected,

Accepted qemu into pike-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.

Please help us by testing this new package. To enable the -proposed
repository:

  sudo add-apt-repository cloud-archive:pike-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-pike-needed to verification-pike-done. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-pike-failed. In either case, details of your testing
will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!

** Changed in: cloud-archive/pike
       Status: Triaged => Fix Committed

** Tags added: verification-pike-needed

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

Title:
  qemu versions 2.10 and 2.11 have error during migration of larger
  guests

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive pike series:
  Fix Committed
Status in Ubuntu on IBM z Systems:
  New
Status in qemu package in Ubuntu:
  Fix Released
Status in qemu source package in Artful:
  Won't Fix

Bug description:
  == Comment: #0 - Christian Borntraeger  - 2018-06-28 06:39:27 ==
  Migration fails with larger guests (e.g. 10GB)  on a z system prints an error message in the log 

  see /var/log/libvirt/qemu/...
  [...]
  qemu-system-s390x: KVM_S390_SET_CMMA_BITS failed: Bad address

  This messes up guest state for the CMMA values (guest data corruption)

  This is fixed with

  commit 46fa893355e0bd88f3c59b886f0d75cbd5f0bbbe
  Author:     Claudio Imbrenda <imbrenda at linux.vnet.ibm.com>
  AuthorDate: Thu Jan 18 18:51:44 2018 +0100
  Commit:     Cornelia Huck <cohuck at redhat.com>
  CommitDate: Mon Jan 22 11:04:52 2018 +0100

      s390x: fix storage attributes migration for non-small guests
      
      Fix storage attribute migration so that it does not fail for guests
      with more than a few GB of RAM.
      With such guests, the index in the buffer would go out of bounds,
      usually by large amounts, thus receiving -EFAULT from the kernel.
      Migration itself would be successful, but storage attributes would then
      not be migrated completely.
      
      This patch fixes the out of bounds access, and thus migration of all
      storage attributes when the guest have large amounts of memory.
      
      Cc: qemu-stable at nongnu.org
      Signed-off-by: Claudio Imbrenda <imbrenda at linux.vnet.ibm.com>
      Fixes: 903fd80b03243476 ("s390x/migration: Storage attributes device")
      Message-Id: <1516297904-18188-1-git-send-email-imbrenda at linux.vnet.ibm.com>
      Reviewed-by: Christian Borntraeger <borntraeger at de.ibm.com>
      Signed-off-by: Cornelia Huck <cohuck at redhat.com>

  This fix is part of 2.11.1 so the qemu in bionic is fine.
  The qemu in artful, as well as the qemu in the cloud archives for 16.04 need this fix, so we have
  affected qemus in 17.10 and 16.04. 

  Regarding 16.04:
  The bug only triggers for host kernels >= 4.13 - in other words when you combine HWE kernel with the qemu from the cloud archive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1779162/+subscriptions