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.
This CPU should support AVX2. Maybe there is some bios option to disable it.
Apparently the processor should emulate AVX instructions with SSE ones when
there is a bios option to disable AVX. Maybe there is also a bios option to
disable such emulation.
The problem is Hyper-V in a mode that allows live migration if I
understand correctly.
Also, it appears it partially implements the instructions openjdk
uses to check for AVX support.
This is arguably a bug in Hyper-V.
Comment 4Andrew John Hughes
2020-02-12 18:35:49 UTC
Can you be more specific as to which older version works correctly?
I can then look into exactly what change triggered the regression in behaviour.
Waiting for user feedback. Only report so far was that it was required do
downgrade the java version for it to work. It is failing with
java-11-openjdk-11.0.6.10-1.el7_7 and I presume a version that did work is
java-11-openjdk-11.0.3.7-1.el7
If there is information on specific version that did work the bug report
will be updated.
The last known working package for the user is java-11-openjdk-11.0.2.7-0.el7_6
User was previously told to temporarily either a known to work older version, or
experiment with "java -XX:UseAVX=N --version" or "java -XX:UseSSE=N --version"
and see what works for different values of N.
The other alternative is check the Hyper-V setup options that also allow enabling
AVX instructions.
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 (java-11-openjdk bug fix and enhancement update), 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-2020:3919