From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, pavankumar_a@persistent.co.in
Subject: Re: [edk2-devel] reg : UEFI Secure Boot is stuck with Black Screen
Date: Tue, 7 May 2019 14:02:24 +0200 [thread overview]
Message-ID: <81f027fb-c382-4299-ebd4-41c5e1367985@redhat.com> (raw)
In-Reply-To: <4451.1557205198685436806@groups.io>
On 05/07/19 06:59, pavankumar_a@persistent.co.in wrote:
> On Thu, May 2, 2019 at 03:11 AM, <pavankumar_a@persistent.co.in>
> wrote:
>
>>
>> Hi Laszlo,
>
> As you suggested in the in-line mail I have found a machine which
> supports EPT technology in our lab environment. And to maintain a
> homogeneous KVM Host environment used qemu-kvm packages which comes
> with the default repo.The thing is that by default qemu-kvm is not
> supporting q35 machine type .This is the reason earlier we went for
> Cent OS packages so that qemu-kvm can support q35 chipset for Guest
> VM. Can you suggest me on the same , if i wanted to perform with RHEL
> 7.6 how can i proceed.
(Given that you asked earlier off-list as well, and that I happened to
answer there first, I think I won't repeat the answer here. The answer
is not related to upstream edk2 development anyway; it has to do with RH
products / RHEL packages. I would have been fine with answering here
only, but now it's not really useful to duplicate that info, which is
strictly speaking off-topic.
I'm posting this short note just to tell the list that I didn't ignore
the question.)
Thanks
Laszlo
prev parent reply other threads:[~2019-05-07 12:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 10:37 reg : UEFI Secure Boot is stuck with Black Screen Pavan Kumar Aravapalli
2019-04-26 21:26 ` [edk2-devel] " Laszlo Ersek
2019-05-02 10:11 ` pavankumar_a
2019-05-07 4:59 ` pavankumar_a
2019-05-07 12:02 ` Laszlo Ersek [this message]
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=81f027fb-c382-4299-ebd4-41c5e1367985@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