From: Cornelia Huck <cohuck@redhat.com>
To: Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Thomas Huth <thuth@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>
Subject: Re: [Qemu-devel] Suggested Wiki Update
Date: Tue, 12 Sep 2017 13:18:23 +0200 [thread overview]
Message-ID: <20170912131823.1f7a9e03.cohuck@redhat.com> (raw)
In-Reply-To: <b0cd3b7a-fcc8-03ed-55dd-cbdba2ff59ec@linux.vnet.ibm.com>
On Tue, 12 Sep 2017 10:57:14 +0200
Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com> wrote:
> Hi,
>
> the content of https://wiki.qemu.org/index.php/Features/S390xNetworkBoot
> is slightly outdated since proper DHCP based netboot support for s390x
> has been implemented by the series ending with commit 29d1221.
>
> As it is still desirable to provide some instructions on building
> network bootable images for the s390x architecture, I'd like to suggest
> that the text is replaced (see proposal below). Conny, could I once more
> request your help in that matter?
>
> == Building a s390 network bootable binary ==
>
> Since 2.10 QEMU offers network boot support which allows to load a
> binary from a TFTP server and boot it. As s390 network bootable images
> are not very common, this document gives a brief overview on how to
> build one.
>
> A s390 network bootable image can be built by bundling some shell
> scripts, busybox and the kexec binary bundled into an initial ramdisk
> and append that to a kernel image. An existing s390 system can be used
> as source.
>
> One way to do that is to take a kernel and an installer initial ramdisk
> from a distribution's DVD/ISO and concatenate them. Some fixups are
> necessary int the new binary, which can be done by using the script in
> [https://github.com/ibm-s390-tools/s390-tools/blob/master/netboot/mk-s390image].
> Booting this image would then start the installation process as if
> booted from the DVD.
>
> Another possible way is to build a binary that behaves similar to the
> PXELINUX boot loader. In this case an initial ramdisk with an init
> process triggering the PXELINUX-like processing has to be built as
> described in
> [https://github.com/ibm-s390-tools/s390-tools/tree/master/netboot]. The
> site also contains a script assisting in the creation of such an initial
> ramdisk.
>
Looks good.
Can you perhaps add a sentence that the base support is available with
2.9 and netboot with 2.10? ('Overview' looks like a good place for
that.)
next prev parent reply other threads:[~2017-09-12 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 8:57 [Qemu-devel] Suggested Wiki Update Viktor Mihajlovski
2017-09-12 10:48 ` Christian Borntraeger
2017-09-12 11:18 ` Cornelia Huck [this message]
2017-09-12 11:25 ` Thomas Huth
2017-09-12 11:56 ` Viktor Mihajlovski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170912131823.1f7a9e03.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=mihajlov@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).