| 2020-08-20 11:19:38 |
bugproxy |
bug |
|
|
added bug |
| 2020-08-20 11:19:40 |
bugproxy |
tags |
|
architecture-s39064 bugnameltc-187747 severity-high targetmilestone-inin2004 |
|
| 2020-08-20 11:19:42 |
bugproxy |
ubuntu: assignee |
|
Skipper Bug Screeners (skipper-screen-team) |
|
| 2020-08-20 11:19:46 |
bugproxy |
affects |
ubuntu |
linux (Ubuntu) |
|
| 2020-08-20 11:23:22 |
Heinz-Werner Seeck |
affects |
linux (Ubuntu) |
s390-tools (Ubuntu) |
|
| 2020-08-20 11:23:44 |
Heinz-Werner Seeck |
summary |
[UBUNTU 20.04]zipl boot loader should check for secure IPL feature before looking up data (was: PV: guest fails to reboot from a disk) |
[UBUNTU 20.04] zipl boot loader should check for secure IPL feature before looking up data (was: PV: guest fails to reboot from a disk) |
|
| 2020-08-20 12:19:29 |
Andrew Cloke |
bug task added |
|
ubuntu-z-systems |
|
| 2020-08-20 12:19:38 |
Andrew Cloke |
ubuntu-z-systems: importance |
Undecided |
High |
|
| 2020-08-20 12:21:14 |
Andrew Cloke |
ubuntu-z-systems: assignee |
|
Canonical Foundations Team (canonical-foundations) |
|
| 2020-08-24 10:11:39 |
Frank Heimes |
nominated for series |
|
Ubuntu Focal |
|
| 2020-08-24 10:11:39 |
Frank Heimes |
bug task added |
|
s390-tools (Ubuntu Focal) |
|
| 2020-08-24 10:11:39 |
Frank Heimes |
nominated for series |
|
Ubuntu Groovy |
|
| 2020-08-24 10:11:39 |
Frank Heimes |
bug task added |
|
s390-tools (Ubuntu Groovy) |
|
| 2020-08-24 10:31:33 |
Frank Heimes |
s390-tools (Ubuntu Groovy): status |
New |
Triaged |
|
| 2020-08-24 10:31:57 |
Frank Heimes |
s390-tools (Ubuntu Groovy): assignee |
Skipper Bug Screeners (skipper-screen-team) |
Canonical Foundations Team (canonical-foundations) |
|
| 2020-08-24 10:32:13 |
Frank Heimes |
s390-tools (Ubuntu Focal): assignee |
|
Canonical Foundations Team (canonical-foundations) |
|
| 2020-08-24 10:32:26 |
Frank Heimes |
ubuntu-z-systems: assignee |
Canonical Foundations Team (canonical-foundations) |
Skipper Bug Screeners (skipper-screen-team) |
|
| 2020-08-24 10:32:32 |
Frank Heimes |
ubuntu-z-systems: status |
New |
Triaged |
|
| 2020-08-26 10:26:35 |
Dimitri John Ledkov |
s390-tools (Ubuntu Groovy): status |
Triaged |
In Progress |
|
| 2020-08-26 14:04:02 |
Frank Heimes |
ubuntu-z-systems: status |
Triaged |
In Progress |
|
| 2020-08-31 20:58:34 |
Launchpad Janitor |
s390-tools (Ubuntu Groovy): status |
In Progress |
Fix Released |
|
| 2020-09-02 12:34:57 |
Francis Ginther |
tags |
architecture-s39064 bugnameltc-187747 severity-high targetmilestone-inin2004 |
architecture-s39064 bugnameltc-187747 id-5f3e969561488979e4dce5fc severity-high targetmilestone-inin2004 |
|
| 2020-10-01 13:01:13 |
Lukas Märdian |
description |
Problem description:
Sometimes a PV guest fails to reboot from a disk.
# How to reproduce?
Try to reboot a PV guest multiple times.
Or using hades (bb/mhartmay/pv branch):
$ for i in $(seq 1 100); do nose2 -v --early-debug tests.test_pv.PVChreiplTestCase; done
# Host kernel used:
5.6.0-rc2-00041-g0c1beb8db4fc
# Host cmdline used:
kvm.nested=1 nokaslr crashkernel=196M selinux=0 root=/dev/disk/by-path/ccw-0.0.1000-part1 rd.dasd=0.0.1000 cio_ignore=all,!condev LANG=en_US.UTF-8 prot_virt=1
# QEMU used:
QEMU emulator version 4.2.50 (v4.2.0-1246-g3d17206cbf41-dirty)
# Guest kernel used:
5.6.0-rc2-00041-g0c1beb8db4fc
# Guest cmdline used:
enforcing=0 console=ttyS0 swiotlb=256000 STARTUP=sshd.sh PV
This is a list of commits that are required to entirely resolve this bug
on top of s390tools-2.12
These commits are zipl related only.
c91d8bd5f9102cb91ba6839cf98c40dd26521cd3
fb62cc9e14591c7f84944148d48ac98114a26d46
f4f2220693ffe2efadfd41e0036f6971aabc1fdd
e0ffb3c584f57783538773b3edabbbb5f48caefc
e67f6300862d939d212d79c4ce5e1249102ddcd3
c4a0933165c7093c2ca52c9ee94e4b074fc9f3f7
cb11d6baec41f14c3e8f6832a13ea0020dcf907d
6c04f977734f55b862b9900abfc325e1db98acd0
ce65c39e18a62743bf65eeec92eaedbe22d035da
19f747847ffb39cb2df43376ff569bf18a026362
eb4e806cdc0801718e3d74b2062700d57f6f4b5a
93a0cb254efe45b5e291283af69d74f531cdc40d
2fe5f27975785a3af91d0b24f88962c7ae82ed44
cc069af26d1c35e35bca9d7db4ee4d8a0f8f5440
0843b7db36af3e30c97fd8be8173debe9f5510b7
1a150b2fe05627adc43cc00dd2291acfff30735a
9a68a25ab609146e0c22ae882a2f80c6da714761
4eea67cd6f100e7db7b71a03495e97a8db96490a
0ac7ce964ed089a2614dbfcffb89bd6c4175992b
0c583ec1a68e998f5ed775a97d7f046aad5df28a
1b65b23b43985cb8a1da2ef399ec6def31bbcc69
454f1427d3edcd94c2e25fe7165d392bcc97567a
71b36d17f019c9e2cf218351520d5b55a6c2d479
41fae58ecd8d0099ce2802f43e6b998eecc818c7
3217e0438fd8ba602706eda8adbb23e74f2f54ad
ae66f795124fb3b5e57637ff002edbf45f05ccbd
d7b816ff58baed404b5406a7c25e390804ff1a76
c367a6bb6529f04bdcb6264ede99439a756dfa3e
943c5dc51d493fd89f8c1b0760656446d5653be6 |
[Impact]
* Sometimes a PV guest fails to reboot from a disk.
* Backporting newer zipl functionality to focal fixes the reboot of protected VMs on IBM Z by checking for the secure IPL feature before looking up data
* This bug was fixed in s390-tools 2.14.0 (which depends on a newer kernel), therefore we cherry-pick just the fixes to zipl, while keeping s390-tools at 2.12.0
[Test Case]
* Secure boot (s390-tools-signed) can only be tested on specific IBM hardware
* Try to reboot a PV guest multiple times.
* Or using hades (bb/mhartmay/pv branch):
$ for i in $(seq 1 100); do nose2 -v --early-debug tests.test_pv.PVChreiplTestCase; done
[Regression Potential]
* regressions in the initial program loader for Z (zipl) could break the creation of new boot devices for s390x
* the package is only available on s390x and thus could only affect IBM Z machines
* Existing boot devices / IPL would not be affected
[Other Info]
* Needs to be tested/verified by IBM internally
* In addition to the patches/cherry-picks provided via the original description, I included fd81728 ("zipl: fix incorrect setup of stage3 flags") from upstream, to fix an issue introduced in commit 6c04f97 ("zipl: consolidate stage3_params structs and stage3 flags")
=== Original Description ===
Problem description:
Sometimes a PV guest fails to reboot from a disk.
# How to reproduce?
Try to reboot a PV guest multiple times.
Or using hades (bb/mhartmay/pv branch):
$ for i in $(seq 1 100); do nose2 -v --early-debug tests.test_pv.PVChreiplTestCase; done
# Host kernel used:
5.6.0-rc2-00041-g0c1beb8db4fc
# Host cmdline used:
kvm.nested=1 nokaslr crashkernel=196M selinux=0 root=/dev/disk/by-path/ccw-0.0.1000-part1 rd.dasd=0.0.1000 cio_ignore=all,!condev LANG=en_US.UTF-8 prot_virt=1
# QEMU used:
QEMU emulator version 4.2.50 (v4.2.0-1246-g3d17206cbf41-dirty)
# Guest kernel used:
5.6.0-rc2-00041-g0c1beb8db4fc
# Guest cmdline used:
enforcing=0 console=ttyS0 swiotlb=256000 STARTUP=sshd.sh PV
This is a list of commits that are required to entirely resolve this bug
on top of s390tools-2.12
These commits are zipl related only.
c91d8bd5f9102cb91ba6839cf98c40dd26521cd3
fb62cc9e14591c7f84944148d48ac98114a26d46
f4f2220693ffe2efadfd41e0036f6971aabc1fdd
e0ffb3c584f57783538773b3edabbbb5f48caefc
e67f6300862d939d212d79c4ce5e1249102ddcd3
c4a0933165c7093c2ca52c9ee94e4b074fc9f3f7
cb11d6baec41f14c3e8f6832a13ea0020dcf907d
6c04f977734f55b862b9900abfc325e1db98acd0
ce65c39e18a62743bf65eeec92eaedbe22d035da
19f747847ffb39cb2df43376ff569bf18a026362
eb4e806cdc0801718e3d74b2062700d57f6f4b5a
93a0cb254efe45b5e291283af69d74f531cdc40d
2fe5f27975785a3af91d0b24f88962c7ae82ed44
cc069af26d1c35e35bca9d7db4ee4d8a0f8f5440
0843b7db36af3e30c97fd8be8173debe9f5510b7
1a150b2fe05627adc43cc00dd2291acfff30735a
9a68a25ab609146e0c22ae882a2f80c6da714761
4eea67cd6f100e7db7b71a03495e97a8db96490a
0ac7ce964ed089a2614dbfcffb89bd6c4175992b
0c583ec1a68e998f5ed775a97d7f046aad5df28a
1b65b23b43985cb8a1da2ef399ec6def31bbcc69
454f1427d3edcd94c2e25fe7165d392bcc97567a
71b36d17f019c9e2cf218351520d5b55a6c2d479
41fae58ecd8d0099ce2802f43e6b998eecc818c7
3217e0438fd8ba602706eda8adbb23e74f2f54ad
ae66f795124fb3b5e57637ff002edbf45f05ccbd
d7b816ff58baed404b5406a7c25e390804ff1a76
c367a6bb6529f04bdcb6264ede99439a756dfa3e
943c5dc51d493fd89f8c1b0760656446d5653be6 |
|
| 2020-10-01 13:01:21 |
Lukas Märdian |
description |
[Impact]
* Sometimes a PV guest fails to reboot from a disk.
* Backporting newer zipl functionality to focal fixes the reboot of protected VMs on IBM Z by checking for the secure IPL feature before looking up data
* This bug was fixed in s390-tools 2.14.0 (which depends on a newer kernel), therefore we cherry-pick just the fixes to zipl, while keeping s390-tools at 2.12.0
[Test Case]
* Secure boot (s390-tools-signed) can only be tested on specific IBM hardware
* Try to reboot a PV guest multiple times.
* Or using hades (bb/mhartmay/pv branch):
$ for i in $(seq 1 100); do nose2 -v --early-debug tests.test_pv.PVChreiplTestCase; done
[Regression Potential]
* regressions in the initial program loader for Z (zipl) could break the creation of new boot devices for s390x
* the package is only available on s390x and thus could only affect IBM Z machines
* Existing boot devices / IPL would not be affected
[Other Info]
* Needs to be tested/verified by IBM internally
* In addition to the patches/cherry-picks provided via the original description, I included fd81728 ("zipl: fix incorrect setup of stage3 flags") from upstream, to fix an issue introduced in commit 6c04f97 ("zipl: consolidate stage3_params structs and stage3 flags")
=== Original Description ===
Problem description:
Sometimes a PV guest fails to reboot from a disk.
# How to reproduce?
Try to reboot a PV guest multiple times.
Or using hades (bb/mhartmay/pv branch):
$ for i in $(seq 1 100); do nose2 -v --early-debug tests.test_pv.PVChreiplTestCase; done
# Host kernel used:
5.6.0-rc2-00041-g0c1beb8db4fc
# Host cmdline used:
kvm.nested=1 nokaslr crashkernel=196M selinux=0 root=/dev/disk/by-path/ccw-0.0.1000-part1 rd.dasd=0.0.1000 cio_ignore=all,!condev LANG=en_US.UTF-8 prot_virt=1
# QEMU used:
QEMU emulator version 4.2.50 (v4.2.0-1246-g3d17206cbf41-dirty)
# Guest kernel used:
5.6.0-rc2-00041-g0c1beb8db4fc
# Guest cmdline used:
enforcing=0 console=ttyS0 swiotlb=256000 STARTUP=sshd.sh PV
This is a list of commits that are required to entirely resolve this bug
on top of s390tools-2.12
These commits are zipl related only.
c91d8bd5f9102cb91ba6839cf98c40dd26521cd3
fb62cc9e14591c7f84944148d48ac98114a26d46
f4f2220693ffe2efadfd41e0036f6971aabc1fdd
e0ffb3c584f57783538773b3edabbbb5f48caefc
e67f6300862d939d212d79c4ce5e1249102ddcd3
c4a0933165c7093c2ca52c9ee94e4b074fc9f3f7
cb11d6baec41f14c3e8f6832a13ea0020dcf907d
6c04f977734f55b862b9900abfc325e1db98acd0
ce65c39e18a62743bf65eeec92eaedbe22d035da
19f747847ffb39cb2df43376ff569bf18a026362
eb4e806cdc0801718e3d74b2062700d57f6f4b5a
93a0cb254efe45b5e291283af69d74f531cdc40d
2fe5f27975785a3af91d0b24f88962c7ae82ed44
cc069af26d1c35e35bca9d7db4ee4d8a0f8f5440
0843b7db36af3e30c97fd8be8173debe9f5510b7
1a150b2fe05627adc43cc00dd2291acfff30735a
9a68a25ab609146e0c22ae882a2f80c6da714761
4eea67cd6f100e7db7b71a03495e97a8db96490a
0ac7ce964ed089a2614dbfcffb89bd6c4175992b
0c583ec1a68e998f5ed775a97d7f046aad5df28a
1b65b23b43985cb8a1da2ef399ec6def31bbcc69
454f1427d3edcd94c2e25fe7165d392bcc97567a
71b36d17f019c9e2cf218351520d5b55a6c2d479
41fae58ecd8d0099ce2802f43e6b998eecc818c7
3217e0438fd8ba602706eda8adbb23e74f2f54ad
ae66f795124fb3b5e57637ff002edbf45f05ccbd
d7b816ff58baed404b5406a7c25e390804ff1a76
c367a6bb6529f04bdcb6264ede99439a756dfa3e
943c5dc51d493fd89f8c1b0760656446d5653be6 |
[Impact]
* Sometimes a PV guest fails to reboot from a disk.
* Backporting newer zipl functionality to focal fixes the reboot of protected VMs on IBM Z by checking for the secure IPL feature before looking up data
* This bug was fixed in s390-tools 2.14.0 (which depends on a newer kernel), therefore we cherry-pick just the fixes to zipl, while keeping s390-tools at 2.12.0
[Test Case]
* Secure boot (s390-tools-signed) can only be tested on specific IBM hardware
* Try to reboot a PV guest multiple times.
* Or using hades (bb/mhartmay/pv branch):
$ for i in $(seq 1 100); do nose2 -v --early-debug tests.test_pv.PVChreiplTestCase; done
[Regression Potential]
* regressions in the initial program loader for Z (zipl) could break the creation of new boot devices for s390x
* the package is only available on s390x and thus could only affect IBM Z machines
* Existing boot devices / IPL would not be affected
[Other Info]
* Needs to be tested/verified by IBM internally
* In addition to the patches/cherry-picks provided via the original description, I included fd81728 ("zipl: fix incorrect setup of stage3 flags") from upstream, to fix an issue introduced in commit 6c04f97 ("zipl: consolidate stage3_params structs and stage3 flags")
=== Original Description ===
Problem description:
Sometimes a PV guest fails to reboot from a disk.
# How to reproduce?
Try to reboot a PV guest multiple times.
Or using hades (bb/mhartmay/pv branch):
$ for i in $(seq 1 100); do nose2 -v --early-debug tests.test_pv.PVChreiplTestCase; done
# Host kernel used:
5.6.0-rc2-00041-g0c1beb8db4fc
# Host cmdline used:
kvm.nested=1 nokaslr crashkernel=196M selinux=0 root=/dev/disk/by-path/ccw-0.0.1000-part1 rd.dasd=0.0.1000 cio_ignore=all,!condev LANG=en_US.UTF-8 prot_virt=1
# QEMU used:
QEMU emulator version 4.2.50 (v4.2.0-1246-g3d17206cbf41-dirty)
# Guest kernel used:
5.6.0-rc2-00041-g0c1beb8db4fc
# Guest cmdline used:
enforcing=0 console=ttyS0 swiotlb=256000 STARTUP=sshd.sh PV
This is a list of commits that are required to entirely resolve this bug
on top of s390tools-2.12
These commits are zipl related only.
c91d8bd5f9102cb91ba6839cf98c40dd26521cd3
fb62cc9e14591c7f84944148d48ac98114a26d46
f4f2220693ffe2efadfd41e0036f6971aabc1fdd
e0ffb3c584f57783538773b3edabbbb5f48caefc
e67f6300862d939d212d79c4ce5e1249102ddcd3
c4a0933165c7093c2ca52c9ee94e4b074fc9f3f7
cb11d6baec41f14c3e8f6832a13ea0020dcf907d
6c04f977734f55b862b9900abfc325e1db98acd0
ce65c39e18a62743bf65eeec92eaedbe22d035da
19f747847ffb39cb2df43376ff569bf18a026362
eb4e806cdc0801718e3d74b2062700d57f6f4b5a
93a0cb254efe45b5e291283af69d74f531cdc40d
2fe5f27975785a3af91d0b24f88962c7ae82ed44
cc069af26d1c35e35bca9d7db4ee4d8a0f8f5440
0843b7db36af3e30c97fd8be8173debe9f5510b7
1a150b2fe05627adc43cc00dd2291acfff30735a
9a68a25ab609146e0c22ae882a2f80c6da714761
4eea67cd6f100e7db7b71a03495e97a8db96490a
0ac7ce964ed089a2614dbfcffb89bd6c4175992b
0c583ec1a68e998f5ed775a97d7f046aad5df28a
1b65b23b43985cb8a1da2ef399ec6def31bbcc69
454f1427d3edcd94c2e25fe7165d392bcc97567a
71b36d17f019c9e2cf218351520d5b55a6c2d479
41fae58ecd8d0099ce2802f43e6b998eecc818c7
3217e0438fd8ba602706eda8adbb23e74f2f54ad
ae66f795124fb3b5e57637ff002edbf45f05ccbd
d7b816ff58baed404b5406a7c25e390804ff1a76
c367a6bb6529f04bdcb6264ede99439a756dfa3e
943c5dc51d493fd89f8c1b0760656446d5653be6 |
|
| 2020-10-01 13:03:15 |
Lukas Märdian |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-10-01 13:04:01 |
Lukas Märdian |
description |
[Impact]
* Sometimes a PV guest fails to reboot from a disk.
* Backporting newer zipl functionality to focal fixes the reboot of protected VMs on IBM Z by checking for the secure IPL feature before looking up data
* This bug was fixed in s390-tools 2.14.0 (which depends on a newer kernel), therefore we cherry-pick just the fixes to zipl, while keeping s390-tools at 2.12.0
[Test Case]
* Secure boot (s390-tools-signed) can only be tested on specific IBM hardware
* Try to reboot a PV guest multiple times.
* Or using hades (bb/mhartmay/pv branch):
$ for i in $(seq 1 100); do nose2 -v --early-debug tests.test_pv.PVChreiplTestCase; done
[Regression Potential]
* regressions in the initial program loader for Z (zipl) could break the creation of new boot devices for s390x
* the package is only available on s390x and thus could only affect IBM Z machines
* Existing boot devices / IPL would not be affected
[Other Info]
* Needs to be tested/verified by IBM internally
* In addition to the patches/cherry-picks provided via the original description, I included fd81728 ("zipl: fix incorrect setup of stage3 flags") from upstream, to fix an issue introduced in commit 6c04f97 ("zipl: consolidate stage3_params structs and stage3 flags")
=== Original Description ===
Problem description:
Sometimes a PV guest fails to reboot from a disk.
# How to reproduce?
Try to reboot a PV guest multiple times.
Or using hades (bb/mhartmay/pv branch):
$ for i in $(seq 1 100); do nose2 -v --early-debug tests.test_pv.PVChreiplTestCase; done
# Host kernel used:
5.6.0-rc2-00041-g0c1beb8db4fc
# Host cmdline used:
kvm.nested=1 nokaslr crashkernel=196M selinux=0 root=/dev/disk/by-path/ccw-0.0.1000-part1 rd.dasd=0.0.1000 cio_ignore=all,!condev LANG=en_US.UTF-8 prot_virt=1
# QEMU used:
QEMU emulator version 4.2.50 (v4.2.0-1246-g3d17206cbf41-dirty)
# Guest kernel used:
5.6.0-rc2-00041-g0c1beb8db4fc
# Guest cmdline used:
enforcing=0 console=ttyS0 swiotlb=256000 STARTUP=sshd.sh PV
This is a list of commits that are required to entirely resolve this bug
on top of s390tools-2.12
These commits are zipl related only.
c91d8bd5f9102cb91ba6839cf98c40dd26521cd3
fb62cc9e14591c7f84944148d48ac98114a26d46
f4f2220693ffe2efadfd41e0036f6971aabc1fdd
e0ffb3c584f57783538773b3edabbbb5f48caefc
e67f6300862d939d212d79c4ce5e1249102ddcd3
c4a0933165c7093c2ca52c9ee94e4b074fc9f3f7
cb11d6baec41f14c3e8f6832a13ea0020dcf907d
6c04f977734f55b862b9900abfc325e1db98acd0
ce65c39e18a62743bf65eeec92eaedbe22d035da
19f747847ffb39cb2df43376ff569bf18a026362
eb4e806cdc0801718e3d74b2062700d57f6f4b5a
93a0cb254efe45b5e291283af69d74f531cdc40d
2fe5f27975785a3af91d0b24f88962c7ae82ed44
cc069af26d1c35e35bca9d7db4ee4d8a0f8f5440
0843b7db36af3e30c97fd8be8173debe9f5510b7
1a150b2fe05627adc43cc00dd2291acfff30735a
9a68a25ab609146e0c22ae882a2f80c6da714761
4eea67cd6f100e7db7b71a03495e97a8db96490a
0ac7ce964ed089a2614dbfcffb89bd6c4175992b
0c583ec1a68e998f5ed775a97d7f046aad5df28a
1b65b23b43985cb8a1da2ef399ec6def31bbcc69
454f1427d3edcd94c2e25fe7165d392bcc97567a
71b36d17f019c9e2cf218351520d5b55a6c2d479
41fae58ecd8d0099ce2802f43e6b998eecc818c7
3217e0438fd8ba602706eda8adbb23e74f2f54ad
ae66f795124fb3b5e57637ff002edbf45f05ccbd
d7b816ff58baed404b5406a7c25e390804ff1a76
c367a6bb6529f04bdcb6264ede99439a756dfa3e
943c5dc51d493fd89f8c1b0760656446d5653be6 |
[Impact]
* Sometimes a PV guest fails to reboot from a disk.
* Backporting newer zipl functionality to focal fixes the reboot of protected VMs on IBM Z by checking for the secure IPL feature before looking up data
* This bug was fixed in s390-tools 2.14.0 (which depends on a newer kernel), therefore we cherry-pick just the fixes to zipl, while keeping s390-tools at 2.12.0
[Test Case]
* Secure boot (s390-tools-signed) can only be tested on specific IBM hardware
* Try to reboot a PV guest multiple times.
* Or using hades (bb/mhartmay/pv branch):
$ for i in $(seq 1 100); do nose2 -v --early-debug tests.test_pv.PVChreiplTestCase; done
[Regression Potential]
* regressions in the initial program loader for Z (zipl) could break the creation of new boot devices for s390x
* the package is only available on s390x and thus could only affect IBM Z machines
* Existing boot devices / IPL would not be affected
[Other Info]
* Needs to be tested/verified by IBM internally
* In addition to the patches/cherry-picks provided via the original description, I included fd81728 ("zipl: fix incorrect setup of stage3 flags") from upstream, to fix an issue introduced in commit 6c04f97 ("zipl: consolidate stage3_params structs and stage3 flags")
* Also includes fixes for LP: #1888231 and LP: #1893027
=== Original Description ===
Problem description:
Sometimes a PV guest fails to reboot from a disk.
# How to reproduce?
Try to reboot a PV guest multiple times.
Or using hades (bb/mhartmay/pv branch):
$ for i in $(seq 1 100); do nose2 -v --early-debug tests.test_pv.PVChreiplTestCase; done
# Host kernel used:
5.6.0-rc2-00041-g0c1beb8db4fc
# Host cmdline used:
kvm.nested=1 nokaslr crashkernel=196M selinux=0 root=/dev/disk/by-path/ccw-0.0.1000-part1 rd.dasd=0.0.1000 cio_ignore=all,!condev LANG=en_US.UTF-8 prot_virt=1
# QEMU used:
QEMU emulator version 4.2.50 (v4.2.0-1246-g3d17206cbf41-dirty)
# Guest kernel used:
5.6.0-rc2-00041-g0c1beb8db4fc
# Guest cmdline used:
enforcing=0 console=ttyS0 swiotlb=256000 STARTUP=sshd.sh PV
This is a list of commits that are required to entirely resolve this bug
on top of s390tools-2.12
These commits are zipl related only.
c91d8bd5f9102cb91ba6839cf98c40dd26521cd3
fb62cc9e14591c7f84944148d48ac98114a26d46
f4f2220693ffe2efadfd41e0036f6971aabc1fdd
e0ffb3c584f57783538773b3edabbbb5f48caefc
e67f6300862d939d212d79c4ce5e1249102ddcd3
c4a0933165c7093c2ca52c9ee94e4b074fc9f3f7
cb11d6baec41f14c3e8f6832a13ea0020dcf907d
6c04f977734f55b862b9900abfc325e1db98acd0
ce65c39e18a62743bf65eeec92eaedbe22d035da
19f747847ffb39cb2df43376ff569bf18a026362
eb4e806cdc0801718e3d74b2062700d57f6f4b5a
93a0cb254efe45b5e291283af69d74f531cdc40d
2fe5f27975785a3af91d0b24f88962c7ae82ed44
cc069af26d1c35e35bca9d7db4ee4d8a0f8f5440
0843b7db36af3e30c97fd8be8173debe9f5510b7
1a150b2fe05627adc43cc00dd2291acfff30735a
9a68a25ab609146e0c22ae882a2f80c6da714761
4eea67cd6f100e7db7b71a03495e97a8db96490a
0ac7ce964ed089a2614dbfcffb89bd6c4175992b
0c583ec1a68e998f5ed775a97d7f046aad5df28a
1b65b23b43985cb8a1da2ef399ec6def31bbcc69
454f1427d3edcd94c2e25fe7165d392bcc97567a
71b36d17f019c9e2cf218351520d5b55a6c2d479
41fae58ecd8d0099ce2802f43e6b998eecc818c7
3217e0438fd8ba602706eda8adbb23e74f2f54ad
ae66f795124fb3b5e57637ff002edbf45f05ccbd
d7b816ff58baed404b5406a7c25e390804ff1a76
c367a6bb6529f04bdcb6264ede99439a756dfa3e
943c5dc51d493fd89f8c1b0760656446d5653be6 |
|
| 2020-10-01 13:17:52 |
Lukas Märdian |
description |
[Impact]
* Sometimes a PV guest fails to reboot from a disk.
* Backporting newer zipl functionality to focal fixes the reboot of protected VMs on IBM Z by checking for the secure IPL feature before looking up data
* This bug was fixed in s390-tools 2.14.0 (which depends on a newer kernel), therefore we cherry-pick just the fixes to zipl, while keeping s390-tools at 2.12.0
[Test Case]
* Secure boot (s390-tools-signed) can only be tested on specific IBM hardware
* Try to reboot a PV guest multiple times.
* Or using hades (bb/mhartmay/pv branch):
$ for i in $(seq 1 100); do nose2 -v --early-debug tests.test_pv.PVChreiplTestCase; done
[Regression Potential]
* regressions in the initial program loader for Z (zipl) could break the creation of new boot devices for s390x
* the package is only available on s390x and thus could only affect IBM Z machines
* Existing boot devices / IPL would not be affected
[Other Info]
* Needs to be tested/verified by IBM internally
* In addition to the patches/cherry-picks provided via the original description, I included fd81728 ("zipl: fix incorrect setup of stage3 flags") from upstream, to fix an issue introduced in commit 6c04f97 ("zipl: consolidate stage3_params structs and stage3 flags")
* Also includes fixes for LP: #1888231 and LP: #1893027
=== Original Description ===
Problem description:
Sometimes a PV guest fails to reboot from a disk.
# How to reproduce?
Try to reboot a PV guest multiple times.
Or using hades (bb/mhartmay/pv branch):
$ for i in $(seq 1 100); do nose2 -v --early-debug tests.test_pv.PVChreiplTestCase; done
# Host kernel used:
5.6.0-rc2-00041-g0c1beb8db4fc
# Host cmdline used:
kvm.nested=1 nokaslr crashkernel=196M selinux=0 root=/dev/disk/by-path/ccw-0.0.1000-part1 rd.dasd=0.0.1000 cio_ignore=all,!condev LANG=en_US.UTF-8 prot_virt=1
# QEMU used:
QEMU emulator version 4.2.50 (v4.2.0-1246-g3d17206cbf41-dirty)
# Guest kernel used:
5.6.0-rc2-00041-g0c1beb8db4fc
# Guest cmdline used:
enforcing=0 console=ttyS0 swiotlb=256000 STARTUP=sshd.sh PV
This is a list of commits that are required to entirely resolve this bug
on top of s390tools-2.12
These commits are zipl related only.
c91d8bd5f9102cb91ba6839cf98c40dd26521cd3
fb62cc9e14591c7f84944148d48ac98114a26d46
f4f2220693ffe2efadfd41e0036f6971aabc1fdd
e0ffb3c584f57783538773b3edabbbb5f48caefc
e67f6300862d939d212d79c4ce5e1249102ddcd3
c4a0933165c7093c2ca52c9ee94e4b074fc9f3f7
cb11d6baec41f14c3e8f6832a13ea0020dcf907d
6c04f977734f55b862b9900abfc325e1db98acd0
ce65c39e18a62743bf65eeec92eaedbe22d035da
19f747847ffb39cb2df43376ff569bf18a026362
eb4e806cdc0801718e3d74b2062700d57f6f4b5a
93a0cb254efe45b5e291283af69d74f531cdc40d
2fe5f27975785a3af91d0b24f88962c7ae82ed44
cc069af26d1c35e35bca9d7db4ee4d8a0f8f5440
0843b7db36af3e30c97fd8be8173debe9f5510b7
1a150b2fe05627adc43cc00dd2291acfff30735a
9a68a25ab609146e0c22ae882a2f80c6da714761
4eea67cd6f100e7db7b71a03495e97a8db96490a
0ac7ce964ed089a2614dbfcffb89bd6c4175992b
0c583ec1a68e998f5ed775a97d7f046aad5df28a
1b65b23b43985cb8a1da2ef399ec6def31bbcc69
454f1427d3edcd94c2e25fe7165d392bcc97567a
71b36d17f019c9e2cf218351520d5b55a6c2d479
41fae58ecd8d0099ce2802f43e6b998eecc818c7
3217e0438fd8ba602706eda8adbb23e74f2f54ad
ae66f795124fb3b5e57637ff002edbf45f05ccbd
d7b816ff58baed404b5406a7c25e390804ff1a76
c367a6bb6529f04bdcb6264ede99439a756dfa3e
943c5dc51d493fd89f8c1b0760656446d5653be6 |
[Impact]
* Sometimes a PV guest fails to reboot from a disk.
* Backporting newer zipl functionality to focal fixes the reboot of protected VMs on IBM Z by checking for the secure IPL feature before looking up data
* This bug was fixed in s390-tools 2.14.0 (which depends on a newer kernel), therefore we cherry-pick just the fixes to zipl, while keeping s390-tools at 2.12.0
[Test Case]
* Secure boot (s390-tools-signed) can only be tested on specific IBM hardware
* Try to reboot a PV guest multiple times.
* Or using hades (bb/mhartmay/pv branch):
$ for i in $(seq 1 100); do nose2 -v --early-debug tests.test_pv.PVChreiplTestCase; done
[Regression Potential]
* regressions in the initial program loader for Z (zipl) could break the creation of new boot devices for s390x
* the package is only available on s390x and thus could only affect IBM Z machines
* Existing boot devices / IPL would not be affected
[Other Info]
* Needs to be tested/verified by IBM internally
* In addition to the patches/cherry-picks provided via the original description, I included fd81728 ("zipl: fix incorrect setup of stage3 flags") from upstream, to fix an issue introduced in commit 6c04f97 ("zipl: consolidate stage3_params structs and stage3 flags")
* Related to LP: #1888231 and LP: #1893027
=== Original Description ===
Problem description:
Sometimes a PV guest fails to reboot from a disk.
# How to reproduce?
Try to reboot a PV guest multiple times.
Or using hades (bb/mhartmay/pv branch):
$ for i in $(seq 1 100); do nose2 -v --early-debug tests.test_pv.PVChreiplTestCase; done
# Host kernel used:
5.6.0-rc2-00041-g0c1beb8db4fc
# Host cmdline used:
kvm.nested=1 nokaslr crashkernel=196M selinux=0 root=/dev/disk/by-path/ccw-0.0.1000-part1 rd.dasd=0.0.1000 cio_ignore=all,!condev LANG=en_US.UTF-8 prot_virt=1
# QEMU used:
QEMU emulator version 4.2.50 (v4.2.0-1246-g3d17206cbf41-dirty)
# Guest kernel used:
5.6.0-rc2-00041-g0c1beb8db4fc
# Guest cmdline used:
enforcing=0 console=ttyS0 swiotlb=256000 STARTUP=sshd.sh PV
This is a list of commits that are required to entirely resolve this bug
on top of s390tools-2.12
These commits are zipl related only.
c91d8bd5f9102cb91ba6839cf98c40dd26521cd3
fb62cc9e14591c7f84944148d48ac98114a26d46
f4f2220693ffe2efadfd41e0036f6971aabc1fdd
e0ffb3c584f57783538773b3edabbbb5f48caefc
e67f6300862d939d212d79c4ce5e1249102ddcd3
c4a0933165c7093c2ca52c9ee94e4b074fc9f3f7
cb11d6baec41f14c3e8f6832a13ea0020dcf907d
6c04f977734f55b862b9900abfc325e1db98acd0
ce65c39e18a62743bf65eeec92eaedbe22d035da
19f747847ffb39cb2df43376ff569bf18a026362
eb4e806cdc0801718e3d74b2062700d57f6f4b5a
93a0cb254efe45b5e291283af69d74f531cdc40d
2fe5f27975785a3af91d0b24f88962c7ae82ed44
cc069af26d1c35e35bca9d7db4ee4d8a0f8f5440
0843b7db36af3e30c97fd8be8173debe9f5510b7
1a150b2fe05627adc43cc00dd2291acfff30735a
9a68a25ab609146e0c22ae882a2f80c6da714761
4eea67cd6f100e7db7b71a03495e97a8db96490a
0ac7ce964ed089a2614dbfcffb89bd6c4175992b
0c583ec1a68e998f5ed775a97d7f046aad5df28a
1b65b23b43985cb8a1da2ef399ec6def31bbcc69
454f1427d3edcd94c2e25fe7165d392bcc97567a
71b36d17f019c9e2cf218351520d5b55a6c2d479
41fae58ecd8d0099ce2802f43e6b998eecc818c7
3217e0438fd8ba602706eda8adbb23e74f2f54ad
ae66f795124fb3b5e57637ff002edbf45f05ccbd
d7b816ff58baed404b5406a7c25e390804ff1a76
c367a6bb6529f04bdcb6264ede99439a756dfa3e
943c5dc51d493fd89f8c1b0760656446d5653be6 |
|
| 2020-10-01 13:44:11 |
Frank Heimes |
s390-tools (Ubuntu Focal): status |
New |
In Progress |
|
| 2020-10-12 13:35:02 |
Łukasz Zemczak |
s390-tools (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2020-10-12 13:35:04 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2020-10-12 13:35:07 |
Łukasz Zemczak |
tags |
architecture-s39064 bugnameltc-187747 id-5f3e969561488979e4dce5fc severity-high targetmilestone-inin2004 |
architecture-s39064 bugnameltc-187747 id-5f3e969561488979e4dce5fc severity-high targetmilestone-inin2004 verification-needed verification-needed-focal |
|
| 2020-10-12 13:42:11 |
Andrew Cloke |
ubuntu-z-systems: status |
In Progress |
Fix Committed |
|
| 2020-10-14 15:46:29 |
Matthieu Clemenceau |
tags |
architecture-s39064 bugnameltc-187747 id-5f3e969561488979e4dce5fc severity-high targetmilestone-inin2004 verification-needed verification-needed-focal |
architecture-s39064 bugnameltc-187747 fr-587 id-5f3e969561488979e4dce5fc severity-high targetmilestone-inin2004 verification-needed verification-needed-focal |
|
| 2020-10-23 07:59:01 |
Frank Heimes |
tags |
architecture-s39064 bugnameltc-187747 fr-587 id-5f3e969561488979e4dce5fc severity-high targetmilestone-inin2004 verification-needed verification-needed-focal |
architecture-s39064 bugnameltc-187747 fr-587 id-5f3e969561488979e4dce5fc severity-high targetmilestone-inin2004 verification-done verification-done-focal |
|
| 2020-10-26 09:59:40 |
Launchpad Janitor |
s390-tools (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2020-10-26 09:59:51 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2020-10-26 10:14:35 |
Frank Heimes |
ubuntu-z-systems: status |
Fix Committed |
Fix Released |
|
