** Description changed:

+ [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

** Description changed:

  [Impact]
  
-  * new models of s390x chips added new facilities which will help 
-    performant and feature-ful execution of guests.
+  * 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.
+  #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.
+  #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.
+  * 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.
  
+  * 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

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

Title:
  [18.04 FEAT] zKVM: Add hardware CPU Model - qemu part

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

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

Reply via email to