XCP-ng 8.2.1
The Host is patched.

XO which I usually use is build from sources.
The last update was yesterday.
I'm currently not sure where exactly to find out the version.

The command displays the following. (xe vdi-list uuid=<UUID>)

uuid ( RO)                    : f0efdb76-a8c0-4a48-8708-3d456a2f45a6
              name-label ( RW): backup01
        name-description ( RW): 
           is-a-snapshot ( RO): true
             snapshot-of ( RO): f0efdb76-a8c0-4a48-8708-3d456a2f45a6
               snapshots ( RO): f0efdb76-a8c0-4a48-8708-3d456a2f45a6
           snapshot-time ( RO): 20241123T02:16:10Z
      allowed-operations (SRO): snapshot; clone
      current-operations (SRO): 
                 sr-uuid ( RO): 9cb0f64d-4941-a1e5-9143-acff1de0e93d
           sr-name-label ( RO): Local storage
               vbd-uuids (SRO): 48fd077c-f1ec-9f35-65ba-76928b65b5f8
         crashdump-uuids (SRO): 
            virtual-size ( RO): 17179869184
    physical-utilisation ( RO): 11376177152
                location ( RO): f0efdb76-a8c0-4a48-8708-3d456a2f45a6
                    type ( RO): User
                sharable ( RO): false
               read-only ( RO): false
            storage-lock ( RO): false
                 managed ( RO): true
     parent ( RO) [DEPRECATED]: <not in database>
                 missing ( RO): false
            is-tools-iso ( RO): false
            other-config (MRW): 
           xenstore-data (MRO): 
               sm-config (MRO): host_OpaqueRef:56af5c39-7115-4328-8ddf-64d2526e8102: RW; read-caching-reason-f9e4b858-c697-47c1-80b1-a48251baa2a6: NO_RO_IMAGE; read-caching-enabled-on-f9e4b858-c697-47c1-80b1-a48251baa2a6: false
                 on-boot ( RW): persist
           allow-caching ( RW): false
         metadata-latest ( RO): false
        metadata-of-pool ( RO): <not in database>
                    tags (SRW): 
             cbt-enabled ( RO): false

The SR view in xoa:

The vm stoage view:

If I try ti attach it there is no vdi to select.

I think it is still attached but not displayed.
The VM still works normally, although the OS disk is not displayed in XOA.
I have also installed another XOA instance.
It is not displayed there either.

The virtual hard disk is still displayed in the server's file system.
How do I get it back into xoa?

Hey,

I wanted to copy a VDI to another SR via xo.
Unfortunately, this does not seem to have worked.
The VDI is no longer displayed in xo.
However, the VM can still boot normally.
Does anyone have any idea how I can get the VDI back into xo?
I have already tried rescanning the SR.

I have installed XO from sources.
I tested XOA and it works.
Sounds like this is related to your post.
Is there an GitHub issue to follow?

Hello,
unfortunately I can no longer create a VM with CloudInit Config.
The task overview shows me the following.
[XO] Importieren von Inhalten in VDI XO CloudConfigDrive auf SR hdd (auf server) 0%
It seems to stuck.
Does anyone have an idea why this could be?

@gskger works thanks

Hey,
Is it possible to undo the activation of the SDN Controller.
I have already deactivated it via the settings and plugins.
However, I still get the error message.

