From 1d6c373a8685d5e0f1f8292d6fc8f795d291202e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Vin=C3=ADcius=20Ferr=C3=A3o?= <2031761+viniciusferrao@users.noreply.github.com> Date: Sun, 6 Sep 2026 04:03:35 -0300 Subject: [PATCH] docs(genesis): clarify virtual s390x discovery --- .../developers/guides/code/genesis_openembedded_plan.rst | 6 +++--- docs/source/guides/admin-guides/references/man8/mknb.8.rst | 2 ++ xCAT-client/pods/man8/mknb.8.pod | 2 ++ 3 files changed, 7 insertions(+), 3 deletions(-) diff --git a/docs/source/developers/guides/code/genesis_openembedded_plan.rst b/docs/source/developers/guides/code/genesis_openembedded_plan.rst index 5b89a4e6a..ec8bf6e7c 100644 --- a/docs/source/developers/guides/code/genesis_openembedded_plan.rst +++ b/docs/source/developers/guides/code/genesis_openembedded_plan.rst @@ -105,9 +105,9 @@ The ``s390x`` image uses virtio networking under QEMU. QEMU does not emulate qeth, so the activation service exits without changing the virtio interface. Physical LPAR and z/VM Genesis networking remain unvalidated. Genesis does not use the shared CEC serial as an s390x node identifier. -QEMU guests report themselves as virtual nodes, so sequential and switch -discovery ignore them. Use profile discovery or assign a pending discovery -record with ``nodediscoverdef``. +s390x hypervisor guests report themselves as virtual nodes, so sequential and +switch discovery ignore them. Use profile discovery or assign a pending +discovery record with ``nodediscoverdef``. QEMU validation covers network IPL, DHCP option 209, TFTP, and the network-specific ``pxelinux.cfg``-style configuration written by ``mknb``. This release does not advertise a DPM boot configuration. diff --git a/docs/source/guides/admin-guides/references/man8/mknb.8.rst b/docs/source/guides/admin-guides/references/man8/mknb.8.rst index 8a925e657..638a8894f 100644 --- a/docs/source/guides/admin-guides/references/man8/mknb.8.rst +++ b/docs/source/guides/admin-guides/references/man8/mknb.8.rst @@ -50,6 +50,8 @@ riscv64 nodes boot through UEFI firmware and grub2. For riscv64, \ **mknb**\ pu QEMU s390-ccw guests receive a network-specific \ ``pxelinux.cfg``\ -style configuration through DHCP option 209. The firmware resolves this name below \ ``pxelinux.cfg``\ . Leave \ ``noderes.netboot``\ unset while a QEMU s390x node uses Genesis discovery. s390x Genesis does not use the shared IBM Z machine serial as a node identifier. On physical IBM Z, Genesis accepts \ ``rd.znet=qeth,read,write,data[,option=value]``\ and activates qeth before NetworkManager starts. Without \ ``rd.znet``\ , it activates unconfigured qeth devices in layer 2 mode. Devices reported as configured by \ ``znetconf``\ are not regrouped. Genesis does not import DPM auto-configuration data. Layer 3 and IP-mode VSWITCH configurations require \ ``layer2=0``\ . QEMU validation covers network IPL through Genesis startup; the discovery exchange with xcatd remains unvalidated for s390x. Legacy xCAT z/VM operating-system provisioning remains unchanged. Physical LPAR and z/VM Genesis networking remain unvalidated because QEMU does not emulate qeth. +s390x hypervisor guests report themselves as virtual nodes, so sequential and switch discovery ignore them. Use profile discovery or assign a pending discovery record with \ **nodediscoverdef**\ . + Run \ **makedhcp -n**\ after installing the s390x image and before booting s390x nodes. This regenerates the DHCP configuration with the required option. diff --git a/xCAT-client/pods/man8/mknb.8.pod b/xCAT-client/pods/man8/mknb.8.pod index 6ea2b7077..e5cdf0f32 100644 --- a/xCAT-client/pods/man8/mknb.8.pod +++ b/xCAT-client/pods/man8/mknb.8.pod @@ -32,6 +32,8 @@ riscv64 nodes boot through UEFI firmware and grub2. For riscv64, B publish QEMU s390-ccw guests receive a network-specific C-style configuration through DHCP option 209. The firmware resolves this name below C. Leave C unset while a QEMU s390x node uses Genesis discovery. s390x Genesis does not use the shared IBM Z machine serial as a node identifier. On physical IBM Z, Genesis accepts C and activates qeth before NetworkManager starts. Without C, it activates unconfigured qeth devices in layer 2 mode. Devices reported as configured by C are not regrouped. Genesis does not import DPM auto-configuration data. Layer 3 and IP-mode VSWITCH configurations require C. QEMU validation covers network IPL through Genesis startup; the discovery exchange with xcatd remains unvalidated for s390x. Legacy xCAT z/VM operating-system provisioning remains unchanged. Physical LPAR and z/VM Genesis networking remain unvalidated because QEMU does not emulate qeth. +s390x hypervisor guests report themselves as virtual nodes, so sequential and switch discovery ignore them. Use profile discovery or assign a pending discovery record with B. + Run B after installing the s390x image and before booting s390x nodes. This regenerates the DHCP configuration with the required option. =head1 OPTIONS