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 1000317 - microcode update should be skipped in virtualized environment
Summary: microcode update should be skipped in virtualized environment
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: microcode_ctl
Version: 6.5
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Anton Arapov
QA Contact: Jeff Bastian
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-23 07:44 UTC by Chao Yang
Modified: 2014-06-18 08:03 UTC (History)
14 users (show)

Fixed In Version: microcode_ctl-1.17-16.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-21 21:41:41 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
patch, update microcode on hosts only (1.17 KB, patch)
2013-08-23 10:57 UTC, Anton Arapov
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1668 0 normal SHIPPED_LIVE microcode_ctl bug fix and enhancement update 2013-11-20 21:52:55 UTC

Description Chao Yang 2013-08-23 07:44:34 UTC
Description of problem:
Lots of failures was observed in guest dmesg. This didn't happen in host dmesg.

--- snip from guest dmesg ---
microcode: CPU0 sig=0x106a5, pf=0x1, revision=0x1
platform microcode: firmware: requesting intel-ucode/06-1a-05
microcode: CPU1 sig=0x106a5, pf=0x1, revision=0x1
platform microcode: firmware: requesting intel-ucode/06-1a-05
microcode: CPU2 sig=0x106a5, pf=0x1, revision=0x1
platform microcode: firmware: requesting intel-ucode/06-1a-05
microcode: CPU3 sig=0x106a5, pf=0x1, revision=0x1
platform microcode: firmware: requesting intel-ucode/06-1a-05
microcode: CPU4 sig=0x106a5, pf=0x1, revision=0x1
platform microcode: firmware: requesting intel-ucode/06-1a-05
microcode: CPU5 sig=0x106a5, pf=0x1, revision=0x1
platform microcode: firmware: requesting intel-ucode/06-1a-05
microcode: CPU6 sig=0x106a5, pf=0x1, revision=0x1
platform microcode: firmware: requesting intel-ucode/06-1a-05
microcode: CPU7 sig=0x106a5, pf=0x1, revision=0x1
platform microcode: firmware: requesting intel-ucode/06-1a-05
Microcode Update Driver: v2.00 <tigran.co.uk>, Peter Oruba
microcode: CPU0 update to revision 0x19 failed
microcode: CPU1 update to revision 0x19 failed
microcode: CPU2 update to revision 0x19 failed
microcode: CPU3 update to revision 0x19 failed
microcode: CPU4 update to revision 0x19 failed
microcode: CPU5 update to revision 0x19 failed
microcode: CPU6 update to revision 0x19 failed
microcode: CPU7 update to revision 0x19 failed
parport_pc 00:05: reported by Plug and Play ACPI
parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]

