From: "Andrew Fish" <afish@apple.com>
To: devel@edk2.groups.io, "Tomas Pilar (tpilar)" <tpilar@solarflare.com>
Subject: Re: [edk2-devel] Help needed in building UEFI qcow2 images
Date: Wed, 22 May 2019 08:58:47 -0700 [thread overview]
Message-ID: <32BDEDBA-2972-4D56-ABA8-E4570A56E85C@apple.com> (raw)
In-Reply-To: <ed4cfca6710b43f78ea5d6d05a87b676@ukex01.SolarFlarecom.com>
[-- Attachment #1: Type: text/plain, Size: 2318 bytes --]
Tom,
Looks like the mailing list stripped your attachment.
Thanks,
Andrew Fish
> On May 22, 2019, at 4:19 AM, Tomas Pilar (tpilar) <tpilar@solarflare.com> wrote:
>
> Hi Pavan,
>
> I am currently playing around with setting up a OVMF based test framework myself. You likely need to tell qemu to use OVMF as it’s firmware. I attach my current working libvirt XML file for creating UEFI VMs (diskless) – note the <loader> and the <nvram> elements within the <os> element.
>
> You want to add a disk sourced from the qcow image and that should work.
>
> Cheers,
> Tom
>
> From: devel@edk2.groups.io <mailto:devel@edk2.groups.io> <devel@edk2.groups.io <mailto:devel@edk2.groups.io>> On Behalf Of Pavan Kumar Aravapalli
> Sent: 22 May 2019 12:02
> To: Devel EDK2 <devel@edk2.groups.io <mailto:devel@edk2.groups.io>>
> Subject: [edk2-devel] Help needed in building UEFI qcow2 images
>
> Hi,
>
>
>
> [re-posting the question]
>
>
>
> I am looking for information/documentation which helps me in enabling UEFI boot to the existing (KVM)VM template. I am trying for CentOS 6.5(64-bit) no GUI 64-bit (KVM) template.
>
>
>
>
>
> I found some images available over https://www.kraxel.org/repos/images/ <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.kraxel.org_repos_images_&d=DwMFAw&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=SzAVyxtJHZm7PriTfxFyvkqqZ_OgUqnNtgjrlf7jVU4&m=txzCgRJWkEmPJeuUxTWCEaTYpYEUWr6BmgcbVIpvuI0&s=VNfaavLgc8f7brJsIT2rTlp9QzZRyNUOTsp7rqTHK6E&e=> with fedora os, but I am looking for uefi enabled Cent OS template. It would be helpfull if any documentation or steps provided for the same.
>
>
>
>
> Regards,
>
> Pavan.
>
> DISCLAIMER
> ==========
> This e-mail may contain privileged and confidential information which is the property of Accelerite, a Persistent Systems business. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Accelerite, a Persistent Systems business does not accept any liability for virus infected mails.
>
> <kvm.xml>
[-- Attachment #2: Type: text/html, Size: 7363 bytes --]
next prev parent reply other threads:[~2019-05-22 15:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 11:02 Help needed in building UEFI qcow2 images Pavan Kumar Aravapalli
2019-05-22 11:19 ` Tomas Pilar (tpilar)
2019-05-22 15:58 ` Andrew Fish [this message]
2019-05-22 16:57 ` [edk2-devel] " Tomas Pilar (tpilar)
2019-05-22 17:05 ` Andrew Fish
2019-05-22 19:05 ` Laszlo Ersek
2019-05-22 19:10 ` Andrew Fish
2019-05-23 13:45 ` Laszlo Ersek
2019-06-03 19:21 ` Pavan Kumar Aravapalli
2019-06-04 10:49 ` Laszlo Ersek
2019-06-04 11:28 ` Pavan Kumar Aravapalli
2019-06-04 16:10 ` Laszlo Ersek
2019-06-05 5:49 ` Gerd Hoffmann
2019-06-07 9:13 ` Pavan Kumar Aravapalli
2019-06-05 18:19 ` Pavan Kumar Aravapalli
2019-06-06 7:43 ` Laszlo Ersek
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=32BDEDBA-2972-4D56-ABA8-E4570A56E85C@apple.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