It's not the main "problem", and yes, XCP-ng 9.0 will use a far more recent kernel 
It's also a question of vendor partnership and so on. But as I said, we are working on it 
Vates Tech Support
Operators from our Vates Pro Support
Posts
-
RE: vGPU options for current XCP-ng?
-
RE: Native Ceph RBD SM driver for XCP-ng
There's some nice progress on @psafont's work regarding improved revert. I'm confident we'll get there
-
RE: vGPU options for current XCP-ng?
Pretty much I'm afraid. That's why we are investigating things on our end.
-
RE: Is supermicro IPMI data display planned?
But but nothing with the current XAPI plugin, so that might need to modify it.
-
RE: Is supermicro IPMI data display planned?
Yes, sorry I have the BMC IP, but not inlet nor outlet temp, I will check why you don't have total power.
edit: in the sensor data you sent, I don't have any total power available
-
RE: Is supermicro IPMI data display planned?
I'm afraid those data aren't complete enough for SuperMicro: I have no BMC info (no IP address), no inlet or outlet temp. It's probably because it's not a full chassis but just info from the motherboard?
-
RE: Is supermicro IPMI data display planned?
For Supermicro, you can use the following branch
olt-supermicro-ipmiand tell me if you have anything displayed in the host view. -
RE: Is supermicro IPMI data display planned?
You can provide:
xe host-call-plugin host-uuid=<uuid> plugin=ipmitool.py fn=is_ipmi_device_availableThen if yes:
xe host-call-plugin host-uuid=<uuid> plugin=ipmitool.py fn=get_all_sensorsAnd paste the result here, with a markdown code block syntax please
