@pdonias
Thank you.
Now everything seems to work.

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?

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.