@olivierlambert Thanks, I have tried using xe-reset-networking and the emergency network reset function in the UI of XCP-NG and neither seem to work to reset the management Interface, after rebooting they still have no interfaces at all (which happened when the failed uplink bond was created).
I will probably need to wipe and re-install to get traction again.
Also I am confused with the MTU.
The servers we are using are configured (using a server profile template) that we also use with vMware, and the uplinks on those are all MTU 9000 both in the VNIC templates (ie hardware side) and in the distributed vSwitches in vCenter (equivalent of bonded interfaces in XO?)
If their was a problem with MTU, I would have though they would not work either.
I will keep at it, thanks for the help.

@olivierlambert I have 9000 everywhere on the network so i set the MTU to that.
I did notice in a previous POC that I used 1500 in XO/XCP-NG though....
Thoughts?
How can I recover, just delete /re-install the hypervisor and reconnect?

Hi all, I have a fresh green fields install of Xen Orchestra with 3 x 8.3.0 servers.
The servers have 8 interfaces, of which I installed the management IP and VLAN on eth0, then connected all 3 to XO and added into a pool.
I then created a bond for eth0 and eth1 per https://xcp-ng.org/blog/2022/09/13/network-bonds-in-xcp-ng/ and the master failed to take any network config, and the 2 slaves both lost connectivity, even after a reboot.
Am I doing this correctly or did I miss something?

Thanks all, much appreciated

Hi.
We are migrating from vMware where we use RedHat Satellite to automate our RHEL builds.
I dont expect there to be much of any integration between XO and Satellite, however I see quite a few posts about Terraform and Ansible.
We currently use Redhat Ansible Automation Platform for patching and hardening, and would like to leverage it to build VMs on XO via ansible automation.
Are there any docs or labs on how to do this please?

Resolved with the following commands:

sudo npm install n -g
n stable

Please close

@Andrew Ok thanks, I assumed the install script would handle that?
Murf

I am trying to run an update (Option 2) on my XO which I built in Feb last year, and last updated around March last year.
I get this error:

error @vates/generator-toolbox@1.0.1: The engine "node" is incompatible with this module. Expected version ">=20.18". Got "18.19.1"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
+ rm -rf /opt/xo/xo-builds/xen-orchestra-202504240934

Any help much appreciated!

@olivierlambert Thanks!

Topic says it all!

@olivierlambert Thanks, I see they are there

https://www.cisco.com/c/en/us/products/collateral/servers-unified-computing/ucs-x-series-modular-system/ucs-x210c-m7-compute-node-aag.html

Thanks in advance

@olivierlambert Thanks

Hi all.
I upgraded from 8.3 Beta 2 to RC1 via yum update but do not see anything to indicate that this took place.
On the XCP-ng console it just says "XCP-ng 8.3" as does the Advanced settings under XO - 8.3.0 ()
Thanks

Hi All,
I am not clear of the process required here.
I have a Windows Server VM with a 6TB attached RDM LUN
Do i need to detach it in VMware, migrate the VM, then re-attach somehow in XO?
Thanks in advance,
Murf.

@florent the thing is I am looking for a seamless migration workflow from VMware.. not a manual VM per VM migration. (unless v2v has this also?)

@Danp
In VMware->

In XOA after import ->

@Danp no need really, they are just set to DHCP instead of the static settings we had, as if I had added a new interface altogether

@Danp Yes the import process. I think it is because we are using VMXNET 3 interfaces, not E1000 (which caused us horrible problems over the years)

@Danp When I migrate Windows Server VMs the network interface does not have the settings anymore and I have to reconfigure them manually, is this expected behavior?