public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: "Tiger Liu(BJ-RD)" <TigerLiu@zhaoxin.com>
Cc: "'edk2-devel@lists.01.org'" <edk2-devel@lists.01.org>,
	Anthony Perard <anthony.perard@citrix.com>,
	Julien Grall <julien.grall@linaro.org>
Subject: Re: OVMF package : Question about Qemu/Xen support
Date: Mon, 5 Mar 2018 10:15:00 +0100	[thread overview]
Message-ID: <9ca0e506-4319-2177-a0e8-bd153a4b0fac@redhat.com> (raw)
In-Reply-To: <b6e6293bba0848169ef944b435d5dbb9@zhaoxin.com>

On 03/05/18 06:49, Tiger Liu(BJ-RD) wrote:
> Hi, experts:
> I have a question about Ovmf.
> 
> Must Ovmf be run with qemu tool?
> Or It could be run with Xen without needed qemu software.
> 
> It seems Xen began to support uefi boot from 4.4 version.

- From the Xen wiki:

https://wiki.xenproject.org/wiki/OVMF

> One thing to have in mind is Xen supports both its own QEMU fork
> called qemu-traditional and upstream QEMU called qemu-xen. OVMF only
> supports the latter. Xen 4.4 has upstream QEMU configured for all HVM
> guests by default, so it is fine to not specify which QEMU to use in
> guest config file. But if you have already configured qemu-traditional
> for your guest you would need to delete / comment out that line.

See also

https://wiki.xenproject.org/wiki/Xen_Project_Release_Features#Device_Models_and_Virtual_Firmware

- I'm also CC'ing the OVMF reviewers for Xen (from the "Maintainers.txt"
file).

Thanks
Laszlo


  reply	other threads:[~2018-03-05  9:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-05  5:49 OVMF package : Question about Qemu/Xen support Tiger Liu(BJ-RD)
2018-03-05  9:15 ` Laszlo Ersek [this message]
2018-03-05  9:35   ` 答复: " Tiger Liu(BJ-RD)
  -- strict thread matches above, loose matches on Subject: below --
2018-04-02  6:55 Tiger Liu(BJ-RD)
2018-04-03 10:36 ` Laszlo Ersek
2018-04-04  0:38 Tiger Liu(BJ-RD)

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=9ca0e506-4319-2177-a0e8-bd153a4b0fac@redhat.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