motorhead/qemu
1
0
Fork 0
mirror of https://github.com/Motorhead1991/qemu.git synced 2025-08-31 05:51:53 -06:00
Code Issues Projects Releases Packages Wiki Activity Actions

docs/system/s390x/bootdevices: Update the documentation about network booting

Browse source 
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>
Message-ID: <20241020012953.1380075-7-jrossi@linux.ibm.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
This commit is contained in:
Jared Rossi 2024-10-19 21:29:40 -04:00 • committed by Thomas Huth
parent f1fdadda36
commit ab2691b6c7
1 changed files with 7 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

20
docs/system/s390x/bootdevices.rst
View file

@ -82,23 +82,17 @@ Note that ``0`` can be used to boot the default entry.
Booting from a network device Booting from a network device
----------------------------- -----------------------------
Beside the normal guest firmware (which is loaded from the file ``s390-ccw.img`` The firmware that ships with QEMU includes a small TFTP network bootloader
in the data directory of QEMU, or via the ``-bios`` option), QEMU ships with for virtio-net-ccw devices. The ``bootindex`` property is especially
a small TFTP network bootloader firmware for virtio-net-ccw devices, too. This important for booting via the network. If you don't specify the ``bootindex``
firmware is loaded from a file called ``s390-netboot.img`` in the QEMU data property here, the network bootloader won't be taken into consideration and
directory. In case you want to load it from a different filename instead, the network boot will fail. For a successful network boot, try something
you can specify it via the ``-global s390-ipl.netboot_fw=filename`` like this::
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::
qemu-system-s390x -netdev user,id=n1,tftp=...,bootfile=... \ qemu-system-s390x -netdev user,id=n1,tftp=...,bootfile=... \
-device virtio-net-ccw,netdev=n1,bootindex=1 -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 configuration files. See the `PXELINUX Configuration page
<https://wiki.syslinux.org/wiki/index.php?title=PXELINUX#Configuration>`__ <https://wiki.syslinux.org/wiki/index.php?title=PXELINUX#Configuration>`__
for details how to set up the configuration file on your TFTP server. for details how to set up the configuration file on your TFTP server.