You should have a command available in your Debian VM with tools, called "xenstore". You can use xenstore-write.

For example:

xenstore-write vm-data/gputemp 82

This will write the value 82 in a key gputemp. This key/value can be seen in the VM object then, eg with a :

xe vm-param-get param-name=xenstore-data param-key=vm-data/gputemp uuid=<VM UUID>

This will return 82. Now you can do whatever script in your Dom0 (or even from your XOA, since you can fetch all data in XAPI)

As you can see, it's very simple and efficient 🙂

I just added a P4 to one of my hosts for exactly this. My servers can only handle low-profile cards, so the P4 fits. Not the most powerful of GPU's but I can get my feet wet.

@wilsonqanda Using HA adds more complexity (to XCP-ng and front-/backend systems). Your use case should really require HA to justify that complexity, especially if you add geo-replication to the mix. Most scenarios can probably be addressed with incremental replication for a low recovery point objectiv (RPO) and a good recovery time objective (RTO), but your mileage my vary.

@gskger You're here. You know the answer. Put in some more memory and a 2TB NVMe and run XCP! See what you can do with it. Dedicate an outside and inside interface and have a DMZ for guest net and more.

I have a system like this (a little faster i7 CPU, 64G, 2x2TB NVMe, 2T SATA) and I run lots of stuff on it including: BT server, asterisk, DNS server, NTP server, XO, Win10, test VMs, ZM for cameras, and more. I turned off a whole bunch of old hardware.

It's 100% fine 🙂 The community forum is the best place to report about your tinkering with the platform!

Happy New Year!

Should be merged soon:
https://github.com/vatesfr/xen-orchestra/pull/6517/files

Thanks @MathieuRA 🙂

MathieuRA opened this pull request in vatesfr/xen-orchestra closed fix(xo-web): "Pro Support" instead of "pool support" in XCP-ng support tooltips #6517

Thank you @gskger

Happy new year to you and everyone in this great community!

I'm not against exposing this in the UI, it might be not that difficult. However, more traction will obviously make it possible 🙂

Having XO from source or XOA act as a certification authority for the XCP-ng hosts is for sure a good approach. Would be great if that could include the VMs running on the XCP-ng hosts, which is my main goal (apart from being able to HTTPS into XO from source of course).