Many thanks @nathanael-h & @shinuza , both approaches indeed work!

@McHenry said in Zabbix on xcp-ng:

Based upon the information below is appears xcp-ng is compatible with Centos/RHEL/Fedora however I am unsure of which OS version to select. I am running xcp-ng 8.3

The dom0 is running CentOS 7.

Hi @dinhngtu ,

Yes, I installed the PV drivers. I made sure everything was selected in the list of functions offered by the installer.
IPv4 address reported correctly

I did some additional test, this time starting from a test VM that had the XenServer tools installed.

0. Started a test VM with the Xenserver tools installed (version correctly reported in XO as Management agent 9.4.0-146 detected)
1. Ran Xenclean
2. Had to do another reboot to disable the "Manage Citrix PV drivers via Windows Update"
3. VM got a blue screen
4. Rebooted again and hit "Continue" after getting the "Windows repair" screen. VM booted successfully
5. Had to run XenClean again as some driver still seem to be present
6. Then finally I could install v9.0.9030
7. The IP is correct. Not sure about the tools version but it seems it's not?

Before XenClean

Step 5

Step 6

v9.0.9030 reporting in XO

v9.0.9030 reporting in XO

Another benchmark with v9.0.9030

I ran another benchmark and it seems you are right re. the variance. The host I test on is not an idle host, although the load is low - could that be the reason?

Other suggestions:
You could add a check that the testsign script is run from 64-bit Powershell version. If run from the 32-bit Powershell the following error will occur: The term 'bcdedit.exe' is not recognized as the name of a cmdlet.
It is easy to run the 32-bit version by accident because it is usually the first one that comes up in the Windows menu search results.

Hope this helps!