Share your Proxmox VE host's temperatures with its Linux virtual machines.
Virtual machines usually cannot read the physical computer's CPU temperature.
hwmon-virt makes selected host temperature sensors available inside the VM,
where tools such as sensors and Resources can display them.
You can share CPU, GPU, or other temperature sensors that Linux can read on the host. The readings describe the physical hardware shared by your VMs.
Proxmox VE is the supported deployment target. The host installation and removal scripts use Proxmox's VM management tools.
Resources inside a Proxmox VM, before and after setup:
| Before: temperature unavailable | After: temperature and history visible |
|---|---|
![]() |
![]() |
- A Proxmox VE host and a Linux guest.
- Administrator access to both machines.
- Python 3.9 or newer and systemd on both machines.
- curl and tar on both machines.
lm-sensors(Debian/Ubuntu) orlm_sensors(Fedora/RHEL) in the guest for thesensorscommand.- DKMS, a C compiler, make, and matching kernel development files in the guest.
- A working temperature sensor on the host.
The installers check dependencies but do not install missing system packages. See tested configurations for compatibility details.
The host is the physical computer running Proxmox. The guest is the virtual machine where you want to see temperatures. These examples use VM 101; replace it with your VM's ID.
On the Proxmox host, run as root:
cd ~
curl -fL -o hwmon-virt-0.1.0.tar.gz \
https://github.com/wmeddie/hwmon-virt/releases/download/v0.1.0/hwmon-virt-0.1.0.tar.gz
tar -xzf hwmon-virt-0.1.0.tar.gz
cd hwmon-virt-0.1.0The release page includes source archives and SHA-256 checksums. The guest installer builds the driver for your running kernel.
Continue with the host setup from that directory.
List the available temperature sensors:
python3 hwmon_virt.py listChoose the sensor you want to share and pass its name to the installer. For
example, if the list includes coretemp:Package id 0:
./install-host.sh --vmid 101 --sensor 'coretemp:Package id 0'This configures temperature sharing for the selected VM and starts the host service. To share more than one sensor, see additional sensors.
Open a terminal inside the Linux guest VM and install the prerequisites for your distribution. Building the driver needs headers and build files matching the running guest kernel; you do not need to download the full kernel source.
Debian / Ubuntu:
sudo apt update
sudo apt install build-essential dkms "linux-headers-$(uname -r)" \
python3 curl tar kmod lm-sensorsFedora / RHEL family:
On RHEL, Rocky Linux, or AlmaLinux 9/10, first enable EPEL and its required CRB/CodeReady Builder repository using the EPEL setup instructions for your distribution. EPEL supplies DKMS on these systems. Fedora includes DKMS in its standard repositories and does not need this step.
sudo dnf install gcc make dkms "kernel-devel-$(uname -r)" \
elfutils-libelf-devel python3 curl tar kmod lm_sensorsOn Fedora/RHEL, kernel-devel supplies the files needed to build the driver;
kernel-headers alone is not enough.
If the matching linux-headers or kernel-devel package is unavailable, update
the guest kernel through your distribution, reboot into it, and rerun the
prerequisite commands. For a custom kernel, obtain matching development files
from its provider.
Then download and install the release in the guest:
cd ~
curl -fL -o hwmon-virt-0.1.0.tar.gz \
https://github.com/wmeddie/hwmon-virt/releases/download/v0.1.0/hwmon-virt-0.1.0.tar.gz
tar -xzf hwmon-virt-0.1.0.tar.gz
cd hwmon-virt-0.1.0
sudo ./install-guest.shThis installs the guest driver and service. You can add --dry-run to either
installer to preview its changes. Guests using Secure Boot may need to enroll
a module-signing key through their distribution's DKMS setup.
The new connection becomes available after a full VM stop/start. Run these on the Proxmox host; shutting down will disconnect sessions in the guest:
qm shutdown 101 --timeout 120
qm status 101 # wait until the VM is stopped before continuing
qm start 101A reboot from inside the guest does not activate the new connection.
In the guest, run:
/usr/bin/sensorsLook for a temperature labeled Host CPU. Open your monitoring application to
check its display. If Resources was already open and still shows N/A, restart it.
Download and extract the new release on both machines using the download commands above. Run the following commands from the newly extracted directory. Installed configuration is kept separately from the downloaded files.
On the host, rerun the installer without --sensor to keep your existing
sensor selection:
./install-host.sh --vmid 101In the guest:
sudo ./install-guest.shAfter installation succeeds, load the updated guest driver:
sudo systemctl stop hwmon-virt-guest &&
sudo modprobe -r hwmon_virt &&
sudo systemctl start hwmon-virt-guestA guest reboot is an alternative to these three commands. If unloading reports that the module is in use, start the service again and reboot the guest when convenient.
An upgrade with an existing connection does not require a Proxmox host reboot or a VM stop/start. Temperature readings are briefly unavailable during the update.
In the guest, preview removal, then run it:
sudo ./uninstall-guest.sh --dry-run
sudo ./uninstall-guest.shOn the host, remove sharing for your VM:
./uninstall-host.sh --vmid 101 --dry-run
./uninstall-host.sh --vmid 101Configuration is kept for reinstallation. Add --purge to remove it too.
The host script leaves other VMs alone and never stops or starts a VM.
A full VM stop/start removes the disconnected channel; use --keep-channel
if you plan to reinstall and want to keep that connection available.
See uninstall details for what is removed and how to handle errors.
If the guest has no temperature reading, check its service:
systemctl status hwmon-virt-guest
journalctl -u hwmon-virt-guest -n 50On the host, check the service for your VM:
systemctl status hwmon-virt-host@101
journalctl -u hwmon-virt-host@101 -n 50If sensors shows the temperature but a monitoring app does not, restart the
app. Applications differ in how they choose a CPU sensor; see
monitoring application compatibility.
See the manual for additional troubleshooting.
- Manual installation and configuration
- Building, testing, and compatibility
- How it works
- Contributing
- Changelog
GNU General Public License version 2 only (GPL-2.0-only). See LICENSE and COPYING.

