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.
Bug 1612299 - microcode_ctl no longer includes microcode in initramfs on Xen dom0
Summary: microcode_ctl no longer includes microcode in initramfs on Xen dom0
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: microcode_ctl
Version: 7.5
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Eugene Syromiatnikov
QA Contact: Rachel Sibley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-03 16:50 UTC by Kevin Stange
Modified: 2018-11-12 20:49 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-12 20:49:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Kevin Stange 2018-08-03 16:50:06 UTC
Description of problem:

Since the microcode_ctl update you check for 'hypervisor' CPU flag, which means it refuses to apply the update inside of a Xen dom0, which is a type of guest.

This breaks the xen feature ucode=scan which will check the initramfs for the microcode and apply it automatically, which I've been using.

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

microcode_ctl-2.1-29.10.el7_5.x86_64

How reproducible:

100%

Steps to Reproduce:
1. Update microcode_ctl
2. Check initramfs type with 'file' (should be cpio, but will be gzip)

Actual results:

initramfs contains no GenuineIntel.bin

Expected results:

initramfs should contain GenuineIntel.bin on platforms with microcode

Additional info:

I found this check at line 146 of the update_ucode script:

        if grep -q '^flags[[:space:]]*:.*hypervisor' /proc/cpuinfo; then

This check is too broad for Xen.  Might make sense to change this check /sys/hypervisor for values related to Xen.  It looks like /sys/hypervisor/uuid will be '00000000-0000-0000-0000-000000000000' in case it's a dom0 and otherwise populated if it's a domU.

Comment 2 Kevin Stange 2018-08-03 16:55:12 UTC
I've been informed that you might also try one of these checks:

1) call systemd-detect-virt

outputs 'none' in dom0
outputs 'xen' in domU
outputs 'kvm' in KVM guest

2) call virt-what

3) check for /proc/xen/capabilities existence

Comment 3 Kevin Stange 2018-08-03 17:01:40 UTC
Correction: For option 3) check for /proc/xen/capabilities with 'control_d', not for its existence

Comment 15 Eugene Syromiatnikov 2018-11-12 20:49:14 UTC
Hello.

RHEL 7 kernel doesn't support Xen dom0. As a possible workaround, I can suggest either to update to a kernel that is based on 3.10.0-862.14.1 (or any newer, see additional information in /usr/share/microcode_ctl/ucode_with_caveats/intel/readme), or updating to microcode_ctl-2.1-29.12 (or newer) and enforce addition of intel microcode files to the initramfs by creating /etc/microcode_ctl/ucode_with_caveats/intel-force-early file (see /usr/share/doc/microcode_ctl/README.caveats for details).


Note You need to log in before you can comment on or make changes to this bug.