From: Philipp Rudo <prudo@redhat.com>
To: kexec@lists.infradead.org
Subject: Is it possible to use a stream for initrd=
Date: Tue, 15 Feb 2022 11:27:40 +0100 [thread overview]
Message-ID: <20220215112740.587048c7@rhtmp> (raw)
In-Reply-To: <CAHfPjO8XAmK9tbPNpMZO9D9h7MJqMjixhn9hTYmgVK1T2Fxcig@mail.gmail.com>
Hi Tobias,
On Wed, 9 Feb 2022 10:32:24 +0100
Tobias Powalowski <tobias.powalowski@googlemail.com> wrote:
> Sorry you misunderstood, I don't want to create the initrd.img file.
> I want to pass the zstd directly to kexec initrd= option.
sorry, that is not possible. The kexec-tools expect a file name with
--initrd. Simply passing a binary blob to be used as initrd isn't
implemented.
Thanks
Philipp
> greetings
> tpowa
>
> Am Mi., 9. Feb. 2022 um 10:28 Uhr schrieb Baoquan He <bhe@redhat.com>:
> >
> > On 02/09/22 at 10:16am, Tobias Powalowski wrote:
> > > Hi,
> > > I have a tmp directory with all files placed in:
> > > find . -mindepth 1 -printf '%P\0' | sort -z | LANG=C bsdtar --uid 0
> > > --gid 0 --null -cnf - -T - |\
> > > LANG=C bsdtar --null -cf - --format=newc @- | zstd -T0 > /initrd.img
> > >
> > > and this initrd.img I want to write into kexec without creating the initrd file.
> > >
> > > kexec -l /vmlinuz-linux --initrd=/initrd.img --reuse-cmdline
> > > systemctl kexec
> >
> > See manpage of kexec, the EXAMPLE part:
> >
> > kexec -l /boot/vmlinux --initrd=/boot/initrd --reuse-cmdline
> > kexec -e
> >
>
>
next prev parent reply other threads:[~2022-02-15 10:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 15:36 Is it possible to use a stream for initrd= Tobias Powalowski
2022-02-09 3:21 ` Baoquan He
2022-02-09 9:16 ` Tobias Powalowski
2022-02-09 9:28 ` Baoquan He
2022-02-09 9:32 ` Tobias Powalowski
2022-02-15 10:27 ` Philipp Rudo [this message]
2022-02-15 10:31 ` Tobias Powalowski
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=20220215112740.587048c7@rhtmp \
--to=prudo@redhat.com \
--cc=kexec@lists.infradead.org \
/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