--- snip from host dmesg ---
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU0 sig=0x106a5, pf=0x1, revision=0x11
Aug 20 17:24:27 intel-e5530-8-2 kernel: platform microcode: firmware: requesting intel-ucode/06-1a-05
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU1 sig=0x106a5, pf=0x1, revision=0x11
Aug 20 17:24:27 intel-e5530-8-2 kernel: platform microcode: firmware: requesting intel-ucode/06-1a-05
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU2 sig=0x106a5, pf=0x1, revision=0x11
Aug 20 17:24:27 intel-e5530-8-2 kernel: platform microcode: firmware: requesting intel-ucode/06-1a-05
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU3 sig=0x106a5, pf=0x1, revision=0x11
Aug 20 17:24:27 intel-e5530-8-2 kernel: platform microcode: firmware: requesting intel-ucode/06-1a-05
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU4 sig=0x106a5, pf=0x1, revision=0x11
Aug 20 17:24:27 intel-e5530-8-2 kernel: platform microcode: firmware: requesting intel-ucode/06-1a-05
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU5 sig=0x106a5, pf=0x1, revision=0x11
Aug 20 17:24:27 intel-e5530-8-2 kernel: platform microcode: firmware: requesting intel-ucode/06-1a-05
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU6 sig=0x106a5, pf=0x1, revision=0x11
Aug 20 17:24:27 intel-e5530-8-2 kernel: platform microcode: firmware: requesting intel-ucode/06-1a-05
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU7 sig=0x106a5, pf=0x1, revision=0x11
Aug 20 17:24:27 intel-e5530-8-2 kernel: platform microcode: firmware: requesting intel-ucode/06-1a-05
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU8 sig=0x106a5, pf=0x1, revision=0x11
Aug 20 17:24:27 intel-e5530-8-2 kernel: platform microcode: firmware: requesting intel-ucode/06-1a-05
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU9 sig=0x106a5, pf=0x1, revision=0x11
Aug 20 17:24:27 intel-e5530-8-2 kernel: platform microcode: firmware: requesting intel-ucode/06-1a-05
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU10 sig=0x106a5, pf=0x1, revision=0x11
Aug 20 17:24:27 intel-e5530-8-2 kernel: platform microcode: firmware: requesting intel-ucode/06-1a-05
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU11 sig=0x106a5, pf=0x1, revision=0x11
Aug 20 17:24:27 intel-e5530-8-2 kernel: platform microcode: firmware: requesting intel-ucode/06-1a-05
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU12 sig=0x106a5, pf=0x1, revision=0x11
Aug 20 17:24:27 intel-e5530-8-2 kernel: platform microcode: firmware: requesting intel-ucode/06-1a-05
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU13 sig=0x106a5, pf=0x1, revision=0x11
Aug 20 17:24:27 intel-e5530-8-2 kernel: platform microcode: firmware: requesting intel-ucode/06-1a-05
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU14 sig=0x106a5, pf=0x1, revision=0x11
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU15 sig=0x106a5, pf=0x1, revision=0x11
Aug 20 17:24:27 intel-e5530-8-2 kernel: platform microcode: firmware: requesting intel-ucode/06-1a-05
Aug 20 17:24:27 intel-e5530-8-2 kernel: Microcode Update Driver: v2.00 <tigran.co.uk>, Peter Oruba
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU0 updated to revision 0x19, date = 2013-06-21
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU1 updated to revision 0x19, date = 2013-06-21
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU2 updated to revision 0x19, date = 2013-06-21
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU3 updated to revision 0x19, date = 2013-06-21
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU4 updated to revision 0x19, date = 2013-06-21
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU5 updated to revision 0x19, date = 2013-06-21
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU6 updated to revision 0x19, date = 2013-06-21
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU7 updated to revision 0x19, date = 2013-06-21
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU8 updated to revision 0x19, date = 2013-06-21
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU9 updated to revision 0x19, date = 2013-06-21
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU10 updated to revision 0x19, date = 2013-06-21
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU11 updated to revision 0x19, date = 2013-06-21
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU12 updated to revision 0x19, date = 2013-06-21
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU13 updated to revision 0x19, date = 2013-06-21
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU14 updated to revision 0x19, date = 2013-06-21
Aug 20 17:24:27 intel-e5530-8-2 kernel: microcode: CPU15 updated to revision 0x19, date = 2013-06-21
Aug 20 17:24:27 intel-e5530-8-2 kernel: kvm: VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL does not work properly. Using workaround


Version-Release number of selected component (if applicable):
2.6.32-414.el6.x86_64
qemu-kvm-0.12.1.2-2.397.el6.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
This log is a little different from Bug 860929 - microcode: CPUx: update failed (for patch_level=0x6000624)

Comment 2 Paolo Bonzini 2013-08-23 08:31:01 UTC
Microcode_ctl should detect hypervisor presence (execute CPUID with EAX=1, check bit 31 of ECX on output), and skip hypervisor updates if so.

Comment 3 Anton Arapov 2013-08-23 10:57:25 UTC
Created attachment 789554 [details]
patch, update microcode on hosts only

This should do the trick.

Comment 4 Anton Arapov 2013-08-23 11:00:06 UTC
I don't mind push it. It is also easy for QA to test.

Taking schedule into account, one should bother with blocker flag if he wants it in RHEL 6.5

Comment 18 errata-xmlrpc 2013-11-21 21:41:41 UTC
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, and where to find the updated
files, follow the link below.

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

http://rhn.redhat.com/errata/RHBA-2013-1668.html


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