2019-07-11 07:19:27 |
bugproxy |
bug |
|
|
added bug |
2019-07-11 07:19:29 |
bugproxy |
tags |
|
architecture-s39064 bugnameltc-179025 severity-high targetmilestone-inin1804 |
|
2019-07-11 07:19:30 |
bugproxy |
ubuntu: assignee |
|
Skipper Bug Screeners (skipper-screen-team) |
|
2019-07-11 07:19:32 |
bugproxy |
affects |
ubuntu |
qemu (Ubuntu) |
|
2019-07-11 07:19:33 |
bugproxy |
bug |
|
|
added subscriber CDE Administration |
2019-07-11 07:19:35 |
bugproxy |
bug |
|
|
added subscriber Heinz-Werner Seeck |
2019-07-11 07:19:37 |
bugproxy |
bug |
|
|
added subscriber Frank Heimes |
2019-07-11 07:19:38 |
bugproxy |
bug |
|
|
added subscriber Lou Peers |
2019-07-11 07:26:01 |
Frank Heimes |
bug task added |
|
ubuntu-z-systems |
|
2019-07-11 07:26:50 |
Frank Heimes |
ubuntu-z-systems: status |
New |
Triaged |
|
2019-07-11 07:26:54 |
Frank Heimes |
ubuntu-z-systems: importance |
Undecided |
High |
|
2019-07-11 07:27:14 |
Frank Heimes |
ubuntu-z-systems: assignee |
|
Canonical Server Team (canonical-server) |
|
2019-07-11 07:28:07 |
Frank Heimes |
information type |
Private |
Public |
|
2019-07-11 07:31:19 |
Christian Ehrhardt |
nominated for series |
|
Ubuntu Bionic |
|
2019-07-11 07:31:19 |
Christian Ehrhardt |
bug task added |
|
qemu (Ubuntu Bionic) |
|
2019-07-11 07:31:19 |
Christian Ehrhardt |
nominated for series |
|
Ubuntu Disco |
|
2019-07-11 07:31:19 |
Christian Ehrhardt |
bug task added |
|
qemu (Ubuntu Disco) |
|
2019-07-11 07:31:24 |
Christian Ehrhardt |
qemu (Ubuntu Bionic): status |
New |
Incomplete |
|
2019-07-11 07:31:25 |
Christian Ehrhardt |
qemu (Ubuntu Disco): status |
New |
Incomplete |
|
2019-07-11 07:31:28 |
Christian Ehrhardt |
qemu (Ubuntu): status |
New |
In Progress |
|
2019-07-11 07:32:23 |
Christian Ehrhardt |
nominated for series |
|
Ubuntu Cosmic |
|
2019-07-11 07:32:23 |
Christian Ehrhardt |
bug task added |
|
qemu (Ubuntu Cosmic) |
|
2019-07-11 07:32:29 |
Christian Ehrhardt |
qemu (Ubuntu Cosmic): status |
New |
Won't Fix |
|
2019-07-12 08:29:31 |
bugproxy |
attachment added |
|
set of bionic patches https://bugs.launchpad.net/bugs/1836154/+attachment/5276661/+files/bionic.tgz |
|
2019-07-12 09:39:22 |
bugproxy |
attachment added |
|
v2 bionic patches https://bugs.launchpad.net/bugs/1836154/+attachment/5276671/+files/bionic.tgz |
|
2019-07-16 10:27:45 |
Christian Ehrhardt |
description |
Feature request to be applied to Ubuntu 18.04 - qemu.
The commit information is already provided within
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1830238
+
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1836066
Once this feature is accepted, all required information for integration will be provided by IBM (qemu 4.1 down to 2.11) |
Feature request to be applied to Ubuntu 18.04 - qemu.
The commit information is already provided within
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1830238
+
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1836066
Once this feature is accepted, all required information for integration will be provided by IBM (qemu 4.1 down to 2.11)
FYI: related kernel part in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836153 |
|
2019-07-16 10:37:38 |
Christian Ehrhardt |
description |
Feature request to be applied to Ubuntu 18.04 - qemu.
The commit information is already provided within
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1830238
+
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1836066
Once this feature is accepted, all required information for integration will be provided by IBM (qemu 4.1 down to 2.11)
FYI: related kernel part in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836153 |
[Impact]
* new models of s390x chips added new facilities which will help
performant and feature-ful execution of guests.
[Test Case]
#1 against regressions we should run workloads as we ahve run them
before, e.g. the regression test set that the server team usually
runs - obviously none of these should be affected.
#2 for the actual z14 GA2 and the z15 cpu model one needs the new HW to
test these types. In this case IBM will do those verifications as they
have such Hardware available. On that guests with those new types
should be used and tested. On older hardware they will fail to start
lacking some facilities which are part of the new CPU models.
[Regression Potential]
* The changes on s390x itself are mostly isolated
Backports required to adapt a few things for Bionic and in general
needed updated headers. If in review we missed something there this
might affect other workloads and IMHO is the regression potential to
keep in mind.
[Other Info]
* This SRU is for the defined other safe cases "For Long Term Support
releases we regularly want to enable new hardware. Such changes are
appropriate provided that we can ensure not to affect upgrades on
existing hardware. For example, modaliases of newly introduced drivers
must not overlap with previously shipped drivers. This also includes
updating hardware description data such as udev's keymaps, media-
player-info, mobile broadband vendors, or PCI vendor/product list
updates." from:
https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases
In this case the new facilities and modes will and can only be used on
those newer machines.
Fortunately the changes to those definitions in qemu are isolated to
CPU models and should not affect other (already existing) cpu models.
Therefore we can add it
* This is very similar to
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1780773
where we added the z14 ZR 1 type, just this time the new types change
more which means more code, but also more benefit to use them.
---
Feature request to be applied to Ubuntu 18.04 - qemu.
The commit information is already provided within
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1830238
+
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1836066
Once this feature is accepted, all required information for integration will be provided by IBM (qemu 4.1 down to 2.11)
FYI: related kernel part in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836153 |
|
2019-07-16 10:37:53 |
Christian Ehrhardt |
description |
[Impact]
* new models of s390x chips added new facilities which will help
performant and feature-ful execution of guests.
[Test Case]
#1 against regressions we should run workloads as we ahve run them
before, e.g. the regression test set that the server team usually
runs - obviously none of these should be affected.
#2 for the actual z14 GA2 and the z15 cpu model one needs the new HW to
test these types. In this case IBM will do those verifications as they
have such Hardware available. On that guests with those new types
should be used and tested. On older hardware they will fail to start
lacking some facilities which are part of the new CPU models.
[Regression Potential]
* The changes on s390x itself are mostly isolated
Backports required to adapt a few things for Bionic and in general
needed updated headers. If in review we missed something there this
might affect other workloads and IMHO is the regression potential to
keep in mind.
[Other Info]
* This SRU is for the defined other safe cases "For Long Term Support
releases we regularly want to enable new hardware. Such changes are
appropriate provided that we can ensure not to affect upgrades on
existing hardware. For example, modaliases of newly introduced drivers
must not overlap with previously shipped drivers. This also includes
updating hardware description data such as udev's keymaps, media-
player-info, mobile broadband vendors, or PCI vendor/product list
updates." from:
https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases
In this case the new facilities and modes will and can only be used on
those newer machines.
Fortunately the changes to those definitions in qemu are isolated to
CPU models and should not affect other (already existing) cpu models.
Therefore we can add it
* This is very similar to
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1780773
where we added the z14 ZR 1 type, just this time the new types change
more which means more code, but also more benefit to use them.
---
Feature request to be applied to Ubuntu 18.04 - qemu.
The commit information is already provided within
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1830238
+
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1836066
Once this feature is accepted, all required information for integration will be provided by IBM (qemu 4.1 down to 2.11)
FYI: related kernel part in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836153 |
[Impact]
* new models of s390x chips added new facilities which will help
performant and feature-ful execution of guests on those new systems.
[Test Case]
#1 against regressions we should run workloads as we ahve run them
before, e.g. the regression test set that the server team usually
runs - obviously none of these should be affected.
#2 for the actual z14 GA2 and the z15 cpu model one needs the new HW to
test these types. In this case IBM will do those verifications as they
have such Hardware available. On that guests with those new types
should be used and tested. On older hardware they will fail to start
lacking some facilities which are part of the new CPU models.
[Regression Potential]
* The changes on s390x itself are mostly isolated
Backports required to adapt a few things for Bionic and in general
needed updated headers. If in review we missed something there this
might affect other workloads and IMHO is the regression potential to
keep in mind.
[Other Info]
* This SRU is for the defined other safe cases "For Long Term Support
releases we regularly want to enable new hardware. Such changes are
appropriate provided that we can ensure not to affect upgrades on
existing hardware. For example, modaliases of newly introduced drivers
must not overlap with previously shipped drivers. This also includes
updating hardware description data such as udev's keymaps, media-
player-info, mobile broadband vendors, or PCI vendor/product list
updates." from:
https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases
In this case the new facilities and modes will and can only be used on
those newer machines.
Fortunately the changes to those definitions in qemu are isolated to
CPU models and should not affect other (already existing) cpu models.
Therefore we can add it
* This is very similar to
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1780773
where we added the z14 ZR 1 type, just this time the new types change
more which means more code, but also more benefit to use them.
---
Feature request to be applied to Ubuntu 18.04 - qemu.
The commit information is already provided within
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1830238
+
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1836066
Once this feature is accepted, all required information for integration will be provided by IBM (qemu 4.1 down to 2.11)
FYI: related kernel part in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836153 |
|
2019-07-16 10:38:50 |
Frank Heimes |
ubuntu-z-systems: status |
Triaged |
In Progress |
|
2019-07-29 11:26:21 |
Christian Ehrhardt |
qemu (Ubuntu Disco): status |
Incomplete |
Triaged |
|
2019-07-29 11:26:22 |
Christian Ehrhardt |
qemu (Ubuntu Bionic): status |
Incomplete |
Triaged |
|
2019-07-29 12:00:08 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/370708 |
|
2019-07-29 12:00:33 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/370709 |
|
2019-07-30 10:25:23 |
Launchpad Janitor |
qemu (Ubuntu): status |
In Progress |
Fix Released |
|
2019-08-21 11:33:37 |
Christian Ehrhardt |
description |
[Impact]
* new models of s390x chips added new facilities which will help
performant and feature-ful execution of guests on those new systems.
[Test Case]
#1 against regressions we should run workloads as we ahve run them
before, e.g. the regression test set that the server team usually
runs - obviously none of these should be affected.
#2 for the actual z14 GA2 and the z15 cpu model one needs the new HW to
test these types. In this case IBM will do those verifications as they
have such Hardware available. On that guests with those new types
should be used and tested. On older hardware they will fail to start
lacking some facilities which are part of the new CPU models.
[Regression Potential]
* The changes on s390x itself are mostly isolated
Backports required to adapt a few things for Bionic and in general
needed updated headers. If in review we missed something there this
might affect other workloads and IMHO is the regression potential to
keep in mind.
[Other Info]
* This SRU is for the defined other safe cases "For Long Term Support
releases we regularly want to enable new hardware. Such changes are
appropriate provided that we can ensure not to affect upgrades on
existing hardware. For example, modaliases of newly introduced drivers
must not overlap with previously shipped drivers. This also includes
updating hardware description data such as udev's keymaps, media-
player-info, mobile broadband vendors, or PCI vendor/product list
updates." from:
https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases
In this case the new facilities and modes will and can only be used on
those newer machines.
Fortunately the changes to those definitions in qemu are isolated to
CPU models and should not affect other (already existing) cpu models.
Therefore we can add it
* This is very similar to
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1780773
where we added the z14 ZR 1 type, just this time the new types change
more which means more code, but also more benefit to use them.
---
Feature request to be applied to Ubuntu 18.04 - qemu.
The commit information is already provided within
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1830238
+
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1836066
Once this feature is accepted, all required information for integration will be provided by IBM (qemu 4.1 down to 2.11)
FYI: related kernel part in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836153 |
[Impact]
* new models of s390x chips added new facilities which will help
performant and feature-ful execution of guests on those new systems.
[Test Case]
#1 against regressions we should run workloads as we have run them
before, e.g. the regression test set that the server team usually
runs - obviously none of these should be affected.
#2 for the actual z14 GA2 and the z15 cpu model one needs the new HW to
test these types. In this case IBM will do those verification as they
have such Hardware available. On that guests with those new types
should be used and tested. On older hardware they will fail to start
lacking some facilities which are part of the new CPU models.
[Regression Potential]
* The changes on s390x itself are mostly isolated
Backports required to adapt a few things for Bionic and in general
needed updated headers. If in review we missed something there this
might affect other workloads and IMHO is the regression potential to
keep in mind.
[Other Info]
* This SRU is for the defined other safe cases "For Long Term Support
releases we regularly want to enable new hardware. Such changes are
appropriate provided that we can ensure not to affect upgrades on
existing hardware. For example, modaliases of newly introduced drivers
must not overlap with previously shipped drivers. This also includes
updating hardware description data such as udev's keymaps, media-
player-info, mobile broadband vendors, or PCI vendor/product list
updates." from:
https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases
In this case the new facilities and modes will and can only be used on
those newer machines.
Fortunately the changes to those definitions in qemu are isolated to
CPU models and should not affect other (already existing) cpu models.
Therefore we can add it
* This is very similar to
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1780773
where we added the z14 ZR 1 type, just this time the new types change
more which means more code, but also more benefit to use them.
---
Feature request to be applied to Ubuntu 18.04 - qemu.
The commit information is already provided within
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1830238
+
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1836066
Once this feature is accepted, all required information for integration will be provided by IBM (qemu 4.1 down to 2.11)
FYI: related kernel part in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836153 |
|
2019-08-22 08:25:07 |
Christian Ehrhardt |
qemu (Ubuntu Disco): status |
Triaged |
In Progress |
|
2019-08-22 08:25:09 |
Christian Ehrhardt |
qemu (Ubuntu Bionic): status |
Triaged |
In Progress |
|
2019-08-27 09:38:03 |
Robie Basak |
qemu (Ubuntu Disco): status |
In Progress |
Fix Committed |
|
2019-08-27 09:38:05 |
Robie Basak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
2019-08-27 09:38:07 |
Robie Basak |
bug |
|
|
added subscriber SRU Verification |
2019-08-27 09:38:11 |
Robie Basak |
tags |
architecture-s39064 bugnameltc-179025 severity-high targetmilestone-inin1804 |
architecture-s39064 bugnameltc-179025 severity-high targetmilestone-inin1804 verification-needed verification-needed-disco |
|
2019-08-27 09:38:49 |
Robie Basak |
qemu (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
2019-08-27 09:38:55 |
Robie Basak |
tags |
architecture-s39064 bugnameltc-179025 severity-high targetmilestone-inin1804 verification-needed verification-needed-disco |
architecture-s39064 bugnameltc-179025 severity-high targetmilestone-inin1804 verification-needed verification-needed-bionic verification-needed-disco |
|
2019-08-28 13:50:17 |
bugproxy |
tags |
architecture-s39064 bugnameltc-179025 severity-high targetmilestone-inin1804 verification-needed verification-needed-bionic verification-needed-disco |
architecture-s39064 bugnameltc-179025 severity-high targetmilestone-inin1804 verification-done-disco verification-needed verification-needed-bionic |
|
2019-08-28 17:19:47 |
bugproxy |
tags |
architecture-s39064 bugnameltc-179025 severity-high targetmilestone-inin1804 verification-done-disco verification-needed verification-needed-bionic |
architecture-s39064 bugnameltc-179025 severity-high targetmilestone-inin1804 verification-done verification-done-bionic verification-done-disco |
|
2019-08-29 05:20:59 |
Frank Heimes |
ubuntu-z-systems: status |
In Progress |
Fix Committed |
|
2019-09-05 10:48:22 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
2019-09-05 10:51:35 |
Launchpad Janitor |
qemu (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
2019-09-05 10:58:19 |
Launchpad Janitor |
qemu (Ubuntu Disco): status |
Fix Committed |
Fix Released |
|
2019-09-05 11:01:13 |
Andrew Cloke |
ubuntu-z-systems: status |
Fix Committed |
Fix Released |
|