To update this, since this is the first result when you google "Windows 11 xcp-ng":

Development is on-going on the XAPI project, an minimal set of features is ready and will probably be available in XCP-ng 8.3 beta within a few weeks.

– @stormi on Sep 17.

I had to do the following to remove the reboot block:

xe vm-param-remove param-name=blocked-operations param-key=hard_reboot uuid=$UUID

And then:

xe vm-reboot force=true vm=$UUID

I had to do the following to remove the reboot block:

xe vm-param-remove param-name=blocked-operations param-key=hard_reboot uuid=$UUID

And then:

xe vm-reboot force=true vm=$UUID

@olivierlambert well when XOA is down and we need to restart it, it'd be nice if we could log in with another user. Is there any way to create XAPI users which can use XOLite then?

Will it be possible to log in to XOLite via XOA local users at some point or will only root/admin be supported?

Hi guys,

I would like my hypervisor to be reachable both via a static IPv4 and a static ULA IPv6.

However, configuring an IPv6 address like this doesn't seem to work:

Manually assigning an IPv6 via xe cli doesn't give any error message and doesn't do anything either:

xe pif-reconfigure-ipv6 uuid=50570aa4-c0ca-89aa-ce9c-be5aa21774aa mode=static gateway=fd4:50:50:33::1 IPv6=fd4:50:50:33::41/64 DNS=fd4:50:50:33::1

I have tried multiple combinations with and without DNS and gateway and with the full 0-padded address instead of the short form.

Can I somehow assign a static IPv6 in the XOA web interface? Where will the IPv6 address be shown in the web interface?

To update this, since this is the first result when you google "Windows 11 xcp-ng":

Development is on-going on the XAPI project, an minimal set of features is ready and will probably be available in XCP-ng 8.3 beta within a few weeks.

– @stormi on Sep 17.

@olivierlambert yes, a list of objects would certainly suffice. Probably everything that #makeRequest is calling in packages/xo-server-netbox/index.js?

Hello,

I activated the Netbox plugin as described in https://xen-orchestra.com/docs/advanced.html#netbox.

The synchronisation works fine as long as the user which the token belongs to has "Superuser status".

When I only give them "Staff status" and rights for custom field, cluster, cluster group, cluster type, virtual machine, interface - the synchronisation test works. However, when I try to manually sync a pool, there's an "unknown error". When I take away one of the object rights listed above, I get the following nondescript error when testing the connection:

Code: -32000
Message: unknown error from the peer

Which permissions does XOA actually need to synchronise to netbox? This is something I'd like to have documented in https://xen-orchestra.com/docs/advanced.html#netbox.