[users] coretemp not working on Xeon L5320

[Kai Schaetzl]

I installed kmod-coretemp-xen-1.1-8.el5.elrepo.x86_64 on a machine with
two L5320 CPUs. Unfortunately, it can't get inserted. It throws an error

kernel: coretemp: Unknown symbol rdmsr_safe_on_cpu

The system is freshly setup with new OS. There was another CPU in the
system (normal X51something) before the L, but the coretemp module wasn't
installed on that 32bit system. So, I'm not sure if it would have worked
with that.
Is this maybe functionality not available on an L5-series CPU?
Can anyone compare if it works on his L5-series CPU?

Googling around it looks like lm-sensors might be the best location to
inquire further. Correct?

Kai

[Ned Slider]

Post by Kai Schaetzl
I installed kmod-coretemp-xen-1.1-8.el5.elrepo.x86_64 on a machine with
two L5320 CPUs. Unfortunately, it can't get inserted. It throws an error
kernel: coretemp: Unknown symbol rdmsr_safe_on_cpu
The system is freshly setup with new OS. There was another CPU in the
system (normal X51something) before the L, but the coretemp module wasn't
installed on that 32bit system. So, I'm not sure if it would have worked
with that.
Is this maybe functionality not available on an L5-series CPU?
Can anyone compare if it works on his L5-series CPU?
Googling around it looks like lm-sensors might be the best location to
inquire further. Correct?
Kai

Nope, that's an elrepo package and it's an elrepo issue. If you'd care
to file a bug here:

http://elrepo.org/bugs

I'll be more than happy to look at it for you.

Thanks.

[Ned Slider]

Post by Kai Schaetzl
I installed kmod-coretemp-xen-1.1-8.el5.elrepo.x86_64 on a machine with
two L5320 CPUs. Unfortunately, it can't get inserted. It throws an error
kernel: coretemp: Unknown symbol rdmsr_safe_on_cpu

Hi Kai,

I looked into this a little further and confirmed the bug.

Unfortunately, later versions of kmod-coretemp are not compatible with
xen kernels. In this instance it appears Red Hat have not backported
certain interfaces into the xen kernel variants which coretemp uses (but
have backported them to the regular (non-xen) kernel). In fact one can
see this first hand as Red Hat backported the coretemp module into
RHEL-5.5 (kernel-2.6.18-194.el5), but *only* for non-xen variants! I
wasn't aware the differences between xen and non-xen kernel variants
were so wide reaching.

With the absence of such interfaces it is becoming increasingly
difficult to continue to backport certain drivers to the xen kernel
platform, and as such we will probably just drop support for xen kernels
where that happens.

To this end I have removed kmod-coretemp-xen-1.1-8.el5.elrepo from the
repository (as it's clearly broken) and have confirmed that the latest
version to support the xen kernel is kmod-coretemp-xen-1.1-6.el5.elrepo.
If you uninstall your current version and reinstall, yum should now pull
in kmod-coretemp-xen-1.1-6.el5.elrepo that does support xen kernels. If
this version fails to support future CPU revisions then we might be able
to backport support for that but it will likely mean maintaining a
separate branch for xen kernels. As there is no native coretemp driver
in the xen kernel it's probably worthwhile, but I'd also be tempted to
file an RFE/patch upstream with Red Hat for native support in xen kernels.

I hope that helps.

[Yury V. Zaytsev]

In fact one can see this first hand as Red Hat backported the coretemp
module into RHEL-5.5 (kernel-2.6.18-194.el5), but *only* for non-xen
variants! I wasn't aware the differences between xen and non-xen
kernel variants were so wide reaching.

Well, maybe someone with an active support contract could talk to their
manager about this... who knows, maybe it's not so complicated to
backport after all, it's just that they need a little kick.

[Ned Slider]

Post by Yury V. Zaytsev

In fact one can see this first hand as Red Hat backported the coretemp
module into RHEL-5.5 (kernel-2.6.18-194.el5), but *only* for non-xen
variants! I wasn't aware the differences between xen and non-xen
kernel variants were so wide reaching.

Well, maybe someone with an active support contract could talk to their
manager about this... who knows, maybe it's not so complicated to
backport after all, it's just that they need a little kick.

Yes, it's not difficult as they've done it (albeit with older upstream
code) for the regular kernel and our earlier v1.1-6 kmod package runs
fine on xen too. However, I think it's largely academic now as RHEL5 is
nearing 4 years old and hence soon entering it's second phase of support
during which they are unlikely to add new functionality. The last time I
filed a request for a refresh of an existing driver (in 5.1) it took 2
years until 5.5 to get released:

https://bugzilla.redhat.com/show_bug.cgi?id=446061

so I'm not holding my breath on getting any new drivers into RHEL5 now -
I think we've missed that boat :-)

[Ned Slider]

Post by Yury V. Zaytsev

In fact one can see this first hand as Red Hat backported the coretemp
module into RHEL-5.5 (kernel-2.6.18-194.el5), but *only* for non-xen
variants! I wasn't aware the differences between xen and non-xen
kernel variants were so wide reaching.

Well, maybe someone with an active support contract could talk to their
manager about this... who knows, maybe it's not so complicated to
backport after all, it's just that they need a little kick.

Yes, it's not difficult as they've done it (albeit with older upstream
code) for the regular kernel and our earlier v1.1-6 kmod package runs
fine on xen too. However, I think it's largely academic now as RHEL5 is
nearing 4 years old and hence soon entering it's second phase of support
during which they are unlikely to add new functionality. The last time I
filed a request for a refresh of an existing driver (in 5.1) it took 2
years until 5.5 to get released:

https://bugzilla.redhat.com/show_bug.cgi?id=446061

so I'm not holding my breath on getting any new drivers into RHEL5 now -
I think we've missed that boat :-)

[Ned Slider]

Post by Yury V. Zaytsev

In fact one can see this first hand as Red Hat backported the coretemp
module into RHEL-5.5 (kernel-2.6.18-194.el5), but *only* for non-xen
variants! I wasn't aware the differences between xen and non-xen
kernel variants were so wide reaching.

Well, maybe someone with an active support contract could talk to their
manager about this... who knows, maybe it's not so complicated to
backport after all, it's just that they need a little kick.

Yes, it's not difficult as they've done it (albeit with older upstream
code) for the regular kernel and our earlier v1.1-6 kmod package runs
fine on xen too. However, I think it's largely academic now as RHEL5 is
nearing 4 years old and hence soon entering it's second phase of support
during which they are unlikely to add new functionality. The last time I
filed a request for a refresh of an existing driver (in 5.1) it took 2
years until 5.5 to get released:

https://bugzilla.redhat.com/show_bug.cgi?id=446061

so I'm not holding my breath on getting any new drivers into RHEL5 now -
I think we've missed that boat :-)

[Ned Slider]

Post by Yury V. Zaytsev

In fact one can see this first hand as Red Hat backported the coretemp
module into RHEL-5.5 (kernel-2.6.18-194.el5), but *only* for non-xen
variants! I wasn't aware the differences between xen and non-xen
kernel variants were so wide reaching.

Well, maybe someone with an active support contract could talk to their
manager about this... who knows, maybe it's not so complicated to
backport after all, it's just that they need a little kick.

Yes, it's not difficult as they've done it (albeit with older upstream
code) for the regular kernel and our earlier v1.1-6 kmod package runs
fine on xen too. However, I think it's largely academic now as RHEL5 is
nearing 4 years old and hence soon entering it's second phase of support
during which they are unlikely to add new functionality. The last time I
filed a request for a refresh of an existing driver (in 5.1) it took 2
years until 5.5 to get released:

https://bugzilla.redhat.com/show_bug.cgi?id=446061

so I'm not holding my breath on getting any new drivers into RHEL5 now -
I think we've missed that boat :-)

[Ned Slider]

Post by Yury V. Zaytsev

In fact one can see this first hand as Red Hat backported the coretemp
module into RHEL-5.5 (kernel-2.6.18-194.el5), but *only* for non-xen
variants! I wasn't aware the differences between xen and non-xen
kernel variants were so wide reaching.

Well, maybe someone with an active support contract could talk to their
manager about this... who knows, maybe it's not so complicated to
backport after all, it's just that they need a little kick.

Yes, it's not difficult as they've done it (albeit with older upstream
code) for the regular kernel and our earlier v1.1-6 kmod package runs
fine on xen too. However, I think it's largely academic now as RHEL5 is
nearing 4 years old and hence soon entering it's second phase of support
during which they are unlikely to add new functionality. The last time I
filed a request for a refresh of an existing driver (in 5.1) it took 2
years until 5.5 to get released:

https://bugzilla.redhat.com/show_bug.cgi?id=446061

so I'm not holding my breath on getting any new drivers into RHEL5 now -
I think we've missed that boat :-)

[Kai Schaetzl]

Thanks for the help and sorry for posting to the wrong list. I use so few
stuff from elrepo that I didn't recognize it's not rf.
I installed the version you mention and it's working fine, thanks!
Just before your posting I created a Mantis account on elrepo that I
probably won't need in the near future ;-) I noticed that there is
something wrong going on. My proxy told me there was no response after
submitting the filled form. Nevertheless, the account was created. You may
want to look into this.

Kai

[Yury V. Zaytsev]

In fact one can see this first hand as Red Hat backported the coretemp
module into RHEL-5.5 (kernel-2.6.18-194.el5), but *only* for non-xen
variants! I wasn't aware the differences between xen and non-xen
kernel variants were so wide reaching.

Well, maybe someone with an active support contract could talk to their
manager about this... who knows, maybe it's not so complicated to
backport after all, it's just that they need a little kick.

[Kai Schaetzl]

Thanks for the help and sorry for posting to the wrong list. I use so few
stuff from elrepo that I didn't recognize it's not rf.
I installed the version you mention and it's working fine, thanks!
Just before your posting I created a Mantis account on elrepo that I
probably won't need in the near future ;-) I noticed that there is
something wrong going on. My proxy told me there was no response after
submitting the filled form. Nevertheless, the account was created. You may
want to look into this.

Kai

[Yury V. Zaytsev]

In fact one can see this first hand as Red Hat backported the coretemp
module into RHEL-5.5 (kernel-2.6.18-194.el5), but *only* for non-xen
variants! I wasn't aware the differences between xen and non-xen
kernel variants were so wide reaching.

Well, maybe someone with an active support contract could talk to their
manager about this... who knows, maybe it's not so complicated to
backport after all, it's just that they need a little kick.

[Kai Schaetzl]

Thanks for the help and sorry for posting to the wrong list. I use so few
stuff from elrepo that I didn't recognize it's not rf.
I installed the version you mention and it's working fine, thanks!
Just before your posting I created a Mantis account on elrepo that I
probably won't need in the near future ;-) I noticed that there is
something wrong going on. My proxy told me there was no response after
submitting the filled form. Nevertheless, the account was created. You may
want to look into this.

Kai

[Yury V. Zaytsev]

In fact one can see this first hand as Red Hat backported the coretemp
module into RHEL-5.5 (kernel-2.6.18-194.el5), but *only* for non-xen
variants! I wasn't aware the differences between xen and non-xen
kernel variants were so wide reaching.

Well, maybe someone with an active support contract could talk to their
manager about this... who knows, maybe it's not so complicated to
backport after all, it's just that they need a little kick.

[Kai Schaetzl]

Thanks for the help and sorry for posting to the wrong list. I use so few
stuff from elrepo that I didn't recognize it's not rf.
I installed the version you mention and it's working fine, thanks!
Just before your posting I created a Mantis account on elrepo that I
probably won't need in the near future ;-) I noticed that there is
something wrong going on. My proxy told me there was no response after
submitting the filled form. Nevertheless, the account was created. You may
want to look into this.

Kai

[Yury V. Zaytsev]

In fact one can see this first hand as Red Hat backported the coretemp
module into RHEL-5.5 (kernel-2.6.18-194.el5), but *only* for non-xen
variants! I wasn't aware the differences between xen and non-xen
kernel variants were so wide reaching.

Well, maybe someone with an active support contract could talk to their
manager about this... who knows, maybe it's not so complicated to
backport after all, it's just that they need a little kick.

[Kai Schaetzl]

Thanks for the help and sorry for posting to the wrong list. I use so few
stuff from elrepo that I didn't recognize it's not rf.
I installed the version you mention and it's working fine, thanks!
Just before your posting I created a Mantis account on elrepo that I
probably won't need in the near future ;-) I noticed that there is
something wrong going on. My proxy told me there was no response after
submitting the filled form. Nevertheless, the account was created. You may
want to look into this.

Kai

[Kai Schaetzl]

I installed kmod-coretemp-xen-1.1-8.el5.elrepo.x86_64 on a machine with
two L5320 CPUs. Unfortunately, it can't get inserted. It throws an error

kernel: coretemp: Unknown symbol rdmsr_safe_on_cpu

The system is freshly setup with new OS. There was another CPU in the
system (normal X51something) before the L, but the coretemp module wasn't
installed on that 32bit system. So, I'm not sure if it would have worked
with that.
Is this maybe functionality not available on an L5-series CPU?
Can anyone compare if it works on his L5-series CPU?

Googling around it looks like lm-sensors might be the best location to
inquire further. Correct?

Kai

[Ned Slider]

Post by Kai Schaetzl
I installed kmod-coretemp-xen-1.1-8.el5.elrepo.x86_64 on a machine with
two L5320 CPUs. Unfortunately, it can't get inserted. It throws an error
kernel: coretemp: Unknown symbol rdmsr_safe_on_cpu
The system is freshly setup with new OS. There was another CPU in the
system (normal X51something) before the L, but the coretemp module wasn't
installed on that 32bit system. So, I'm not sure if it would have worked
with that.
Is this maybe functionality not available on an L5-series CPU?
Can anyone compare if it works on his L5-series CPU?
Googling around it looks like lm-sensors might be the best location to
inquire further. Correct?
Kai

Nope, that's an elrepo package and it's an elrepo issue. If you'd care
to file a bug here:

http://elrepo.org/bugs

I'll be more than happy to look at it for you.

Thanks.

[Ned Slider]

Post by Kai Schaetzl
I installed kmod-coretemp-xen-1.1-8.el5.elrepo.x86_64 on a machine with
two L5320 CPUs. Unfortunately, it can't get inserted. It throws an error
kernel: coretemp: Unknown symbol rdmsr_safe_on_cpu

Hi Kai,

I looked into this a little further and confirmed the bug.

Unfortunately, later versions of kmod-coretemp are not compatible with
xen kernels. In this instance it appears Red Hat have not backported
certain interfaces into the xen kernel variants which coretemp uses (but
have backported them to the regular (non-xen) kernel). In fact one can
see this first hand as Red Hat backported the coretemp module into
RHEL-5.5 (kernel-2.6.18-194.el5), but *only* for non-xen variants! I
wasn't aware the differences between xen and non-xen kernel variants
were so wide reaching.

With the absence of such interfaces it is becoming increasingly
difficult to continue to backport certain drivers to the xen kernel
platform, and as such we will probably just drop support for xen kernels
where that happens.

To this end I have removed kmod-coretemp-xen-1.1-8.el5.elrepo from the
repository (as it's clearly broken) and have confirmed that the latest
version to support the xen kernel is kmod-coretemp-xen-1.1-6.el5.elrepo.
If you uninstall your current version and reinstall, yum should now pull
in kmod-coretemp-xen-1.1-6.el5.elrepo that does support xen kernels. If
this version fails to support future CPU revisions then we might be able
to backport support for that but it will likely mean maintaining a
separate branch for xen kernels. As there is no native coretemp driver
in the xen kernel it's probably worthwhile, but I'd also be tempted to
file an RFE/patch upstream with Red Hat for native support in xen kernels.

I hope that helps.

[Kai Schaetzl]

I installed kmod-coretemp-xen-1.1-8.el5.elrepo.x86_64 on a machine with
two L5320 CPUs. Unfortunately, it can't get inserted. It throws an error

kernel: coretemp: Unknown symbol rdmsr_safe_on_cpu

The system is freshly setup with new OS. There was another CPU in the
system (normal X51something) before the L, but the coretemp module wasn't
installed on that 32bit system. So, I'm not sure if it would have worked
with that.
Is this maybe functionality not available on an L5-series CPU?
Can anyone compare if it works on his L5-series CPU?

Googling around it looks like lm-sensors might be the best location to
inquire further. Correct?

Kai

[Ned Slider]

Post by Kai Schaetzl
I installed kmod-coretemp-xen-1.1-8.el5.elrepo.x86_64 on a machine with
two L5320 CPUs. Unfortunately, it can't get inserted. It throws an error
kernel: coretemp: Unknown symbol rdmsr_safe_on_cpu
The system is freshly setup with new OS. There was another CPU in the
system (normal X51something) before the L, but the coretemp module wasn't
installed on that 32bit system. So, I'm not sure if it would have worked
with that.
Is this maybe functionality not available on an L5-series CPU?
Can anyone compare if it works on his L5-series CPU?
Googling around it looks like lm-sensors might be the best location to
inquire further. Correct?
Kai

Nope, that's an elrepo package and it's an elrepo issue. If you'd care
to file a bug here:

http://elrepo.org/bugs

I'll be more than happy to look at it for you.

Thanks.

[Ned Slider]

Post by Kai Schaetzl
I installed kmod-coretemp-xen-1.1-8.el5.elrepo.x86_64 on a machine with
two L5320 CPUs. Unfortunately, it can't get inserted. It throws an error
kernel: coretemp: Unknown symbol rdmsr_safe_on_cpu

Hi Kai,

I looked into this a little further and confirmed the bug.

Unfortunately, later versions of kmod-coretemp are not compatible with
xen kernels. In this instance it appears Red Hat have not backported
certain interfaces into the xen kernel variants which coretemp uses (but
have backported them to the regular (non-xen) kernel). In fact one can
see this first hand as Red Hat backported the coretemp module into
RHEL-5.5 (kernel-2.6.18-194.el5), but *only* for non-xen variants! I
wasn't aware the differences between xen and non-xen kernel variants
were so wide reaching.

With the absence of such interfaces it is becoming increasingly
difficult to continue to backport certain drivers to the xen kernel
platform, and as such we will probably just drop support for xen kernels
where that happens.

To this end I have removed kmod-coretemp-xen-1.1-8.el5.elrepo from the
repository (as it's clearly broken) and have confirmed that the latest
version to support the xen kernel is kmod-coretemp-xen-1.1-6.el5.elrepo.
If you uninstall your current version and reinstall, yum should now pull
in kmod-coretemp-xen-1.1-6.el5.elrepo that does support xen kernels. If
this version fails to support future CPU revisions then we might be able
to backport support for that but it will likely mean maintaining a
separate branch for xen kernels. As there is no native coretemp driver
in the xen kernel it's probably worthwhile, but I'd also be tempted to
file an RFE/patch upstream with Red Hat for native support in xen kernels.

I hope that helps.

[Kai Schaetzl]

I installed kmod-coretemp-xen-1.1-8.el5.elrepo.x86_64 on a machine with
two L5320 CPUs. Unfortunately, it can't get inserted. It throws an error

kernel: coretemp: Unknown symbol rdmsr_safe_on_cpu

The system is freshly setup with new OS. There was another CPU in the
system (normal X51something) before the L, but the coretemp module wasn't
installed on that 32bit system. So, I'm not sure if it would have worked
with that.
Is this maybe functionality not available on an L5-series CPU?
Can anyone compare if it works on his L5-series CPU?

Googling around it looks like lm-sensors might be the best location to
inquire further. Correct?

Kai

[Ned Slider]

Post by Kai Schaetzl
I installed kmod-coretemp-xen-1.1-8.el5.elrepo.x86_64 on a machine with
two L5320 CPUs. Unfortunately, it can't get inserted. It throws an error
kernel: coretemp: Unknown symbol rdmsr_safe_on_cpu
The system is freshly setup with new OS. There was another CPU in the
system (normal X51something) before the L, but the coretemp module wasn't
installed on that 32bit system. So, I'm not sure if it would have worked
with that.
Is this maybe functionality not available on an L5-series CPU?
Can anyone compare if it works on his L5-series CPU?
Googling around it looks like lm-sensors might be the best location to
inquire further. Correct?
Kai

Nope, that's an elrepo package and it's an elrepo issue. If you'd care
to file a bug here:

http://elrepo.org/bugs

I'll be more than happy to look at it for you.

Thanks.

[Ned Slider]

Post by Kai Schaetzl
I installed kmod-coretemp-xen-1.1-8.el5.elrepo.x86_64 on a machine with
two L5320 CPUs. Unfortunately, it can't get inserted. It throws an error
kernel: coretemp: Unknown symbol rdmsr_safe_on_cpu

Hi Kai,

I looked into this a little further and confirmed the bug.

Unfortunately, later versions of kmod-coretemp are not compatible with
xen kernels. In this instance it appears Red Hat have not backported
certain interfaces into the xen kernel variants which coretemp uses (but
have backported them to the regular (non-xen) kernel). In fact one can
see this first hand as Red Hat backported the coretemp module into
RHEL-5.5 (kernel-2.6.18-194.el5), but *only* for non-xen variants! I
wasn't aware the differences between xen and non-xen kernel variants
were so wide reaching.

With the absence of such interfaces it is becoming increasingly
difficult to continue to backport certain drivers to the xen kernel
platform, and as such we will probably just drop support for xen kernels
where that happens.

To this end I have removed kmod-coretemp-xen-1.1-8.el5.elrepo from the
repository (as it's clearly broken) and have confirmed that the latest
version to support the xen kernel is kmod-coretemp-xen-1.1-6.el5.elrepo.
If you uninstall your current version and reinstall, yum should now pull
in kmod-coretemp-xen-1.1-6.el5.elrepo that does support xen kernels. If
this version fails to support future CPU revisions then we might be able
to backport support for that but it will likely mean maintaining a
separate branch for xen kernels. As there is no native coretemp driver
in the xen kernel it's probably worthwhile, but I'd also be tempted to
file an RFE/patch upstream with Red Hat for native support in xen kernels.

I hope that helps.

[Kai Schaetzl]

I installed kmod-coretemp-xen-1.1-8.el5.elrepo.x86_64 on a machine with
two L5320 CPUs. Unfortunately, it can't get inserted. It throws an error

kernel: coretemp: Unknown symbol rdmsr_safe_on_cpu

The system is freshly setup with new OS. There was another CPU in the
system (normal X51something) before the L, but the coretemp module wasn't
installed on that 32bit system. So, I'm not sure if it would have worked
with that.
Is this maybe functionality not available on an L5-series CPU?
Can anyone compare if it works on his L5-series CPU?

Googling around it looks like lm-sensors might be the best location to
inquire further. Correct?

Kai

[Ned Slider]

Post by Kai Schaetzl
I installed kmod-coretemp-xen-1.1-8.el5.elrepo.x86_64 on a machine with
two L5320 CPUs. Unfortunately, it can't get inserted. It throws an error
kernel: coretemp: Unknown symbol rdmsr_safe_on_cpu
The system is freshly setup with new OS. There was another CPU in the
system (normal X51something) before the L, but the coretemp module wasn't
installed on that 32bit system. So, I'm not sure if it would have worked
with that.
Is this maybe functionality not available on an L5-series CPU?
Can anyone compare if it works on his L5-series CPU?
Googling around it looks like lm-sensors might be the best location to
inquire further. Correct?
Kai

Nope, that's an elrepo package and it's an elrepo issue. If you'd care
to file a bug here:

http://elrepo.org/bugs

I'll be more than happy to look at it for you.

Thanks.

[Ned Slider]

Post by Kai Schaetzl
I installed kmod-coretemp-xen-1.1-8.el5.elrepo.x86_64 on a machine with
two L5320 CPUs. Unfortunately, it can't get inserted. It throws an error
kernel: coretemp: Unknown symbol rdmsr_safe_on_cpu

Hi Kai,

I looked into this a little further and confirmed the bug.

Unfortunately, later versions of kmod-coretemp are not compatible with
xen kernels. In this instance it appears Red Hat have not backported
certain interfaces into the xen kernel variants which coretemp uses (but
have backported them to the regular (non-xen) kernel). In fact one can
see this first hand as Red Hat backported the coretemp module into
RHEL-5.5 (kernel-2.6.18-194.el5), but *only* for non-xen variants! I
wasn't aware the differences between xen and non-xen kernel variants
were so wide reaching.

With the absence of such interfaces it is becoming increasingly
difficult to continue to backport certain drivers to the xen kernel
platform, and as such we will probably just drop support for xen kernels
where that happens.

To this end I have removed kmod-coretemp-xen-1.1-8.el5.elrepo from the
repository (as it's clearly broken) and have confirmed that the latest
version to support the xen kernel is kmod-coretemp-xen-1.1-6.el5.elrepo.
If you uninstall your current version and reinstall, yum should now pull
in kmod-coretemp-xen-1.1-6.el5.elrepo that does support xen kernels. If
this version fails to support future CPU revisions then we might be able
to backport support for that but it will likely mean maintaining a
separate branch for xen kernels. As there is no native coretemp driver
in the xen kernel it's probably worthwhile, but I'd also be tempted to
file an RFE/patch upstream with Red Hat for native support in xen kernels.

I hope that helps.