Skip to content

Commit 63bdd54

Browse files
Merge pull request #81906 from krishnanshruthi/OCPBUGS-41987
[MULTIARCH-3807] ABI documentation updates for 4.17
2 parents 2710390 + da6c7b1 commit 63bdd54

File tree

1 file changed

+8
-43
lines changed

1 file changed

+8
-43
lines changed

modules/adding-ibmz-lpar-agent.adoc

Lines changed: 8 additions & 43 deletions
Original file line numberDiff line numberDiff line change
@@ -34,56 +34,21 @@ random.trust_cpu=on rd.luks.options=discard
3434
<2> For the `ip` parameter, manually assign the IP address, as described in _Installing a cluster with z/VM on IBM Z and IBM LinuxONE_.
3535
<3> For installations on DASD-type disks, use `rd.dasd` to specify the DASD where {op-system-first} is to be installed. For installations on FCP-type disks, use `rd.zfcp=<adapter>,<wwpn>,<lun>` to specify the FCP disk where {op-system} is to be installed.
3636
<4> Specify this parameter when you use an Open Systems Adapter (OSA) or HiperSockets.
37-
38-
. Generate the `.ins` and `initrd.img.addrsize` files by running the following Python script:
39-
+
40-
The `.ins` file is a special file that includes installation data and is present on the FTP server. It can be accessed from the HMC system.
41-
This file contains details such as mapping of the location of installation data on the disk or FTP server, the memory locations where the data is to be copied.
4237
+
4338
[NOTE]
4439
====
45-
The `.ins` and `initrd.img.addrsize` files are not automatically generated as part of boot-artifacts from the installer. You must manually generate these files.
40+
The `.ins` and `initrd.img.addrsize` files are automatically generated for `s390x` architecture as part of boot-artifacts from the installation program and are only used when booting in an LPAR environment.
4641
====
47-
48-
.. Save the following script to a file, such as `generate-files.py`:
49-
+
50-
.Example of a Python file named `generate-files.py` file
51-
[source,python]
52-
----
53-
# The following commands retrieve the size of the `kernel` and `initrd`:
54-
KERNEL_IMG_PATH='./kernel.img'
55-
INITRD_IMG_PATH='./initrd.img'
56-
CMDLINE_PATH='./generic.prm'
57-
kernel_size=(stat -c%s KERNEL_IMG_PATH)
58-
initrd_size=(stat -c%s INITRD_IMG_PATH)
59-
# The following command rounds the `kernel` size up to the next megabytes (MB) boundary.
60-
# This value is the starting address of `initrd.img`.
61-
offset=(( (kernel_size + 1048575) / 1048576 * 1048576 ))
62-
INITRD_IMG_NAME=(echo INITRD_IMG_PATH | rev | cut -d '/' -f 1 | rev)
63-
# The following commands create the kernel binary patch file that contains the `initrd` address and size:
64-
KERNEL_OFFSET=0x00000000
65-
KERNEL_CMDLINE_OFFSET=0x00010480
66-
INITRD_ADDR_SIZE_OFFSET=0x00010408
67-
OFFSET_HEX=(printf '0x%08x\n' offset)
68-
# The following command converts the address and size to binary format:
69-
printf "(printf '%016x\n' $initrd_size)" | xxd -r -p > temp_size.bin
70-
# The following command concatenates the address and size binaries:
71-
cat temp_address.bin temp_size.bin > "$INITRD_IMG_NAME.addrsize"
72-
# The following command deletes temporary files:
73-
rm -rf temp_address.bin temp_size.bin
74-
# The following commands create the `.ins` file.
75-
# The file is based on the paths of the `kernel.img`, `initrd.img`, `initrd.img.addrsize`, and `cmdline` files and the memory locations where the data is to be copied.
76-
KERNEL_IMG_PATH KERNEL_OFFSET
77-
INITRD_IMG_PATH OFFSET_HEX
78-
INITRD_IMG_NAME.addrsize INITRD_ADDR_SIZE_OFFSET
79-
CMDLINE_PATH KERNEL_CMDLINE_OFFSET
80-
----
81-
82-
.. Execute the script by running the following command:
8342
+
43+
.Example filesystem with LPAR boot
8444
[source,terminal]
8545
----
86-
$ python3 <file_name>.py
46+
boot-artifacts
47+
├─ agent.s390x-generic.ins
48+
├─ agent.s390x-initrd.addrsize
49+
├─ agent.s390x-rootfs.img
50+
└─ agent.s390x-kernel.img
51+
└─ agent.s390x-rootfs.img
8752
----
8853

8954
. Transfer the `initrd`, `kernel`, `generic.ins`, and `initrd.img.addrsize` parameter files to the file server. For more information, see link:https://www.ibm.com/docs/en/linux-on-systems?topic=bl-booting-linux-in-lpar-mode[Booting Linux in LPAR mode] (IBM documentation).

0 commit comments

Comments
 (0)