diff options
| author | Thomas Huth <thuth@redhat.com> | 2018-05-22 11:37:29 +0200 |
|---|---|---|
| committer | Thomas Huth <thuth@redhat.com> | 2018-06-18 15:08:44 +0200 |
| commit | ec623990b34ab0e271141356af96d67a0c4e980d (patch) | |
| tree | c23ed6218721cd55e5a5326b7f145ec7def984ab /os-posix.c | |
| parent | 134f0b3d7ca5fbbd17f21fea87066967ce1d6de5 (diff) | |
| download | qemu-ec623990b34ab0e271141356af96d67a0c4e980d.zip qemu-ec623990b34ab0e271141356af96d67a0c4e980d.tar.gz qemu-ec623990b34ab0e271141356af96d67a0c4e980d.tar.bz2 | |
pc-bios/s390-ccw/net: Add support for pxelinux-style config files
Since it is quite cumbersome to manually create a combined kernel with
initrd image for network booting, we now support loading via pxelinux
configuration files, too. In these files, the kernel, initrd and command
line parameters can be specified seperately, and the firmware then takes
care of glueing everything together in memory after the files have been
downloaded. See this URL for details about the config file layout:
https://www.syslinux.org/wiki/index.php?title=PXELINUX
The user can either specify a config file directly as bootfile via DHCP
(but in this case, the file has to start either with "default" or a "#"
comment so we can distinguish it from binary kernels), or a folder (i.e.
the bootfile name must end with "/") where the firmware should look for
the typical pxelinux.cfg file names, e.g. based on MAC or IP address.
We also support the pxelinux.cfg DHCP options 209 and 210 from RFC 5071.
Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
Tested-by: Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Diffstat (limited to 'os-posix.c')
0 files changed, 0 insertions, 0 deletions