From: Baoquan He <bhe@redhat.com>
To: Yishen Miao <mys721tx@gmail.com>
Cc: kexec@lists.infradead.org
Subject: Re: Unified Kernel Image Support
Date: Mon, 6 Feb 2023 17:19:33 +0800 [thread overview]
Message-ID: <Y+DGJfYEJpbee/bM@MiWiFi-R3L-srv> (raw)
In-Reply-To: <5D04A23B-9A82-4186-AFA8-7E3A0FBBDF86@gmail.com>
On 02/03/23 at 10:46pm, Yishen Miao wrote:
> Hello all,
>
> I am experimenting kexec on my box. It uses systemd-boot as the bootloader and boots from a unified kernel image (objcopy'ed cmdline, kernel, initrdramfs, and microcode updates). As of kexec-tools 2.0.25 and systemd 252.5, when I rum systemctl kexec, it returns the following:
>
>
> # sudo systemctl kexec
> Running /usr/bin/kexec --load "/efi/EFI/Linux/ArchLinux-linux.efi" --append "root=UUID=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"(null)
> Cannot determine the file type of /efi/EFI/Linux/ArchLinux-linux.efi
>
> It seems that systemctl successfully identified the UKI from systemd-boot, however, kexec could not recognize it.
>
> Are there any plans to add UKI support to kexec? Your response is greatly appreciated!
My colleageus mentioned UKI recently. We have plan to support it, while
haven't started to work on that.
I have a testing machine at hand right now, just finished teseting
upstream patches. If you have the detailed steps about how to make UKI,
privately or publicly, I can try it now, and see what we can do.
Thanks
Baoquan
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2023-02-06 9:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 6:46 Unified Kernel Image Support Yishen Miao
2023-02-06 9:19 ` Baoquan He [this message]
2023-02-06 16:33 ` Philipp Rudo
2023-02-06 17:45 ` Yishen Miao
2024-12-22 20:06 ` Yishen Miao
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=Y+DGJfYEJpbee/bM@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=mys721tx@gmail.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