PVIMG(1)
π PVIMG(1) β the pvimg glow-up guide π
okay bestie, so this is straight out of the Pvimg Manual, section PVIMG(1) β yes it's giving official documentation but make it cute β¨
πΈ NAME πΈ
pvimg β create and inspect IBM Secure Execution images π«Ά
β SYNOPSIS β
pvimg [OPTIONS] <COMMAND>
π¦ DESCRIPTION π¦
So like, use pvimg to create an IBM Secure Execution image, which can then be loaded using zipl or QEMU β iconic behaviour honestly. And pvimg can also inspect existing Secure Execution images, because we love a multi-hyphenate π
π PVIMG COMMANDS π
pvimg-create(1)β Create an IBM Secure Execution image. π Create a brand-new IBM Secure Execution image. Only create these images in a trusted environment, such as your workstation β like, do not do this in a sketchy place, iykyk π₯. Thepvimg createcommand creates randomly generated keys to protect the image. The generated image can then be booted on an IBM Secure Execution system as a KVM guest. slay.pvimg-info(1)β Print information about the IBM Secure Execution image. β¨ Theinfosubcommand extracts and displays information about an existing IBM Secure Execution image, including information from the Secure Execution header. By default the header is displayed without verifying its integrity and authenticity. Use--hdr-keyto authenticate and verify the header integrity β that's the whole vibe check right there π΅οΈββοΈ. Output can be formatted as human-readable text or JSON. Use--formatto control the output format and level of detail.
SECURITY NOTE: Without --hdr-key, the displayed information is NOT verified and should not be trusted. fr fr, do not trust it π
pvimg-test(1)β Test different aspects of an existing IBM Secure Execution image. π§
β¨ OPTIONS β¨
-v,--verboseβ Provide more detailed output. spill the tea, give me everything π-q,--quietβ Provide less output. not me asking for silence π--versionβ Print version information and exit.-h,--helpβ Print help (see a summary with-h). the summary is the little sister of the full help, cute π
π EXIT STATUS π
0β Program finished successfully The command was executed successfully. we ate and left no crumbs π1β Generic error Something went wrong during the operation. Refer to the error message. it happens bestie π2β Usage error The command was used incorrectly, for example: unsupported command line flag, or wrong number of arguments. read the synopsis again, love π
π SEE ALSO π
pvimg-create(1), pvimg-info(1), pvimg-test(1), zipl(8), qemu(1)
and that's the whole page, bestie π«Ά brought to you by s390-tools, dated 2026-08-11, filed under PVIMG(1) β periodt π
π¦ where this page comes from
- centos-stream 10: s390utils 2:2.44.1-2.el10 Β· MIT AND LGPL-2.1-or-later
- centos-stream 9: s390utils 2:2.44.1-2.el9 Β· MIT
- opensuse-leap 16.0: s390-tools 2.44.1-160000.1.1 Β· MIT
- opensuse-leap 16.0: s390-tools 2.44.1-160000.1.1 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms