lm_sensor support

[dkwan]

I have been testing ESX4, so far I found it is somewhat similar to RHEL5 (2.6.18-128.ESX). It comes with rpm tool as well as lm_sensors. However it doesn't seems to have the latest full range support for all sensors like in kernel 2.6.29.1-102...

I have not not deal with loading modules for a while and my Linux skill is getting rusty... In theory I think I should be able to use modprobe -f to load the module that support my chipset for lm_sensor to works.

e.g. dmesg: hwmon: version magic '2.6.29.1-102.fc11.x86_64 SMP mod_unload ' should be '2.6.18-128.ESX mod_unload gcc-4.1'

But just wondering if VMWare has any plans to 'update' the kernel to include other modules in kernel/drives/hwmon or any guru can tell me how (or if possible) to load modules from a similar kernel into ESX4...

[AndreTheGiant]

Do not use Linux modules inside the Service Console.

Remember that ESX is not Linux (the RHEL part is just a Service Console).

ESX has an internal sensors monitor tools based on CIM (and you can see it in Healt Status).

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

[dkwan]

Yes, I have heard the common "ESX != Linux" many times but yet there are some useful stuff, namely lm_sensor, that's included and just need a bit of tweak and it will work.

And yes, I also aware there are some sort of internal sensors monitor tools based on CMI and trust me, I have spend the past few days, read the docs and tried them. The problems is ESX only giving a OK status but not the temp or fan RPM on my test box. And yes, I know there is a list of 'compatible/certified servers' and what I have isn't on the list.

Knowing it is just a matter of loading a module will be able to have "sensors" running it seems to be the only gap to what I needed. Perhaps VMWare can consider to include hwmon modules in the next release that I am sure will be a welcoming feature. And may can enjoy monitoring their whitebox ESX/ESXi server....

[AndreTheGiant]

The problems is ESX only giving a OK status but not the temp or fan RPM on my test box. And yes, I know there is a list of 'compatible/certified servers' and what I have isn't on the list.

Ok, if is not a production environment you could to some tests :smileyhappy:

Get the binary package for RHEL5.1 and try to install.

Or you must start from source files, but you will need also gcc and devel tools on the ESX.

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

[dkwan]

Well the problem is not matter of install the "sensors" RPM package, in fact what comes with ESX4 is already the latest version of "Sensors" (Same version as Sensors RPM that comes with RHEL5.1) I think it either needs to find a way to load a kernel module by forcing to skip the version check (but still runs into unreferenced parameters) or try to compile the kernel module on a similar version of Linux kernel and see if it will load. Note: I don't think we can get the "same" version of Linux kernel build, because I think VMWare has made some chances to the original kernel code.

[Rumple]

The other thing to realize is that the service console is just another virtual machine and in reality doesn't actually have any more access to the physical hardware then just loading up a VM with RH5 and trying to monitor with the tools. The service console is really just a management interface that talks to the kernel for scheduling, management,etc, but not the hardware directly.

[AndreTheGiant]

To find and load lm_sensors kernel modules the command is sensors-detect.

But for me doesn't find any module.

I think the Service Console, due to the virtual environment (since ESX 4 it's also base on vmdk disks), is not able to access to this infos.

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

[Texiwill]

Hello,

The vmkernel would have to expose to the Management vAppliance (service console) the lm_sensor data. It does not due this and while you can certainly install the sensors within the VM, it may only be limited to seeing exactly what the VM sees. Which may just include CPU information and not chassis information.

Best regards, Edward L. Haletky VMware Communities User Moderator, VMware vExpert 2009
Now Available on Rough-Cuts: 'VMware vSphere(TM) and Virtual Infrastructure Security: Securing ESX and the Virtual Environment'[/url]
Also available 'VMWare ESX Server in the Enterprise'[/url]
[url=http://www.astroarch.com/wiki/index.php/Blog_Roll]SearchVMware Pro[/url]|Blue Gears[/url]|Top Virtualization Security Links[/url]|Virtualization Security Round Table Podcast[/url]