From: PGNet Dev <pgnet.dev@gmail.com>
To: Daniel Kiper <daniel.kiper@oracle.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH v2 00/23] x86: multiboot2 protocol support
Date: Fri, 30 Oct 2015 11:36:03 -0700 [thread overview]
Message-ID: <5633B893.4040800@gmail.com> (raw)
In-Reply-To: <20151030182318.GM3489@olila.local.net-space.pl>
On 10/30/2015 11:23 AM, Daniel Kiper wrote:
> I missed that you are talking about PE executable. However,
> as it was said you must create xen.cfg in advance and put it in the same
> directory with xen.efi. Please check xen/docs/misc/efi.markdown for more details.
TBH I'm not clear on whether the executable is -- or more importantly,
still will be -- needed.
Atm, I'm manually creating the xen.cfg/xen.ini and chainloading via
GRUB2. Hence the mess, and asking about simpler approaches.
IIUC, systemd-boot is a rename (fork?) of gummiboot. WAS going to try
it awhile ago, as a simpler alternative to Grub2, but saw only that the
project had been emptied out. Didn't realize that it'd been subsumed.
Interestingly, from https://en.wikipedia.org/wiki/Gummiboot_(software)
"Red Hat's Fedora Project does not use gummiboot for booting UEFI
systems; instead, it will use efilinux to chainload GRUB."
Trying to find out the WHY in the different boot-Xen-on-UEFI approaches,
let alone simply what just works, is a challenge.
next prev parent reply other threads:[~2015-10-30 18:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 15:44 [PATCH v2 00/23] x86: multiboot2 protocol support PGNet Dev
2015-10-30 17:29 ` Daniel Kiper
2015-10-30 18:06 ` PGNet Dev
2015-10-30 18:23 ` Daniel Kiper
2015-10-30 18:36 ` PGNet Dev [this message]
2015-10-30 20:04 ` Daniel Kiper
-- strict thread matches above, loose matches on Subject: below --
2015-07-20 14:28 Daniel Kiper
2015-07-21 9:39 ` Jan Beulich
2015-07-21 9:39 ` Jan Beulich
2015-07-20 14:28 Daniel Kiper
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=5633B893.4040800@gmail.com \
--to=pgnet.dev@gmail.com \
--cc=daniel.kiper@oracle.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.