From mboxrd@z Thu Jan  1 00:00:00 1970
Authentication-Results: mx.groups.io;
 dkim=missing; spf=pass (domain: redhat.com, ip: 209.132.183.28, mailfrom: lersek@redhat.com)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 by groups.io with SMTP; Tue, 07 May 2019 05:02:31 -0700
Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mx1.redhat.com (Postfix) with ESMTPS id 39D143019898;
	Tue,  7 May 2019 12:02:26 +0000 (UTC)
Received: from lacos-laptop-7.usersys.redhat.com (ovpn-120-152.rdu2.redhat.com [10.10.120.152])
	by smtp.corp.redhat.com (Postfix) with ESMTP id 7AC10174B3;
	Tue,  7 May 2019 12:02:25 +0000 (UTC)
Subject: Re: [edk2-devel] reg : UEFI Secure Boot is stuck with Black Screen
To: devel@edk2.groups.io, pavankumar_a@persistent.co.in
References: <23646.1556791866430355880@groups.io>
 <4451.1557205198685436806@groups.io>
From: "Laszlo Ersek" <lersek@redhat.com>
Message-ID: <81f027fb-c382-4299-ebd4-41c5e1367985@redhat.com>
Date: Tue, 7 May 2019 14:02:24 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <4451.1557205198685436806@groups.io>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.47]); Tue, 07 May 2019 12:02:31 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit

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