vif.set
{
  "allowedIpv4Addresses": [
    "10.0.0.1"
  ],
  "allowedIpv6Addresses": [],
  "id": "123e4567-e89b-12d3-a456-426614174000"
}
{
  "code": "OPERATION_NOT_ALLOWED",
  "params": [
    "A vswitch controller is active"
  ],
  "call": {
    "method": "VIF.set_locking_mode",
    "params": [
      "OpaqueRef:123e4567-e89b-12d3-a456-426614174000",
      "locked"
    ]
  },
  "message": "OPERATION_NOT_ALLOWED(A vswitch controller is active)",
  "name": "XapiError",
  "stack": "XapiError: OPERATION_NOT_ALLOWED(A vswitch controller is active)
    at Function.wrap (file:///opt/xo/xo-builds/xen-orchestra-202402061623/packages/xen-api/_XapiError.mjs:16:12)
    at file:///opt/xo/xo-builds/xen-orchestra-202402061623/packages/xen-api/transports/json-rpc.mjs:35:21"
}

Hey guys,
I noticed 2 more things with the Netbox Sync plugin.

first:
First, you can define device roles in Netbox.
The XOA plugin does not seem to assign these so far.
There it would be practical if you can define the device role in the plugin settings, which the VMs should get.

secondly:
The tags that are added by the sync of the XOA plugin should be assigned to the VMs.
This makes the whole thing clearer.
The tags are displayed without this assignment e.g. also in the IPAM.

OK then I will wait.
The icons are not an important feature for survival anyway.

Good day,
is there a possibility to add more operating system icons?
As there are already some for Debian and FreeBSD.
E.g. for AlmaLinux?

@yann

Here is the output from ifconfig.
I replaced the public IPs with:
192.168.178.0/24
fe00::/112

enc0: flags=0<> metric 0 mtu 1536
	groups: enc
	nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
	options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
	inet6 ::1 prefixlen 128
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
	inet 127.0.0.1 netmask 0xff000000
	groups: lo
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
pflog0: flags=20100<PROMISC,PPROMISC> metric 0 mtu 33160
	groups: pflog
pfsync0: flags=41<UP,RUNNING> metric 0 mtu 1500
	pfsync: syncdev: xn2 syncpeer: 10.0.255.2 maxupd: 128 defer: off
	syncok: 1
	groups: pfsync
xn0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
	description: WAN (wan)
	ether 32:92:38:a6:82:37
	inet 192.168.178.3 netmask 0xfffffff0 broadcast 192.168.178.255
	inet 192.168.178.2 netmask 0xfffffff0 broadcast 192.168.178.255 vhid 3
	inet 192.168.178.4 netmask 0xfffffff0 broadcast 192.168.178.255
	inet 192.168.178.5 netmask 0xfffffff0 broadcast 192.168.178.255
	inet 192.168.178.6 netmask 0xfffffff0 broadcast 192.168.178.255
	inet 192.168.178.7 netmask 0xfffffff0 broadcast 192.168.178.255
	inet 192.168.178.8 netmask 0xfffffff0 broadcast 192.168.178.255
	inet 192.168.178.9 netmask 0xfffffff0 broadcast 192.168.178.255
	inet6 fe00::3 prefixlen 64
	inet6 fe80::30da:86ff:fea6:e181%xn0 prefixlen 64 scopeid 0x5
	inet6 fe00::2 prefixlen 64 vhid 4
	carp: MASTER vhid 3 advbase 1 advskew 100
	carp: MASTER vhid 4 advbase 1 advskew 100
	media: Ethernet manual
	status: active
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
xn1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
	description: LAN (lan)
	ether 43:86:34:67:34:75
	inet 10.0.0.2 netmask 0xffffff00 broadcast 10.0.0.255
	inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255 vhid 1
	inet 10.0.3.1 netmask 0xffffff00 broadcast 10.0.3.255
	inet6 fd00::2 prefixlen 112
	inet6 fe80::c45c:dbff:feb5:62b9%xn1 prefixlen 64 scopeid 0x6
	inet6 fd00::1 prefixlen 112 vhid 2
	inet6 fd00::3:1 prefixlen 112
	carp: MASTER vhid 1 advbase 1 advskew 100
	carp: MASTER vhid 2 advbase 1 advskew 100
	media: Ethernet manual
	status: active
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
xn2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	description: pfsync (opt1)
	ether 32:90:32:43:21:89
	inet 10.0.255.1 netmask 0xffffff00 broadcast 10.0.255.255
	inet6 fd00::ffff:1 prefixlen 112
	inet6 fe80::6809:c1ff:fe14:b82d%xn2 prefixlen 64 scopeid 0x7
	media: Ethernet manual
	status: active
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
wg1: flags=80c1<UP,RUNNING,NOARP,MULTICAST> metric 0 mtu 1420
	options=80000<LINKSTATE>
	inet6 fd00::1:1 prefixlen 112
	inet 10.0.1.1 netmask 0xffffff00
	groups: wg wireguard
	nd6 options=101<PERFORMNUD,NO_DAD>
wg2: flags=80c1<UP,RUNNING,NOARP,MULTICAST> metric 0 mtu 1420
	options=80000<LINKSTATE>
	inet6 fd00::2:1 prefixlen 112
	inet 10.0.2.1 netmask 0xffffff00
	groups: wg wireguard
	nd6 options=101<PERFORMNUD,NO_DAD>

@yann

Here are the infomations.
Guest OS:
Management agent version: 6.2.0-76888
OS name: FreeBSD 13.2-RELEASE-p2 (OpnSense 23.7.1_3)
OS kernel: 13.2-RELEASE-p2

Is it possible that the reporting of IPv6 addresses works only sometimes or not at all?
Also under other operating systems, like Windows Server, Debian and AlmaLinux.

@pdonias
Thank you.
Now everything seems to work.

@pdonias
xo-server: 5.120.2
xo-web: 5.122.2

XCP-NG:
NAME="XCP-ng"
VERSION="8.2.1"
ID="xenenterprise"
ID_LIKE="centos rhel fedora"
VERSION_ID="8.2.1"
PRETTY_NAME="XCP-ng 8.2.1"
ANSI_COLOR="0;31"
HOME_URL="http://xcp-ng.org/"
BUG_REPORT_URL="https://github.com/xcp-ng/xcp"

I also noticed that the doct talks about virtualization > vminterface.
However, in my netbox there is only virtualization > interface.

https://xen-orchestra.com/docs/advanced.html#netbox
next to: Add a UUID custom field:

@ThasianXi
I have updated xoa.
However, I get the same error message.

netbox.synchronize
{
  "pools": [
    "550e8400-e29b-41d4-a716-446655440000"
  ]
}
{
  "message": "ipaddr: the address has neither IPv6 nor IPv4 format",
  "name": "Error",
  "stack": "Error: ipaddr: the address has neither IPv6 nor IPv4 format
    at Object.parse (/opt/xo/xo-builds/xen-orchestra-202308162147/packages/xo-server-netbox/node_modules/ipaddr.js/lib/ipaddr.js:933:19)
    at Netbox.#synchronize (/opt/xo/xo-builds/xen-orchestra-202308162147/packages/xo-server-netbox/src/index.js:631:35)
    at Api.#callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202308162147/packages/xo-server/src/xo-mixins/api.mjs:417:20)"
}

I took a look at the other post.
I get 2 noticeable things that may not have been considered.

first:

{
  "addresses": {}
},

second:

{
  "addresses": {
    "0/ipv4/0": "192.168.178.1",
    "0/ipv4/1": "192.168.178.2",
    "0/ipv4/2": "192.168.178.3",
    "0/ipv4/3": "192.168.178.4",
    "0/ipv4/4": "192.168.178.5",
    "0/ipv4/5": "192.168.178.6",
    "0/ipv4/6": "192.168.178.7",
    "0/ipv4/7": "192.168.178.9",
    "0/ipv4/8": "192.168.178.2 192.168.178.3 192.168.178.4 192.168.178.5 192.168.178.6 192.168.178.7 192.168.178.8 192.168.178.9",
    "1/ipv4/0": "10.0.0.2",
    "1/ipv4/1": "10.0.0.1",
    "1/ipv4/2": "10.0.0.2 10.0.0.1",
    "2/ipv4/0": "10.0.255.1"
  }
},

I replaced the public IPs with some from the 192.168.178.0/24 network.

Are there any suggestions?

Good day,
I have noticed that Xen Orchestra does not sync the IPs with Netbox.
When I manually trigger the sync, I get the following error message.

netbox.synchronize
{
  "pools": [
    "550e8400-e29b-41d4-a716-446655440000"
  ]
}
{
  "message": "ipaddr: the address has neither IPv6 nor IPv4 format",
  "name": "Error",
  "stack": "Error: ipaddr: the address has neither IPv6 nor IPv4 format
    at Object.parse (/opt/xo/xo-builds/xen-orchestra-202306050256/packages/xo-server-netbox/node_modules/ipaddr.js/lib/ipaddr.js:929:19)
    at Netbox.#synchronize (/opt/xo/xo-builds/xen-orchestra-202306050256/packages/xo-server-netbox/src/index.js:555:35)
    at Api.#callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202306050256/packages/xo-server/src/xo-mixins/api.mjs:417:20)"
} 

Does anyone have an idea how to get to the source of the error message.