diff options
author | Christian Borntraeger <borntraeger@de.ibm.com> | 2017-07-12 16:00:41 +0200 |
---|---|---|
committer | Christian Borntraeger <borntraeger@de.ibm.com> | 2017-07-14 12:29:48 +0200 |
commit | 6c5359e161b8e90e14940c0c72025dcfb8ce32f9 (patch) | |
tree | 7e8d007da410b28ec5c6ac5fdf3ab6d26fd0f627 | |
parent | 29d12216dae487a35f54141c6a397a64ec86cfe8 (diff) | |
download | qemu-6c5359e161b8e90e14940c0c72025dcfb8ce32f9.zip |
pc-bios/s390: add s390-netboot.img
It's already possible to do a network boot of an s390x guest with an
external netboot image based on a Linux installation, but it would
be much more convenient if the s390-ccw firmware supported network
booting right out of the box, without the need to assemble such an
external image first.
This is an s390-netboot.img that can be used for network booting.
You can download a combined kernel + initrd image via TFTP
by starting QEMU for example with:
qemu-system-s390x ... -device virtio-net,netdev=n1,bootindex=1 \
-netdev user,id=n1,tftp=/path/to/tftp,bootfile=kernel.img
Note that this version does not support downloading via config
files (i.e. pxelinux config files or .INS config files) yet. This
will be added later.
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
-rw-r--r-- | Makefile | 2 | ||||
-rwxr-xr-x | pc-bios/s390-netboot.img | bin | 0 -> 83864 bytes |
2 files changed, 1 insertions, 1 deletions
@@ -553,7 +553,7 @@ efi-e1000e.rom efi-vmxnet3.rom \ qemu-icon.bmp qemu_logo_no_text.svg \ bamboo.dtb petalogix-s3adsp1800.dtb petalogix-ml605.dtb \ multiboot.bin linuxboot.bin linuxboot_dma.bin kvmvapic.bin \ -s390-ccw.img \ +s390-ccw.img s390-netboot.img \ spapr-rtas.bin slof.bin skiboot.lid \ palcode-clipper \ u-boot.e500 \ diff --git a/pc-bios/s390-netboot.img b/pc-bios/s390-netboot.img Binary files differnew file mode 100755 index 0000000000..295ddfcf6a --- /dev/null +++ b/pc-bios/s390-netboot.img |