CPU Thermal Sensor Info

[NollipfSense]

How does one get the Intel CPU thermal sensor info to pfSense from Proxmox? No system-sensor.rrd

[NollipfSense]

I had been running qemu agent on pfSense hoping to create synergy of information sharing, but it appears the CPU's thermal sensor info isn't considered important enough, or no one senior in the forum saw my post to share know how...

[provels]

In a virtual environment, wouldn't you be monitoring the host instead? I don't think it's available on a VM in Hyper-V either.

[NollipfSense]

@provels said in CPU Thermal Sensor Info:

In a virtual environment, wouldn't you be monitoring the host instead? I

Yes; however, this is a virtual environment where pfSense is made the boss and this boss can easily display that info, especially if the host doesn't easily render that info at a glance as pfSense does.

[viragomann]

@NollipfSense
The boss in a virtual environment is the host running the hypervisor, even if others do the whole job.
This seems similar to my company.

I cannot think of any possibility for a VM to get sensor data by directly accessing the hardware. And this is, what the sensor tool in pfSense does.

I've scripted a sensor request with mail alarm for my Proxmox server, to inform me if any is out of the normal range.

[NollipfSense]

@viragomann When I had setup mine, someone on Proxmox forum had given me a script that basically passthrough all input/output; so, I thought adding the qemu-agent would have help. Since then, apart from WAN and LAN, I have passedthrough one USB for Nut. Tried audio but still cannot get the pfSense boot up, shutdown, and login sound. (I like the novelty).

@viragomann said in CPU Thermal Sensor Info:

I've scripted a sensor request with mail alarm for my Proxmox server, to inform me if any is out of the normal range.

This is a potential work around; however, if a qemu-agent package makes it officially to pfSense package namagement, then maybe this thermal sensor info could be consider sharing with pfSense.

[viragomann]

@NollipfSense
I don't think that the qemu-agent is capable of doing this.
Quoted from the Proxmox wiki:

The qemu-guest-agent is a helper daemon, which is installed in the guest. It is used to exchange information between the host and guest, and to execute command in the guest.

In Proxmox VE, the qemu-guest-agent is used for mainly two things:

1. To properly shutdown the guest, instead of relying on ACPI commands or windows policies
2. To freeze the guest file system when making a backup (on windows, use the volume shadow copy service VSS).

Sensor reading need direct hardware access and for my understanding this is not given.

[Patch]

@NollipfSense said in CPU Thermal Sensor Info:

someone on Proxmox forum

I think this is a Proxmox limitation
There is a bugzilla entry to fix it from 2012 https://bugzilla.proxmox.com/show_bug.cgi?id=208
And a thread with 48,000 reads since 2020 https://forum.proxmox.com/threads/temperature.67755/

[NollipfSense]

@viragomann said in CPU Thermal Sensor Info:

Sensor reading need direct hardware access and for my understanding this is not given.

Thank you for sharing.

@Patch said in CPU Thermal Sensor Info:

I think this is a Proxmox limitation

Wow, I am not alone seeking this vital info...thank you Patch!