Temps seem to be working on i5-10500T:

[11:46 delta-2 ~]# xenpm get-core-temp
Package0: 57°C
CPU0: 56°C
CPU2: 57°C
CPU4: 56°C
CPU6: 56°C
CPU8: 55°C
CPU10: 57°C

As this is my first time installing these update candidates, is there no other action required after doing:

yum clean metadata --enablerepo=xcp-ng-testing,xcp-ng-candidates
yum update --enablerepo=xcp-ng-testing,xcp-ng-candidates
reboot

Meaning I am not permanently in testing mode now? Next yum update should just pull the latest stable versions?

@rzr @stormi Perfect, thanks for clarifying!

Temps seem to be working on i5-10500T:

[11:46 delta-2 ~]# xenpm get-core-temp
Package0: 57°C
CPU0: 56°C
CPU2: 57°C
CPU4: 56°C
CPU6: 56°C
CPU8: 55°C
CPU10: 57°C

As this is my first time installing these update candidates, is there no other action required after doing:

yum clean metadata --enablerepo=xcp-ng-testing,xcp-ng-candidates
yum update --enablerepo=xcp-ng-testing,xcp-ng-candidates
reboot

Meaning I am not permanently in testing mode now? Next yum update should just pull the latest stable versions?

Yay! Santa came early this year!!

Is this possible now? I can only see the management NIC.

Related: https://xcp-ng.org/forum/topic/9160/xen-orchestra-prometheus-backup-metrics/10

I was about to link Mike's work here, but wanted to say how we desperately need a metrics system that would be exposed from a centralized location. There's no way in hell I'm giving a docker host credential access to the hypervisor it resides on (and all the other hypervisors) - on the other hand, if the metrics were exposed only via XO and limited in terms of where these metrics could be accessed from, now that would be a sold implementation.

Hey, since I'm running TrueNAS virtualized, I wanted to passthrough the SATA controller.

This led me to a journey of updating to 8.3, just so I could do it through xen orchestra, which I did. After I toggled the controller, the system restarted and all of a sudden xcp-ng didn't want to boot. It was stuck in the dracut emergency shell.

I had absolutely no idea why, until I realized the system itself is on a SATA SSD, and not an m.2 drive.

I had to manually change the grub config for it to be able to boot to the main config again, which was a bit stressful.

Anyways, my idea, just adding a little popup warning, or something similar that this could happen if users have xcp-ng installed on a SATA drive, just to prevent future headaches for homelabbers such as myself, but in reality, it could happen to anyone.

Good things take time.
Your team is doing god's work.
Remember to stay healthy, in both mind and body!

Got it, thanks!
I'm certain many if not all enterprise users would be interested in such a feature.

@olivierlambert That's where my question comes in

Any plans on having these exposed for monitoring in Grafana?