You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<1> For installations on DASD-type disks, add `coreos.inst.install_dev=/dev/dasda`. Omit this value for FCP-type disks.
133
-
<2> Specify the location of the `rootfs` artifact for the `kernel` and `initramfs` you are booting. Only HTTP and HTTPS protocols are supported.
134
-
<3> Specify the location of the Ignition config file. Use `master.ign` or `worker.ign`. Only HTTP and HTTPS protocols are supported.
135
-
<4> For installations on FCP-type disks, add `zfcp.allow_lun_scan=0`. Omit this value for DASD-type disks.
136
-
<5> For installations on DASD-type disks, replace with `rd.dasd=0.0.3490` to specify the DASD device.
137
-
138
-
132
+
<1> Specify the block device type. For installations on DASD-type disks, specify `/dev/dasda`. For installations on FCP-type disks, specify `/dev/sda`.
133
+
<2> Specify the location of the Ignition config file. Use `master.ign` or `worker.ign`. Only HTTP and HTTPS protocols are supported.
134
+
<3> Specify the location of the `rootfs` artifact for the `kernel` and `initramfs` you are booting. Only HTTP and HTTPS protocols are supported.
135
+
<4> For installations on DASD-type disks, replace with `rd.dasd=0.0.xxxx` to specify the DASD device.
<1> For the `--location` parameter, specify the location of the kernel/initrd on the HTTP or HTTPS server.
172
-
<2> For the `coreos.live.rootfs_url=` artifact, specify the matching `rootfs` artifact for the `kernel` and `initramfs` you are booting. Only HTTP and HTTPS protocols are supported.
173
-
<3> For the `ignition.config.url=` parameter, specify the Ignition file for the machine role. Only HTTP and HTTPS protocols are supported.
170
+
<1> For the `--location` parameter, specify the location of the kernel/initrd on the HTTP or HTTPS server.
171
+
<2> Specify the location of the `bootstrap.ign` config file. Only HTTP and HTTPS protocols are supported.
172
+
<3> For the `coreos.live.rootfs_url=` artifact, specify the matching `rootfs` artifact for the `kernel` and `initramfs` you are booting. Only HTTP and HTTPS protocols are supported.
173
+
<4> For the `ip=` parameter, assign the IP address manually as described in "Installing a cluster with with {op-system-base} KVM on {ibm-z-name} and {ibm-linuxone-name}".
<1> For the `coreos.live.rootfs_url=`artifact, specify the matching `rootfs` artifact for the `kernel`and `initramfs` you are booting. Only HTTP and HTTPS protocols are supported.
166
-
<2> For the `ignition.config.url=`parameter, specify the Ignition file for the machine role. Only HTTP and HTTPS protocols are supported.
164
+
<1> For the `ignition.config.url=`parameter, specify the Ignition file for the machine role. Only HTTP and HTTPS protocols are supported.
165
+
<2> For the `coreos.live.rootfs_url=`artifact, specify the matching `rootfs` artifact for the `kernel`and `initramfs` you are booting. Only HTTP and HTTPS protocols are supported.
167
166
<3> For the `ip=` parameter, assign the IP address automatically using DHCP or manually as described in "Installing a cluster with z/VM on {ibm-z-name} and {ibm-linuxone-name}".
168
167
<4> For installations on DASD-type disks, use `rd.dasd=` to specify the DASD where {op-system} is to be installed. Omit this entry for FCP-type disks.
169
168
<5> For installations on FCP-type disks, use `rd.zfcp=<adapter>,<wwpn>,<lun>` to specify the FCP disk where {op-system} is to be installed. Omit this entry for DASD-type disks.
Copy file name to clipboardExpand all lines: modules/installation-full-ibm-z-kvm-user-infra-machines-iso.adoc
+14-10Lines changed: 14 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,22 +40,26 @@ The file names contain the {product-title} version number. They resemble the fol
40
40
The Ignition files are generated by the {product-title} installer.
41
41
====
42
42
. Create the new KVM guest nodes using the {op-system-base} kernel, initramfs, and Ignition files, the new disk image, and adjusted parm line arguments.
43
-
** For `--location`, specify the location of the kernel/initrd on the HTTP or HTTPS server.
44
-
** For `coreos.inst.ignition_url=`, specify the Ignition file for the machine role. Use `bootstrap.ign`, `master.ign`, or `worker.ign`. Only HTTP and HTTPS protocols are supported.
45
-
** For `coreos.live.rootfs_url=`, specify the matching rootfs artifact for the kernel and initramfs you are booting. Only HTTP and HTTPS protocols are supported.
<1> Specify the location of the `rootfs` artifact for the `kernel` and `initramfs` you are booting. Only HTTP and HTTPS protocols are supported.
98
+
<1> Specify the block device type. For installations on DASD-type disks, specify `/dev/dasda`. For installations on FCP-type disks, specify `/dev/sda`.
99
99
<2> Specify the location of the Ignition config file. Use `bootstrap.ign`, `master.ign`, or `worker.ign`. Only HTTP and HTTPS protocols are supported.
100
-
<3> Optional: To enable secure boot, add `coreos.inst.secure_ipl`.
100
+
<3> Specify the location of the `rootfs` artifact for the `kernel` and `initramfs` you are booting. Only HTTP and HTTPS protocols are supported.
101
+
<4> Optional: To enable secure boot, add `coreos.inst.secure_ipl`.
101
102
+
102
103
Write all options in the parameter file as a single line and make sure you have no newline characters.
103
104
@@ -126,18 +127,18 @@ The following is an example parameter file `worker-1.parm` for a compute node wi
0 commit comments