@savage79 said in How to get know a temperature of MxGPU?: I tested only with xcp-ng-8.1.0-2.iso which is based on centos8 Not exact. XCP-ng 8.1 is based on CentOS 7.5 (well 2/3 of it is, the rest is custom).

We are aware of it Our "bandwidth" right now is not enough to investigate further. edit: it's more a generic library than a real product, so it's nice but that would require a reasonable amount of work to turn it into something "turnkey". However, we are definitely keeping an eye on it

Hi @Andy76 Please open a support ticket, it's within our XCP-ng Enterprise support package

oVirt is the same concept, the only diff is maybe a REST API, but otherwise it's really similar (but even a bit harder to setup). Anyway, if you need assistance on API calls, let us know.

@stormi It does. I put the screen shots of what it looks like when you run it in the pull request.

@hani sounds great, keep us posted on your progress and findings!

It's not a trick, it's a way to do it with the CLI

Short answer is that the module is referring to wrong symbol table. Its a lookup table for function interaction between module and kernel. Easy answer is to use this .config file and build full kernel.

If I understand correctly, the "ISO" you are asking for is for building drivers. I don't intend on creating a specific ISO just for that. Everything is available in yum repositories to build drivers (usually you just need make, gcc and kernel-devel), and there's also a docker image at https://github.com/xcp-ng/xcp-ng-build-env I do prefer Olivier's suggestion, though: going through support, because drivers built for one user through support are made available to other users through our repositories.

@r1 the way the rook-ceph works that you pass raw disk to the Debian host and then it creates the OSD and cluster, I have few issues with this: Adding and removing k8s nodes is just few commands and very quick and zero downtime for apps, but if I am running rook-ceph, I need to rebuild the cluster every time I do that and thats extremely time consuming and extra over head. The size of each VM that is being backed up daily/weekly is also extremely big and consumes a lot of resources and storage space. Instead if you get a xcp-ng native local cluster that can be used by VM's as local block type SR that would simplify the implementation many times.

@imtrobin No, AMD. Currently a WX4100 (as its LP and fits into a 2U server) but have also had a RX580 working before.

What do you mean?

@stormi enabled=0, didn't see it! thanks

2020 https://fosdem.org/2020/schedule/event/inmcofasmd/

@fibrewire If you're looking at a free way to do so, you can install XOA from the sources and do it through that. I honestly don't miss the updates portion of XCP-ng Center (even after having used it for years in XenCenter). It was very clunky and time-consuming; and, I ultimately ended up scripting a lot of it locally on hosts instead. This is obviously much easier now that it can be done through a simple "yum" command instead of having to pull all the separate packages and install them like XenServer does. XOA will obviously provide that feature through the paid versions as well (if you've already got it). I'm not big on pushing people to XOA from XCP-ng Center, as I still use XCP-ng Center way more than XOA (at least until they push out the new version with the tree view so I can give it a try); but, that's the easy answer to your question.

Hi. Unfortunately, there's no other way than booting from an ISO to install XCP-ng. You can't convert an CentOS into XCP-ng. The disk layout would not be good, and actually "our" OS runs as a Xen domain.

You don't need a link. You can simply attach the guest-tools.iso, already present and known by XCP-ng, to the VM and mount it.

XCP-ng includes Xen as a core component but it's probably not the only component that is involved. I can't answer to the question about "how much" it differs from someone using Xen directly. Someone would need to investigate that.

Great! thanks

CH 8.1 has the same kernel than 8.0. So by default, will have the same too.