There is a lot of good descriptions how to set it up, however – as Pi-diet does not use classic sshd but `dropbear` `pvecm qdevice setup` does not work:
# pvecm qdevice setup 192.168.1.202 -f
/bin/ssh-copy-id: INFO: Source of key(s) A toolset to gather temperature and power consumption metrics then collect in Prometheus. Can be found on GitHub https://github.com/jaroslawhartman/proxmox-monitoring/tree/main
Collecting script is running every minute on the pve host
* * * * * As stated in Proxmox Doc, you can create a custom Cloud-Init config where you’re free to set all parameters you need in a snippet yaml file, then generate a Cloud-Init custom image
This file is static
Found this at opportunity of installing Home Assistant – from HA OS qemu2 image – boot process just stops into UEFI Shell prompt:
BLK0: Alias (s):…
PciRoot (0x0) /Pci (0x1E,0x0) /Pci (0x1,0x0)/Pci (0x5,0x0) /Scsi (0x0,0x0)
BLK2: Alias (s):
PciRoot (Ox0)
Since a few weeks, my Proxmox lab has started having issues with on-board network. The adapter enters in “hang” state, the logs are full of recurring errors like below:
[89276.274556] e1000e 0000:00:1f.6 enp0s31f6: Reset adapter unexpectedly [89276.306147] vmbr0: port 1(enp0s31f6)…