All autopkgtests for the newly accepted qemu (1:2.11+dfsg-1ubuntu7.21) for bionic have finished running. The following regressions have been reported in tests triggered by the package:
vagrant-mutate/1.2.0-3 (armhf) systemd/237-3ubuntu10.31 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#qemu [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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: Fix Committed 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
