Hello bugproxy, or anyone else affected,

Accepted qemu into disco-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:3.1+dfsg-
2ubuntu3.7 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  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-needed-disco to verification-done-disco. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-disco. In either case, without details of your
testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: qemu (Ubuntu Disco)
       Status: In Progress => Fix Committed

** Tags removed: verification-done-disco
** Tags added: verification-needed verification-needed-disco

** Changed in: qemu (Ubuntu Bionic)
       Status: In Progress => Fix Committed

** Tags removed: verification-done-bionic
** Tags added: verification-needed-bionic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1842774

Title:
  Enhanced Hardware Support - Finalize Naming

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in qemu source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Released
Status in qemu source package in Disco:
  Fix Committed

Bug description:
  @SRU Team: For SRU template of Qemu please scroll down ...

  SRU Justification Kernel:
  =========================

  [Impact]

  * Add / activate support for IBM z15 and LinuxONE III systems

  [Fix]

  * a0e2251132995b962281aa80ab54a9288f9e0b6b a0e2251 "s390: add support
  for IBM z15 machines"

  [Test Case]

  * check and verify cpuinfo - regression testing is possible by
  Canonical/me

  * functional testing is currently only doable by IBM

  [Regression Potential]

  * There is regression potential with having new code in and the flags
  added/active

  * but the code changes are pretty straight forward, just add config,
  cases and defs

  * and are not used on existing systems, just on the new generation
  that is not yet out in the field

  [Other Info]

  * SRU of LP 1842916 merged with (this) LP 1842774

  
  ---

  
  SRU Template for qemu as the impact/scope is different
  ======================================================

  [Impact]

  * Update naming of the new HW Generation

  * Now that the systems are released people might look for types matching
    the name and no one really knows "IBM 8561 GA1".

  * Help users to identify the cpu type by backporting the fix that sets the
    defined name.

  [Fix]

  * https://git.qemu.org/?p=qemu.git;a=commit;h=7505deca

  [Test Case]

  * qemu-system-s390x -cpu ? | grep gen15
  s390 gen15a-base     IBM 8561 GA1                        (static, 
migration-safe)
  s390 gen15a          IBM 8561 GA1                        (migration-safe)
  s390 gen15b-base     IBM 8562 GA1                        (static, 
migration-safe)
  s390 gen15b          IBM 8562 GA1                        (migration-safe)

  * With the fix gen15a should be called "IBM z15 GA1"

  [Regression Potential]

  * The only thing changing (for qemu) are some texts e.g. when showing CPU
    types. The cpu type itself that is used in e.g. scripts / commands will
    not change. Therefore the regression risk of the qemu change is next to
    none. The only I can think of is people grepping for the old ID in text
    output, but that seems theoretical and not important.

  [Other Info]

  * For an SRU perspective this is "nice to have" we will only do this
    "along" other higher impact SRUs.

  __________

  This feature request will provide the final naming of the next machine

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to