From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Sylvain Munaut <s.munaut@whatever-company.com>, daniel.kiper@oracle.com
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen, EFI and kexec
Date: Wed, 9 Nov 2016 11:24:44 -0500 [thread overview]
Message-ID: <20161109162444.GB13019@char.us.oracle.com> (raw)
In-Reply-To: <CAF6-1L5coSSWxbAFcwfXfr+qg9q2Ce+U__JE74XfZmztxq-JAw@mail.gmail.com>
On Wed, Nov 09, 2016 at 03:13:16PM +0100, Sylvain Munaut wrote:
> Hi,
>
>
> A bit of background: What I'm currently trying to do is to network
> boot a first linux image in EFI mode (using UEFI network boot), then
> from that image, kexec into Xen in EFI mode as well.
>
> It's not working.
>
> When you kexec into another linux in EFI mode, kexec actually passes
> some more infos to the kernel to allow it to use EFI mode properly.
> IIUC Linux also maps the various EFI ranges at deterministic addresses
> because the seting up EFI virtual address mode is only allowed once
> per boot and so both the old and new kernel have to use the same
> mappings.
>
> I have seen the patch series by Daniel Kiper to add support for
> multiboot2 protocol and EFI support for it. This seems like a good
> step toward what I'd like to do. Adding multiboot2 support to kexec
> user tools seems like something I could do. This should allow Xen to
> get the info it needs.
>
> However I don't think that'll be sufficient.
>
> By the time kexec will launch Xen, the first kernel will have done an
> "ExitBootServices". And looking at Daniel's patch, that seems to be an
CC-ing Daniel.
> issue.
>
> I'm also not sure if the EFI virtual address mode will be an issue or
> not yet. (i.e. Xen uses the physical address mode, but is that usable
> after the first linux setup the virtual mode).
OK, then that ought to work.
>
> Is there anything else I overlooked that will be an issue ?
Buggy BIOSes?
>
> Is this a use case worth supporting ? (Obviously I think so, but I'm biased :p)
I think the idea of kexecing Xen is quite neat. You could (long-term with
lots of careful work), restart Xen without bringing down the guests.
(Yeah, I know, it sounds insane, but then I am livepatching an hypervisor
so I already have a foot in the looney bin)
>
> And if I'm looking at it the wrong way, what way should I be looking at it ?
>
>
> Cheers,
>
> Sylvain Munaut
>
>
> PS: I'm currently making my way through the 2000+ pages of the EFI
> specs so I probably got some things wrong above ...
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-11-09 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 14:13 Xen, EFI and kexec Sylvain Munaut
2016-11-09 16:24 ` Konrad Rzeszutek Wilk [this message]
2016-11-10 11:23 ` 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=20161109162444.GB13019@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=daniel.kiper@oracle.com \
--cc=s.munaut@whatever-company.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 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).