From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xensource.com, xen@lists.fedoraproject.org
Subject: [Fedora-xen] Xen, Linux and EFI.
Date: Wed, 11 Jul 2012 16:45:05 -0400 [thread overview]
Message-ID: <20120711204505.GA9717@phenom.dumpdata.com> (raw)
Hey,
There has been some discussion about EFI and SecureBoot and such.
Most of the time I get questions in the form of "How do I get Fedora 17
with Xen to do EFI", I am going to concentrate on Fedora, but I think
this applies to other distros too.
From my reading (I hadn't actually tried EFI yet), there are two ways
to bootup a system:
- Using grub2.efi. Grub2 does the EFI API calls and calls the Xen hypervisor
as if there were no EFI. This means no need for the EFI calls from
Linux or Xen are required).
- Using xen.efi. Xen can be built as a PE (Portable Executable) and it can
boot as an EFI image. Naturally you also need to provide a configuration
file and here are the details on it:
http://xenbits.xen.org/docs/unstable/misc/efi.html
And you would also need to configure the EFI nvram to execute xen.efi
instead of grub2.efi.
For the Linux side, the kernel needs to make new EFI variant hypercalls.
Currently the SLES kernel is capable of it. The upstream Linux kernel
cannot do it. There were patches proposed for it:
http://lists.xen.org/archives/html/xen-devel/2012-02/msg02027.html
which were mostly ports of how SLES did it (And they should reflect
the proper ownership, which they don't have right now).
The EFI maintainer (Matthew) commented
http://lists.xen.org/archives/html/xen-devel/2012-02/msg00815.html
that he would like a better abstraction model for it. Mainly to
push those calls deeper down (so introduce the registration in the
the efi_calls). Or perhaps by providing in boot_params.efi_info.efi_systab
a finely crafted structure pointing to Linux functions that would
do the hypercalls.
And there you have it. In other words it needs somebody willing to
look at the patches as a baseline and do some exciting new work.
I sadly don't have right now the time to address this :-(
--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
next reply other threads:[~2012-07-11 20:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 20:45 Konrad Rzeszutek Wilk [this message]
2012-07-11 21:27 ` Xen, Linux and EFI Shriram Rajagopalan
2012-07-11 23:12 ` [Fedora-xen] [Xen-devel] " Pasi Kärkkäinen
2012-07-12 13:31 ` Konrad Rzeszutek Wilk
2012-07-12 15:39 ` Shriram Rajagopalan
2012-07-12 16:47 ` Konrad Rzeszutek Wilk
2012-07-23 13:53 ` Jan Beulich
2012-07-12 16:10 ` 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=20120711204505.GA9717@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen@lists.fedoraproject.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.