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!

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!

@dinhngtu said in XCP-ng Windows PV tools 9.0.9030 Testsign released: now with Rust-based Xen Guest Agent:

9.0.9000.0, we're interested in hearing about your upgrade experience to 9.0.9030

I tested the new tools today on a fresh Windows Server 2022 VM.

Coming from 9.0.9000.0 I was given an error message that warned of incompatible drivers already installed and I had to run the XenClean utility first, then reboot and finally install 9.0.9030. Everything went smoothly.

The only thing I would expect differently is a menu entry in the Start Menu that links to the tools installed and repairing or removing them, I guess.

After that I ran some benchmark out of curiosity. The VM storage is on a XFS NVMe. Somehow it seems I used to get better performance with the 9.0.9000.0 version.

XCP-ng Tools v9.0.9000.0 aka

XCP-ng Tools v9.0.9030

Citrix Guest Tools v9.4.0

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

Hello!

I'm working with the community.general.xen_orchestra dynamic inventory plugin and trying to implement group-specific variables through the tagging function.

For instance, here's an example of a static inventory I currently have. Nothing fancy.

gp1:
  vars:
    ansible_user: admin
  hosts:
    server1.example.com:
    server2.example.com:
gp2:
  vars:
    ansible_user: anotheradmin
  hosts:
    server3.example.com:
    server4.example.com:

The following dynamic inventory configuration works fine:

plugin: community.general.xen_orchestra
api_host: xo.example.com
user: admin
password: mypass
validate_certs: true
use_ssl: true
groups:
    gp1: "'gp1' in tags"
    gp2: "'gp2' in tags"

But adding group vars breaks it:

[...]
groups:
    gp1: "'gp1' in tags"
        vars:
            ansible_user: admin
    gp2: "'gp2' in tags"
        vars:
            ansible_user: anotheradmin

I'm wondering if the plugin supports adding group-specific variables directly in the dynamic inventory configuration.

Would appreciate hearing if anyone has made this work and the most elegant and supported solution. I looked extensively through the forum, blog posts, etc. and could not figure it out.

Thanks in advance for your help!

@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.