[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH 06/18] docs/system/s390x/bootdevices: Update the documentation ab
From: |
jrossi |
Subject: |
[PATCH 06/18] docs/system/s390x/bootdevices: Update the documentation about network booting |
Date: |
Thu, 26 Sep 2024 20:51:05 -0400 |
From: Jared Rossi <jrossi@linux.ibm.com>
Remove the information about the separate s390-netboot.img from
the documentation.
Co-authored by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Jared Rossi <jrossi@linux.ibm.com>
---
docs/system/s390x/bootdevices.rst | 20 +++++++-------------
1 file changed, 7 insertions(+), 13 deletions(-)
diff --git a/docs/system/s390x/bootdevices.rst
b/docs/system/s390x/bootdevices.rst
index 1a7a18b43b..c97efb8fc0 100644
--- a/docs/system/s390x/bootdevices.rst
+++ b/docs/system/s390x/bootdevices.rst
@@ -82,23 +82,17 @@ Note that ``0`` can be used to boot the default entry.
Booting from a network device
-----------------------------
-Beside the normal guest firmware (which is loaded from the file
``s390-ccw.img``
-in the data directory of QEMU, or via the ``-bios`` option), QEMU ships with
-a small TFTP network bootloader firmware for virtio-net-ccw devices, too. This
-firmware is loaded from a file called ``s390-netboot.img`` in the QEMU data
-directory. In case you want to load it from a different filename instead,
-you can specify it via the ``-global s390-ipl.netboot_fw=filename``
-command line option.
-
-The ``bootindex`` property is especially important for booting via the network.
-If you don't specify the ``bootindex`` property here, the network bootloader
-firmware code won't get loaded into the guest memory so that the network boot
-will fail. For a successful network boot, try something like this::
+The firmware that ships with QEMU includes a small TFTP network bootloader
+for virtio-net-ccw devices. The ``bootindex`` property is especially
+important for booting via the network. If you don't specify the ``bootindex``
+property here, the network bootloader won't be taken into consideration and
+the network boot will fail. For a successful network boot, try something
+like this::
qemu-system-s390x -netdev user,id=n1,tftp=...,bootfile=... \
-device virtio-net-ccw,netdev=n1,bootindex=1
-The network bootloader firmware also has basic support for pxelinux.cfg-style
+The network bootloader also has basic support for pxelinux.cfg-style
configuration files. See the `PXELINUX Configuration page
<https://wiki.syslinux.org/wiki/index.php?title=PXELINUX#Configuration>`__
for details how to set up the configuration file on your TFTP server.
--
2.45.1
- [PATCH V2 0/18] s390x: Add Full Boot Order Support, jrossi, 2024/09/26
- [PATCH 01/18] hw/s390x/ipl: Provide more memory to the s390-ccw.img firmware, jrossi, 2024/09/26
- [PATCH 03/18] pc-bios/s390-ccw: Link the netboot code into the main s390-ccw.img binary, jrossi, 2024/09/26
- [PATCH 04/18] hw/s390x: Remove the possibility to load the s390-netboot.img binary, jrossi, 2024/09/26
- [PATCH 02/18] pc-bios/s390-ccw: Use the libc from SLOF and remove sclp prints, jrossi, 2024/09/26
- [PATCH 06/18] docs/system/s390x/bootdevices: Update the documentation about network booting,
jrossi <=
- [PATCH 07/18] pc-bios/s390-ccw: Remove panics from ISO IPL path, jrossi, 2024/09/26
[PATCH 05/18] pc-bios/s390-ccw: Merge netboot.mak into the main Makefile, jrossi, 2024/09/26
[PATCH 08/18] pc-bios/s390-ccw: Remove panics from ECKD IPL path, jrossi, 2024/09/26
[PATCH 09/18] pc-bios/s390-ccw: Remove panics from SCSI IPL path, jrossi, 2024/09/26