From: Anthony PERARD <anthony.perard@citrix.com>
To: <edk2-devel@lists.01.org>,
Jordan Justen <jordan.l.justen@intel.com>,
Laszlo Ersek <lersek@redhat.com>
Cc: <xen-devel@lists.xen.org>
Subject: OVMF for Xen PVH
Date: Thu, 8 Sep 2016 10:38:09 +0100 [thread overview]
Message-ID: <20160908093809.GR1847@perard.uk.xensource.com> (raw)
Hello,
We are introducing a new virtualisation mode in Xen called PVHv2 (also
called hvmlite in the past). We would like to have a UEFI firmware
running on it to make it easier to start a guest. (Right now, I think it
involves supplying the guest kernel to the guest config, like a PV
guest.)
I'm exploring different possibility of what could be done, and what
should be avoided. It would be nice to have only one binary for both
PVHv2 guest and HVM guest.
Would it be possible to introduce a different entry point in OVMF? The
current one cannot be used at the start of the day of a PVHv2 guest.
If not, we'll try to use the current entry point or create a new package
like it has been done for Xen on ARM.
Thanks for any feedback,
--
Anthony PERARD
next reply other threads:[~2016-09-08 9:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 9:38 Anthony PERARD [this message]
2016-09-08 10:24 ` OVMF for Xen PVH Laszlo Ersek
2016-09-13 13:46 ` Anthony PERARD
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-list 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=20160908093809.GR1847@perard.uk.xensource.com \
--to=devel@edk2.groups.io \
/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