@florent I also ran into this. It seems to be working on Dell hosts, but on my supermicro hosts I get nothing even though I do get data back from the cli plugin

[09:15 host01 ~]# xe host-call-plugin host-uuid=aa8e6bf4-6710-4320-98f9-d8e581cf8ef7  plugin=ipmitool.py fn=is_ipmi_device_available
true
[09:16 host01 ~]# xe host-call-plugin host-uuid=aa8e6bf4-6710-4320-98f9-d8e581cf8ef7  plugin=ipmitool.py fn=get_all_sensors
[{"name": "CPU Temp", "value": "59 degrees C", "event": "ok"}, {"name": "Inlet Temp", "value": "no reading", "event": "ns"}, {"name": "PCH Temp", "value": "43 degrees C", "event": "ok"}, {"name": "System Temp", "value": "23 degrees C", "event": "ok"}, {"name": "Peripheral Temp", "value": "30 degrees C", "event": "ok"}, {"name": "CPU_VRMON Temp", "value": "39 degrees C", "event": "ok"}, {"name": "M2_SSD1 Temp", "value": "38 degrees C", "event": "ok"}, {"name": "M2_SSD2 Temp", "value": "40 degrees C", "event": "ok"}, {"name": "DIMMAB Temp", "value": "30 degrees C", "event": "ok"}, {"name": "FAN1", "value": "16240 RPM", "event": "ok"}, {"name": "FAN2", "value": "16800 RPM", "event": "ok"}, {"name": "FAN3", "value": "16380 RPM", "event": "ok"}, {"name": "FAN4", "value": "no reading", "event": "ns"}, {"name": "FAN5", "value": "no reading", "event": "ns"}, {"name": "FANA", "value": "10080 RPM", "event": "ok"}, {"name": "FANB", "value": "no reading", "event": "ns"}, {"name": "MB 12V", "value": "11.92 Volts", "event": "ok"}, {"name": "MB 5VCC", "value": "5.10 Volts", "event": "ok"}, {"name": "MB 3.3VCC", "value": "3.34 Volts", "event": "ok"}, {"name": "VBAT", "value": "0x04", "event": "ok"}, {"name": "MB 5VSB", "value": "5.06 Volts", "event": "ok"}, {"name": "MB 3.3VSB", "value": "3.34 Volts", "event": "ok"}, {"name": "PCH 1.8V", "value": "1.82 Volts", "event": "ok"}, {"name": "CPU 1.8V_AUX", "value": "1.79 Volts", "event": "ok"}, {"name": "PCH 1.05V", "value": "1.05 Volts", "event": "ok"}, {"name": "BMC 2.5V", "value": "2.50 Volts", "event": "ok"}, {"name": "BMC 1.8V", "value": "1.81 Volts", "event": "ok"}, {"name": "CPU 1.1V_DDR", "value": "1.11 Volts", "event": "ok"}, {"name": "CPU Core", "value": "1.34 Volts", "event": "ok"}, {"name": "BMC 3.3VSB", "value": "3.34 Volts", "event": "ok"}, {"name": "CPU 1.05V", "value": "1.05 Volts", "event": "ok"}, {"name": "CPU 1.8V", "value": "1.82 Volts", "event": "ok"}, {"name": "Chassis Intru", "value": "0x00", "event": "ok"}, {"name": "PS1 Status", "value": "0x01", "event": "ok"}, {"name": "AOC_NIC1 Temp", "value": "63 degrees C", "event": "ok"}, {"name": "PS2 Status", "value": "0x01", "event": "ok"}]

I saw on the webpage that "Legacy plans (XOA Standalone) will be removed in the future."

We have been a happy Xen Orchestra Enterprise customer. Can you comment on when this change will happen? When it does we will have to discontinue our Xen Orchestra enterprise use so we'll need some time to plan ahead.

Also note we receive this error:
✖ unknown error from the peer

I am running into an issue registering an instance of XO running on a Hyper-V system. Our central datacenter where we want to run XO is Hyper-V, but we want to use it to manage distributed compute that will be based on XCP-NG.

I suspect the issue is that XO can see its not running on Xen and fails the check:
✖ Fetching VM UUID: Error: Command failed: xenstore-read vm
xenstore.Open error: Cannot locate xenbus dev path in [/proc/xen/xenbus /dev/xen/xenbus /kern/xen/xenbus]

Will it be possible to run in this configuration? Changing the hypervisor in our datacenter is not likely feasible at this time, but we still want to leverage XO.

Thanks