@julien-f Thank you very much I've updated to the latest commit and can confirm the behaviour has stopped, the prompt fix is much appreciated.

@AtaxyaNetwork Well I feel quite silly now thank you for showing me the easy way rather than the hard way I did it!

All,

Managed to figure this out but had to configure this in the command line:

Found an old XCP-NG blog entry for it I've included a snippet below (put the necessary command in bold) but the full URL is:

https://xcp-ng.org/blog/2022/09/13/network-bonds-in-xcp-ng/

️ Creating a new management interface on your bond via CLI
Note that if you have lost your management interface or similar (and that's why you're stuck using the CLI), you can now configure a management interface on top of this new bond manually. First, find the UUID of your bond by running xe pif-list - you're looking for the entry named bond0, and it should have a vlan value of -1- (which means no vlan). For instance, on my machine:

uuid ( RO) : f7baee9b-67b5-860f-8bad-69f39088d4a4
device ( RO): bond0
currently-attached ( RO): true
VLAN ( RO): -1
network-uuid ( RO): 6e93da18-f159-4801-f67a-eccb78cc0b62
We want to use that top UUID in the following command along with your own network information you'd like to assign to this host:

xe pif-reconfigure-ip uuid=f7baee9b-67b5-860f-8bad-69f39088d4a4 netmask=255.255.255.0 gateway=192.168.1.1 IP=192.168.1.5 mode=static
Now we just need to tell XCP-ng to use this interface as the management interface (use the same top UUID from before):

xe host-management-reconfigure pif-uuid=f7baee9b-67b5-860f-8bad-69f39088d4a4
That's it! Assuming LACP is properly configured on the switch side, you should now be able to access the host via the IP you assigned.

@DustinB Hi Dustin,

Thanks for the help so far but I cant see a location to set this information at the pool level, hence why I was looking at the network level:

Screenshot of config

@DustinB Added at the pool level, I dont have multiple hosts in one pool yet.

@AtaxyaNetwork Hi there,

I haven't added an IP didn't know that was needed. This is what the current config looks like:

I checked at the pool level as well and couldn't see a way to add it, is this something I need to add via the command line?

I recently added a new NIC to one of my hosts (the pool master) to use for backups exclusively (over a nice 10gb link) I have successfully created the bond and can see it but I'm unable to set it as the dedicated backup network on my pool, I can only set the original bonded network I created which also doubles as the management network?

Can someone help guide me here as I feel like I might just be missing a setting etc.

Thanks in advance.

@dinhngtu Thanks for confirming I'll turn that on, if I have any issues I'll report back!

@dinhngtu Can you confirm if you mean the the Citrix Drivers option in advanced on the VM? If not then no as I wasn't sure if that option was for the XenServer drivers and not the official Citrix Drivers?

Hi Guys,

Noticed the Xeniface error and started mitigating, noticed some of our VM's had updated from Windows update to get the newest XenServer VM Drivers.

But the problem is XOA Isn't picking up that these drivers are running?

Still getting this error:

I ran the mitigation script (scan) and noticed that it wasn't mitigated.

Not sure how to proceed here as I cant re run the installer as the drivers are already in place? Is best course of action to fully uninstall then reinstall.

@Bastien-Nollet Thank you for your help, purging the config then readding it seemed to fix the problem, appreciate the support.