Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Historically QEMU had a choice of gcrypt or nettle for crypto backends, and currently we pick gcrypt as that has better performance.  In forthcoming QEMU 6.1, there is a new option of using gnutls for crypto backend and with new enough gnutls this has performance on a par with gcrypt for x86 arch at least.

Upstream QEMU will default to using gnutls.

We want to make sure that RHEL honours this default

 - Pass --disable-gcrypt --disable-nettle to configure
 - Remove libgcrypt-devel from BuildReuqires

RHEL-8.x should remain using gcrypt forever, since its gnutls version is too old to be acceptable performance-wise.

Version-Release number of selected component (if applicable):
6.1.0

Danilo - looks to be something for Mirek as part of the 6.1 rebase downstream/build effort.

Moving this to Jon to take a look on that.

QE bot(pre verify): Set 'Verified:Tested,SanityOnly' as gating/tier1 test pass.

Regression testing of luks and luks-inside-qcow2, all passed.


Tested with:
qemu-kvm-6.1.0-2.el9
kernel-5.14.0-0.rc7.54.el9.x86_64


Test results(by automation):
Luks:
Summary: 
Finshed=87, PASS=87

Luks-inside-qcow2:
Summary: 
Finshed=99, PASS=99

Regression tests against qemu-kvm-6.1.0-2.el9.x86_64
For VNC, I have tested password authentication as well as tls/tls+vnc password authentication, no problem found.

VNC client used is virt-viewer-10.0-3.el9.x86_64

Move the bug to 'VERIFIED' per comment 12 and 13, thanks.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new packages: qemu-kvm), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:2307