Bug 848595 - kernel(clocksource_register) changed, causes dependency issues with Microsoft's Linux Integration Services
kernel(clocksource_register) changed, causes dependency issues with Microsoft...
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel (Show other bugs)
6.3
All Linux
unspecified Severity medium
: rc
: ---
Assigned To: Prarit Bhargava
Red Hat Kernel QE team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-08-15 18:17 EDT by Orion Poplawski
Modified: 2012-08-17 15:23 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-08-17 15:23:04 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Orion Poplawski 2012-08-15 18:17:39 EDT
Description of problem:

Trying to install Microsoft's Linux Integration Services on a EL6.3 VM you get:

error: Failed dependencies:
        kernel(clocksource_register) = 0xd88be65d is needed by kmod-microsoft-hyper-v-rhel63.3-4.20120605.x86_64

Indeed, that kernel provide changed from the 6.2 kernels to 6.3:

# rpm -q kernel-2.6.32-220.23.1.el6.x86_64 --provides | grep -F 'kernel(clocksource_register)'
kernel(clocksource_register) = 0xd88be65d
# rpm -q kernel-2.6.32-279.1.1.el6.x86_64 --provides | grep -F 'kernel(clocksource_register)'
kernel(clocksource_register) = 0xd2235d73

No idea if this was intentional or not or if this particular KABI is not expected to stay the same.

Version-Release number of selected component (if applicable):
kernel-2.6.32-279.1.1.el6.x86_64
Comment 4 Prarit Bhargava 2012-08-17 15:23:04 EDT
This is a Microsoft bug and not a RHEL bug.  I'll try to get some sort of message to Microsoft through our internal contacts about the situation but, again, this isn't a RHEL bug.

P.

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