Subcategories

  • VMs, hosts, pools, networks and all other usual management tasks.

    470 Topics
    4k Posts
    DanpD
    @andrewperry This script hasn't been designed or tested to work on XCP-ng 8.2.1 because it reached EOL status last year. Installing Python3 on XCP-ng 8.2.1 should be fine, but we aren't able to guarantee the script's functionality on that platform. Upgrading to XCP-ng 8.3 is your best option here so that you can benefit from product improvements, security updates, etc.
  • ACLs, Self-service, Cloud-init, Load balancing...

    103 Topics
    859 Posts
    J
    @gcpeters4 said: @john.c This is a good idea as well. If the previous suggestion of trying to do a DNS round robin approach doesn't work, this may be my best option. Thanks for taking the time to provide your suggestion! By the way my suggestion is recommended best practice from Microsoft for their Active Directory software and/or technology. My suggestion will be more likely to work if your DNS servers and requests have issues with Round Robin configuration. Plus with my solution you can easily add more servers as domain controllers to the cluster, as required and use replication to keep them consistent and up to date.
  • All XO backup features: full and incremental, replication, mirrors...

    504 Topics
    5k Posts
    julienXOvatesJ
    @tonyp90 great, thanks !
  • Everything related to Xen Orchestra's REST API

    85 Topics
    633 Posts
    DustyArmstrongD
    @florent OK cool, thank you for the info.
  • Terraform, Packer or any tool to do IaC

    50 Topics
    470 Posts
    CyrilleC
    Kubernetes CSI Driver for XO new release v0.3.0 Stable CSI Volume Identity: This decouples Kubernetes volume identity from backend storage lifecycle events (e.g. VDI migration between Storage Repositories) Topology-Aware Volume Provisioning: Dynamic provisioning now supports topology-aware pool selection. ️ Migration required from v0.2.0 to v0.3.0 Full release note: https://github.com/vatesfr/xenorchestra-csi-driver/releases/tag/v0.3.0
  • 🛰️ XO 6: dedicated thread for all your feedback!

    Pinned
    226
    7 Votes
    226 Posts
    35k Views
    julienXOvatesJ
    @jr-m4 Thank you for this feedback. We'll try to make it better based on this !
  • Some dashboard loading issues with v6

    11
    5
    0 Votes
    11 Posts
    216 Views
    acebmxerA
    @MathieuRA [ "/rest/v0/schedules/8cf0dcb7-2122-41c6-8a2c-5c150308b292", "/rest/v0/schedules/22ce7eb8-ea62-4cbd-8e9b-646f99b6896c", "/rest/v0/schedules/f3504435-9e2b-4e43-a4f4-2f70aa51aa30", "/rest/v0/schedules/d5f4478e-4bba-4679-be5b-375f7c9aeb09", "/rest/v0/schedules/77e3804e-2180-458a-969b-d08f44504c3a", "/rest/v0/schedules/aa8ee2fb-6587-4a5f-a7c7-f292f563b43c", "/rest/v0/schedules/70c6cfc3-baa6-4c8f-804b-ba273b14267d", "/rest/v0/schedules/da426cb4-9bc2-46bf-a5c6-268bb67b80ad", "/rest/v0/schedules/b4fa328a-856a-4e00-8e14-7353d45a79e1", "/rest/v0/schedules/5906f9f7-ca8f-4623-954c-744f0615fb55", "/rest/v0/schedules/3059d28e-eaf1-449f-a0d1-fece3712df0c", "/rest/v0/schedules/14b6af3b-5d2f-4bd2-9d80-440c1d773e2a", "/rest/v0/schedules/f45a8928-bf4b-4d36-bfb2-3d96735ef8fd" ] ❯ journalctl -u xo-server -f -n 50 May 21 07:20:45 xo-ce xo-server[8974]: } May 21 07:20:45 xo-ce xo-server[8974]: } May 21 07:20:45 xo-ce xo-server[8974]: 2026-05-21T07:20:45.705Z xo:xapi:xapi-disks INFO export through vhd May 21 07:20:47 xo-ce xo-server[8974]: 2026-05-21T07:20:47.589Z xo:xapi:vdi WARN invalid HTTP header in response body { May 21 07:20:47 xo-ce xo-server[8974]: body: 'HTTP/1.1 500 Internal Error\r\n' + May 21 07:20:47 xo-ce xo-server[8974]: 'content-length: 318\r\n' + May 21 07:20:47 xo-ce xo-server[8974]: 'content-type: text/html\r\n' + May 21 07:20:47 xo-ce xo-server[8974]: 'connection: close\r\n' + May 21 07:20:47 xo-ce xo-server[8974]: 'cache-control: no-cache, no-store\r\n' + May 21 07:20:47 xo-ce xo-server[8974]: '\r\n' + May 21 07:20:47 xo-ce xo-server[8974]: '<html><body><h1>HTTP 500 internal server error</h1>An unexpected error occurred; please wait a while and try again. If the problem persists, please contact your support representative.<h1> Additional information </h1>VDI_INCOMPATIBLE_TYPE: [ OpaqueRef:fdeb8877-741a-d753-988f-34f20417f451; CBT metadata ]</body></html>' May 21 07:20:47 xo-ce xo-server[8974]: } May 21 07:20:47 xo-ce xo-server[8974]: 2026-05-21T07:20:47.598Z xo:xapi:xapi-disks WARN can't compute delta OpaqueRef:e17293bd-788e-1391-4567-4a3b9f2be433 from OpaqueRef:fdeb8877-741a-d753-988f-34f20417f451, fallBack to a full { May 21 07:20:47 xo-ce xo-server[8974]: error: Error: invalid HTTP header in response body May 21 07:20:47 xo-ce xo-server[8974]: at checkVdiExport (file:///opt/xen-orchestra/@xen-orchestra/xapi/vdi.mjs:37:19) May 21 07:20:47 xo-ce xo-server[8974]: at process.processTicksAndRejections (node:internal/process/task_queues:103:5) May 21 07:20:47 xo-ce xo-server[8974]: at async Xapi.exportContent (file:///opt/xen-orchestra/@xen-orchestra/xapi/vdi.mjs:261:5) May 21 07:20:47 xo-ce xo-server[8974]: at async #getExportStream (file:///opt/xen-orchestra/@xen-orchestra/xapi/disks/XapiVhdStreamSource.mjs:123:20) May 21 07:20:47 xo-ce xo-server[8974]: at async XapiVhdStreamSource.init (file:///opt/xen-orchestra/@xen-orchestra/xapi/disks/XapiVhdStreamSource.mjs:135:23) May 21 07:20:47 xo-ce xo-server[8974]: at async #openExportStream (file:///opt/xen-orchestra/@xen-orchestra/xapi/disks/Xapi.mjs:182:7) May 21 07:20:47 xo-ce xo-server[8974]: at async #openNbdStream (file:///opt/xen-orchestra/@xen-orchestra/xapi/disks/Xapi.mjs:97:22) May 21 07:20:47 xo-ce xo-server[8974]: at async XapiDiskSource.openSource (file:///opt/xen-orchestra/@xen-orchestra/xapi/disks/Xapi.mjs:260:18) May 21 07:20:47 xo-ce xo-server[8974]: at async XapiDiskSource.init (file:///opt/xen-orchestra/@xen-orchestra/disk-transform/dist/DiskPassthrough.mjs:28:41) May 21 07:20:47 xo-ce xo-server[8974]: at async file:///opt/xen-orchestra/@xen-orchestra/backups/_incrementalVm.mjs:66:5 May 21 07:20:47 xo-ce xo-server[8974]: } May 21 07:20:47 xo-ce xo-server[8974]: 2026-05-21T07:20:47.600Z xo:xapi:xapi-disks INFO export through vhd May 21 07:33:57 xo-ce xo-server[8974]: 2026-05-21T07:33:57.365Z xo:backups:worker INFO backup has ended May 21 07:33:57 xo-ce xo-server[8974]: 2026-05-21T07:33:57.558Z xo:backups:worker INFO process will exit { May 21 07:33:57 xo-ce xo-server[8974]: duration: 2036887755, May 21 07:33:57 xo-ce xo-server[8974]: exitCode: 0, May 21 07:33:57 xo-ce xo-server[8974]: resourceUsage: { May 21 07:33:57 xo-ce xo-server[8974]: userCPUTime: 2331929487, May 21 07:33:57 xo-ce xo-server[8974]: systemCPUTime: 555709233, May 21 07:33:57 xo-ce xo-server[8974]: maxRSS: 273572, May 21 07:33:57 xo-ce xo-server[8974]: sharedMemorySize: 0, May 21 07:33:57 xo-ce xo-server[8974]: unsharedDataSize: 0, May 21 07:33:57 xo-ce xo-server[8974]: unsharedStackSize: 0, May 21 07:33:57 xo-ce xo-server[8974]: minorPageFault: 11509457, May 21 07:33:57 xo-ce xo-server[8974]: majorPageFault: 3, May 21 07:33:57 xo-ce xo-server[8974]: swappedOut: 0, May 21 07:33:57 xo-ce xo-server[8974]: fsRead: 21664, May 21 07:33:57 xo-ce xo-server[8974]: fsWrite: 0, May 21 07:33:57 xo-ce xo-server[8974]: ipcSent: 0, May 21 07:33:57 xo-ce xo-server[8974]: ipcReceived: 0, May 21 07:33:57 xo-ce xo-server[8974]: signalsCount: 0, May 21 07:33:57 xo-ce xo-server[8974]: voluntaryContextSwitches: 3572469, May 21 07:33:57 xo-ce xo-server[8974]: involuntaryContextSwitches: 248999 May 21 07:33:57 xo-ce xo-server[8974]: }, May 21 07:33:57 xo-ce xo-server[8974]: summary: { duration: '34m', cpuUsage: '142%', memoryUsage: '267.16 MiB' } May 21 07:33:57 xo-ce xo-server[8974]: } ❯ journalctl -u xo-server May 03 18:14:41 xo-ce systemd[1]: Starting xo-server.service - Xen Orchestra Server... May 03 18:14:41 xo-ce systemd[1]: Started xo-server.service - Xen Orchestra Server. May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.248Z xo:main INFO Starting xo-server v5.200.0 (https://github.com> May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.255Z xo:main INFO Configuration loaded. May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.260Z xo:main INFO Web server listening on http://0.0.0.0:80 May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.263Z xo:main INFO Web server listening on https://0.0.0.0:443 May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.473Z xo:mixins:hooks WARN start failure { May 03 18:14:43 xo-ce xo-server[6780]: error: Error: spawn xenstore-read ENOENT May 03 18:14:43 xo-ce xo-server[6780]: at Process.ChildProcess._handle.onexit (node:internal/child_process:287:19) May 03 18:14:43 xo-ce xo-server[6780]: at onErrorNT (node:internal/child_process:508:16) May 03 18:14:43 xo-ce xo-server[6780]: at processTicksAndRejections (node:internal/process/task_queues:90:21) { May 03 18:14:43 xo-ce xo-server[6780]: errno: -2, May 03 18:14:43 xo-ce xo-server[6780]: code: 'ENOENT', May 03 18:14:43 xo-ce xo-server[6780]: syscall: 'spawn xenstore-read', May 03 18:14:43 xo-ce xo-server[6780]: path: 'xenstore-read', May 03 18:14:43 xo-ce xo-server[6780]: spawnargs: [ 'vm' ], May 03 18:14:43 xo-ce xo-server[6780]: cmd: 'xenstore-read vm' May 03 18:14:43 xo-ce xo-server[6780]: } May 03 18:14:43 xo-ce xo-server[6780]: } May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.478Z xo:mixins:hooks WARN start failure { May 03 18:14:43 xo-ce xo-server[6780]: error: Error: Command failed with exit code 5: vgchange -an May 03 18:14:43 xo-ce xo-server[6780]: WARNING: Running as a non-root user. Functionality may be unavailable. May 03 18:14:43 xo-ce xo-server[6780]: /run/lock/lvm/P_global:aux: open failed: Permission denied May 03 18:14:43 xo-ce xo-server[6780]: at makeError (file:///opt/xen-orchestra/packages/xo-server/node_modules/execa/l> May 03 18:14:43 xo-ce xo-server[6780]: at handlePromise (file:///opt/xen-orchestra/packages/xo-server/node_modules/exe> May 03 18:14:43 xo-ce xo-server[6780]: shortMessage: 'Command failed with exit code 5: vgchange -an', May 03 18:14:43 xo-ce xo-server[6780]: command: 'vgchange -an', May 03 18:14:43 xo-ce xo-server[6780]: escapedCommand: 'vgchange -an', May 03 18:14:43 xo-ce xo-server[6780]: exitCode: 5, May 03 18:14:43 xo-ce xo-server[6780]: signal: undefined, May 03 18:14:43 xo-ce xo-server[6780]: signalDescription: undefined, May 03 18:14:43 xo-ce xo-server[6780]: stdout: '', May 03 18:14:43 xo-ce xo-server[6780]: stderr: ' WARNING: Running as a non-root user. Functionality may be unavailable.> May 03 18:14:43 xo-ce xo-server[6780]: ' /run/lock/lvm/P_global:aux: open failed: Permission denied', May 03 18:14:43 xo-ce xo-server[6780]: cwd: '/opt/xen-orchestra/packages/xo-server', May 03 18:14:43 xo-ce xo-server[6780]: failed: true, May 03 18:14:43 xo-ce xo-server[6780]: timedOut: false, May 03 18:14:43 xo-ce xo-server[6780]: isCanceled: false, May 03 18:14:43 xo-ce xo-server[6780]: killed: false May 03 18:14:43 xo-ce xo-server[6780]: } May 03 18:14:43 xo-ce xo-server[6780]: } May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.556Z xo:xo-mixins:subjects INFO Default user created: admin@admin> May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.565Z xo:main INFO Setting up /robots.txt → /opt/xen-orchestra/pac> May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.616Z xo:plugin INFO register audit May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.618Z xo:plugin INFO register auth-github May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.619Z xo:plugin INFO register auth-google May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.620Z xo:plugin INFO register auth-ldap May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.621Z xo:plugin INFO register auth-oidc May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.621Z xo:plugin INFO register auth-saml May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.622Z xo:plugin INFO register backup-reports May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.623Z xo:plugin INFO register load-balancer May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.623Z xo:plugin INFO register netbox May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.624Z xo:plugin INFO register openmetrics May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.625Z xo:plugin INFO register perf-alert May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.626Z xo:plugin INFO register sdn-controller May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.627Z xo:plugin INFO register test-plugin May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.628Z xo:plugin INFO register transport-email May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.628Z xo:plugin INFO register transport-icinga2 May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.629Z xo:plugin INFO register transport-nagios May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.629Z xo:plugin INFO register transport-slack May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.630Z xo:plugin INFO register transport-xmpp May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.630Z xo:plugin INFO register usage-report May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.631Z xo:plugin INFO register web-hooks May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.998Z xo:xo-server-openmetrics INFO Plugin initialized May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin auth-gith> May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin audit for> May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin auth-oidc> May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin auth-goog> May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin auth-ldap> May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin auth-saml> May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin load-bala> May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin netbox fo> May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin perf-aler> May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin sdn-contr> May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin backup-re> May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin test-plug> May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin transport> May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin transport> May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin transport> May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin transport> May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin transport> May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin web-hooks> May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin usage-rep> May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin openmetri> May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.027Z xo:plugin INFO successfully register auth-github May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.027Z xo:plugin INFO successfully register auth-oidc May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.027Z xo:plugin INFO successfully register auth-google May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.027Z xo:plugin INFO successfully register auth-ldap May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.027Z xo:plugin INFO successfully register auth-saml May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.027Z xo:plugin INFO successfully register load-balancer May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.040Z xo:plugin INFO successfully register audit May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.056Z xo:plugin INFO successfully register netbox May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.056Z xo:plugin INFO successfully register test-plugin May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.056Z xo:plugin INFO successfully register transport-nagios May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.056Z xo:plugin INFO successfully register transport-email May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.056Z xo:plugin INFO successfully register transport-icinga2 May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.056Z xo:plugin INFO successfully register transport-slack May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.056Z xo:plugin INFO successfully register transport-xmpp May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.056Z xo:plugin INFO successfully register web-hooks May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.056Z xo:plugin INFO successfully register usage-report May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.056Z xo:xo-server-openmetrics INFO Starting OpenMetrics server { > May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.062Z xo:plugin INFO successfully register backup-reports May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.062Z xo:plugin INFO successfully register perf-alert May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.142Z xo:plugin INFO successfully register openmetrics May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.480Z xo:plugin INFO successfully register sdn-controller May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.481Z xo:main INFO Setting up /v5 → /opt/xen-orchestra/packages/xo> May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.481Z xo:main INFO Setting up /v6 → /opt/xen-orchestra/@xen-orches> May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.481Z xo:main INFO Setting up / → /opt/xen-orchestra/@xen-orchestr> May 03 18:15:16 xo-ce xo-server[6780]: (node:6780) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Pleas> May 03 18:15:16 xo-ce xo-server[6780]: (Use `node --trace-deprecation ...` to show where the warning was created) May 03 18:15:16 xo-ce xo-server[6780]: 2026-05-03T18:15:16.063Z xo:xo-server WARN Node warning { May 03 18:15:16 xo-ce xo-server[6780]: error: DeprecationWarning: The `util._extend` API is deprecated. Please use Object.> May 03 18:15:16 xo-ce xo-server[6780]: at ProxyServer.ws (/opt/xen-orchestra/node_modules/http-proxy/lib/http-proxy/in> May 03 18:15:16 xo-ce xo-server[6780]: at app.<anonymous> (file:///opt/xen-orchestra/packages/xo-server/src/index.mjs:> May 03 18:15:16 xo-ce xo-server[6780]: at app.emit (node:events:509:28) May 03 18:15:16 xo-ce xo-server[6780]: at app.emit (/opt/xen-orchestra/@xen-orchestra/log/configure.js:52:17) May 03 18:15:16 xo-ce xo-server[6780]: at Server.<anonymous> (file:///opt/xen-orchestra/packages/xo-server/src/index.m> May 03 18:15:16 xo-ce xo-server[6780]: at Server.emit (node:events:521:24) May 03 18:15:16 xo-ce xo-server[6780]: at Server.patchedEmit [as emit] (/opt/xen-orchestra/@xen-orchestra/log/configur> May 03 18:15:16 xo-ce xo-server[6780]: at onParserExecuteCommon (node:_http_server:987:14) May 03 18:15:16 xo-ce xo-server[6780]: at onParserExecute (node:_http_server:891:3) { May 03 18:15:16 xo-ce xo-server[6780]: code: 'DEP0060' May 03 18:15:16 xo-ce xo-server[6780]: } May 03 18:15:16 xo-ce xo-server[6780]: } May 03 18:15:30 xo-ce xo-server[6780]: 2026-05-03T18:15:30.553Z xo:rest-api:listener ERROR cannot handle data for task liste> May 03 18:15:30 xo-ce xo-server[6780]: error: XoError: no such user a7eed653-d733-4909-99b6-88afb4baf6c4 May 03 18:15:30 xo-ce xo-server[6780]: at noSuchObject (/opt/xen-orchestra/packages/xo-common/api-errors.js:26:11) May 03 18:15:30 xo-ce xo-server[6780]: at default._getUser (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins> May 03 18:15:30 xo-ce xo-server[6780]: at default.getUser (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/> May 03 18:15:30 xo-ce xo-server[6780]: at XoListener.getAclEvent (file:///opt/xen-orchestra/@xen-orchestra/rest-api/di> May 03 18:15:30 xo-ce xo-server[6780]: at XoListener.handleData (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dis> May 03 18:15:30 xo-ce xo-server[6780]: at file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/abstract-classes/list> May 03 18:15:30 xo-ce xo-server[6780]: code: 1, May 03 18:15:30 xo-ce xo-server[6780]: data: { id: 'a7eed653-d733-4909-99b6-88afb4baf6c4', type: 'user' } May 03 18:15:30 xo-ce xo-server[6780]: } May 03 18:15:30 xo-ce xo-server[6780]: } May 03 18:15:30 xo-ce xo-server[6780]: 2026-05-03T18:15:30.553Z xo:rest-api:listener ERROR cannot handle data for task liste> May 03 18:15:30 xo-ce xo-server[6780]: error: XoError: no such user a7eed653-d733-4909-99b6-88afb4baf6c4 May 03 18:15:30 xo-ce xo-server[6780]: at noSuchObject (/opt/xen-orchestra/packages/xo-common/api-errors.js:26:11) May 03 18:15:30 xo-ce xo-server[6780]: at default._getUser (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins> May 03 18:15:30 xo-ce xo-server[6780]: at default.getUser (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/> May 03 18:15:30 xo-ce xo-server[6780]: at XoListener.getAclEvent (file:///opt/xen-orchestra/@xen-orchestra/rest-api/di> May 03 18:15:30 xo-ce xo-server[6780]: at XoListener.handleData (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dis> May 03 18:15:30 xo-ce xo-server[6780]: at file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/abstract-classes/list> May 03 18:15:30 xo-ce xo-server[6780]: code: 1, May 03 18:15:30 xo-ce xo-server[6780]: data: { id: 'a7eed653-d733-4909-99b6-88afb4baf6c4', type: 'user' } May 03 18:15:30 xo-ce xo-server[6780]: } May 03 18:15:30 xo-ce xo-server[6780]: } May 03 18:15:30 xo-ce xo-server[6780]: 2026-05-03T18:15:30.557Z xo:authentification ERROR no such user a7eed653-d733-4909-99> May 03 18:15:30 xo-ce xo-server[6780]: error: XoError: no such user a7eed653-d733-4909-99b6-88afb4baf6c4 May 03 18:15:30 xo-ce xo-server[6780]: at noSuchObject (/opt/xen-orchestra/packages/xo-common/api-errors.js:26:11) May 03 18:15:30 xo-ce xo-server[6780]: at default._getUser (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins> May 03 18:15:30 xo-ce xo-server[6780]: at default.getUser (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/> May 03 18:15:30 xo-ce xo-server[6780]: at default._authenticateUser (file:///opt/xen-orchestra/packages/xo-server/src/> May 03 18:15:30 xo-ce xo-server[6780]: at auth (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/authenticat> May 03 18:15:30 xo-ce xo-server[6780]: at Task.runInside (/opt/xen-orchestra/@vates/task/index.js:204:22) May 03 18:15:30 xo-ce xo-server[6780]: at Task.run (/opt/xen-orchestra/@vates/task/index.js:188:20) May 03 18:15:30 xo-ce xo-server[6780]: at Xo.signIn (file:///opt/xen-orchestra/packages/xo-server/src/api/session.mjs:> May 03 18:15:30 xo-ce xo-server[6780]: at Task.runInside (/opt/xen-orchestra/@vates/task/index.js:204:22) May 03 18:15:30 xo-ce xo-server[6780]: at Task.run (/opt/xen-orchestra/@vates/task/index.js:188:20) May 03 18:15:30 xo-ce xo-server[6780]: at Api.#callApiMethod (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixi> May 03 18:15:30 xo-ce xo-server[6780]: code: 1, May 03 18:15:30 xo-ce xo-server[6780]: data: { id: 'a7eed653-d733-4909-99b6-88afb4baf6c4', type: 'user' } May 03 18:15:30 xo-ce xo-server[6780]: } May 03 18:15:30 xo-ce xo-server[6780]: } May 03 18:15:30 xo-ce xo-server[6780]: 2026-05-03T18:15:30.560Z xo:api WARN (unknown user) | session.signIn(...) [8ms] =!> X> May 03 18:15:53 xo-ce sudo[6982]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=999) May 03 18:15:53 xo-ce sudo[6982]: xo-service : PWD=/opt/xen-orchestra/packages/xo-server ; USER=root ; COMMAND=/usr/bin/mou> May 03 18:15:53 xo-ce sudo[6984]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=999) May 03 18:15:53 xo-ce sudo[6984]: xo-service : PWD=/opt/xen-orchestra/packages/xo-server ; USER=root ; COMMAND=/usr/bin/mou> May 03 18:15:54 xo-ce sudo[6984]: pam_unix(sudo:session): session closed for user root May 03 18:15:54 xo-ce sudo[6982]: pam_unix(sudo:session): session closed for user root May 03 18:16:45 xo-ce xo-server[6780]: 2026-05-03T18:16:45.301Z xo:main INFO + Console proxy (nick - 127.0.0.1) May 03 18:16:47 xo-ce xo-server[6780]: 2026-05-03T18:16:47.299Z xo:main INFO - Console proxy (nick - 127.0.0.1) May 03 23:04:20 xo-ce xo-server[6780]: 2026-05-03T23:04:20.943Z xo:api WARN nick | token.create(...) [1ms] =!> Error: too hi> May 03 23:04:38 xo-ce xo-server[6780]: 2026-05-03T23:04:38.359Z xo:api WARN nick | token.create(...) [1ms] =!> Error: too hi> May 03 23:04:52 xo-ce xo-server[6780]: 2026-05-03T23:04:52.662Z xo:api WARN nick | token.create(...) [1ms] =!> Error: too hi> May 03 23:05:19 xo-ce xo-server[6780]: 2026-05-03T23:05:19.432Z xo:api WARN nick | token.create(...) [1ms] =!> Error: too hi> May 03 23:34:52 xo-ce xo-server[6780]: 2026-05-03T23:34:52.293Z xo:main INFO + Console proxy (nick - 127.0.0.1) May 03 23:36:04 xo-ce xo-server[6780]: 2026-05-03T23:36:04.989Z xo:main INFO - Console proxy (nick - 127.0.0.1) May 04 04:08:33 xo-ce xo-server[8919]: 2026-05-04T04:08:33.617Z xo:backups:worker INFO starting backup May 04 04:08:33 xo-ce sudo[8932]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=999) May 04 04:08:33 xo-ce sudo[8932]: xo-service : PWD=/opt/xen-orchestra/packages/xo-server ; USER=root ; COMMAND=/usr/bin/mou> May 04 04:08:33 xo-ce sudo[8932]: pam_unix(sudo:session): session closed for user root May 04 04:08:36 xo-ce xo-server[8919]: 2026-05-04T04:08:36.432Z xo:xapi:xapi-disks INFO export through vhd May 04 04:08:37 xo-ce xo-server[8919]: 2026-05-04T04:08:37.874Z xo:xapi:xapi-disks INFO export through vhd May 04 04:12:16 xo-ce xo-server[8919]: 2026-05-04T04:12:16.797Z xo:xapi:xapi-disks INFO export through vhd May 04 04:37:10 xo-ce xo-server[8919]: 2026-05-04T04:37:10.906Z xo:xapi:xapi-disks INFO export through vhd May 04 04:46:44 xo-ce xo-server[8919]: { May 04 04:46:44 xo-ce xo-server[8919]: err: [Error: Unknown system error -122: Unknown system error -122, write] { May 04 04:46:44 xo-ce xo-server[8919]: errno: -122, May 04 04:46:44 xo-ce xo-server[8919]: code: 'Unknown system error -122', May 04 04:46:44 xo-ce xo-server[8919]: syscall: 'write' May 04 04:46:44 xo-ce xo-server[8919]: } May 04 04:46:44 xo-ce xo-server[8919]: } May 04 04:46:44 xo-ce xo-server[8919]: 2026-05-04T04:46:44.907Z xo:backups:AbstractVmRunner WARN writer step failed { May 04 04:46:44 xo-ce xo-server[8919]: error: Error: ENOENT: no such file or directory, open '/run/xo-server/mounts/3ba9ee> May 04 04:46:44 xo-ce xo-server[8919]: From: May 04 04:46:44 xo-ce xo-server[8919]: at NfsHandler.addSyncStackTrace (/opt/xen-orchestra/@xen-orchestra/fs/dist/loca> May 04 04:46:44 xo-ce xo-server[8919]: at NfsHandler._openFile (/opt/xen-orchestra/@xen-orchestra/fs/dist/local.js:154> May 04 04:46:44 xo-ce xo-server[8919]: at /opt/xen-orchestra/@xen-orchestra/fs/dist/utils.js:29:26 May 04 04:46:44 xo-ce xo-server[8919]: at new Promise (<anonymous>) May 04 04:46:44 xo-ce xo-server[8919]: at NfsHandler.<anonymous> (/opt/xen-orchestra/@xen-orchestra/fs/dist/utils.js:2> May 04 04:46:44 xo-ce xo-server[8919]: at loopResolver (/opt/xen-orchestra/node_modules/promise-toolbox/retry.js:83:46) May 04 04:46:44 xo-ce xo-server[8919]: at new Promise (<anonymous>) May 04 04:46:44 xo-ce xo-server[8919]: at loop (/opt/xen-orchestra/node_modules/promise-toolbox/retry.js:85:22) May 04 04:46:44 xo-ce xo-server[8919]: at NfsHandler.retry (/opt/xen-orchestra/node_modules/promise-toolbox/retry.js:8> May 04 04:46:44 xo-ce xo-server[8919]: at NfsHandler._openFile (/opt/xen-orchestra/node_modules/promise-toolbox/retry.> May 04 04:46:44 xo-ce xo-server[8919]: errno: -2, May 04 04:46:44 xo-ce xo-server[8919]: code: 'ENOENT', May 04 04:46:44 xo-ce xo-server[8919]: syscall: 'open', May 04 04:46:44 xo-ce xo-server[8919]: path: '/run/xo-server/mounts/3ba9eed2-55f1-4760-ac08-655c252aa316/xo-vm-backups/f> May 04 04:46:44 xo-ce xo-server[8919]: }, May 04 04:46:44 xo-ce xo-server[8919]: step: 'writer.updateUuidAndChain()', May 04 04:46:44 xo-ce xo-server[8919]: writer: 'IncrementalRemoteWriter' May 04 04:46:44 xo-ce xo-server[8919]: } May 04 04:46:51 xo-ce xo-server[8919]: 2026-05-04T04:46:51.605Z xo:xapi:xapi-disks INFO export through vhd May 04 04:46:51 xo-ce xo-server[8919]: 2026-05-04T04:46:51.606Z xo:xapi:xapi-disks INFO export through vhd May 04 04:46:53 xo-ce xo-server[8919]: { May 04 04:46:53 xo-ce xo-server[8919]: err: [Error: Unknown system error -122: Unknown system error -122, write] { May 04 04:46:53 xo-ce xo-server[8919]: errno: -122, May 04 04:46:53 xo-ce xo-server[8919]: code: 'Unknown system error -122', May 04 04:46:53 xo-ce xo-server[8919]: syscall: 'write' May 04 04:46:53 xo-ce xo-server[8919]: } May 04 04:46:53 xo-ce xo-server[8919]: } May 04 04:46:53 xo-ce xo-server[8919]: 2026-05-04T04:46:53.434Z vates:nbd-client WARN will retry reading block 13 May 04 04:46:53 xo-ce xo-server[8919]: 2026-05-04T04:46:53.435Z vates:nbd-client WARN will retry reading block 14 May 04 04:46:53 xo-ce xo-server[8919]: 2026-05-04T04:46:53.435Z vates:nbd-client WARN will retry reading block 15 May 04 04:46:53 xo-ce xo-server[8919]: 2026-05-04T04:46:53.435Z vates:nbd-client WARN will retry reading block 16 May 04 04:46:53 xo-ce xo-server[8919]: 2026-05-04T04:46:53.435Z vates:nbd-client WARN will retry reading block 17 May 04 04:46:53 xo-ce xo-server[8919]: 2026-05-04T04:46:53.435Z vates:nbd-client WARN will retry reading block 18 May 04 04:46:53 xo-ce xo-server[8919]: 2026-05-04T04:46:53.435Z vates:nbd-client WARN will retry reading block 19 May 04 04:46:53 xo-ce xo-server[8919]: 2026-05-04T04:46:53.435Z vates:nbd-client WARN will retry reading block 20 May 04 04:46:53 xo-ce xo-server[8919]: 2026-05-04T04:46:53.435Z vates:nbd-client WARN will retry reading block 21 May 04 04:46:53 xo-ce xo-server[8919]: 2026-05-04T04:46:53.435Z xo:backups:AbstractVmRunner WARN writer step failed { May 04 04:46:53 xo-ce xo-server[8919]: error: Error: ENOENT: no such file or directory, open '/run/xo-server/mounts/3ba9ee> May 04 04:46:53 xo-ce xo-server[8919]: From: May 04 04:46:53 xo-ce xo-server[8919]: at NfsHandler.addSyncStackTrace (/opt/xen-orchestra/@xen-orchestra/fs/dist/loca> May 04 04:46:53 xo-ce xo-server[8919]: at NfsHandler._openFile (/opt/xen-orchestra/@xen-orchestra/fs/dist/local.js:154> May 04 04:46:53 xo-ce xo-server[8919]: at /opt/xen-orchestra/@xen-orchestra/fs/dist/utils.js:29:26 May 04 04:46:53 xo-ce xo-server[8919]: at new Promise (<anonymous>) May 04 04:46:53 xo-ce xo-server[8919]: at NfsHandler.<anonymous> (/opt/xen-orchestra/@xen-orchestra/fs/dist/utils.js:2> May 04 04:46:53 xo-ce xo-server[8919]: at loopResolver (/opt/xen-orchestra/node_modules/promise-toolbox/retry.js:83:46) May 04 04:46:53 xo-ce xo-server[8919]: at new Promise (<anonymous>) May 04 04:46:53 xo-ce xo-server[8919]: at loop (/opt/xen-orchestra/node_modules/promise-toolbox/retry.js:85:22) May 04 04:46:53 xo-ce xo-server[8919]: at NfsHandler.retry (/opt/xen-orchestra/node_modules/promise-toolbox/retry.js:8> May 04 04:46:53 xo-ce xo-server[8919]: at NfsHandler._openFile (/opt/xen-orchestra/node_modules/promise-toolbox/retry.> May 04 04:46:53 xo-ce xo-server[8919]: errno: -2, May 04 04:46:53 xo-ce xo-server[8919]: code: 'ENOENT', May 04 04:46:53 xo-ce xo-server[8919]: syscall: 'open', May 04 04:46:53 xo-ce xo-server[8919]: path: '/run/xo-server/mounts/3ba9eed2-55f1-4760-ac08-655c252aa316/xo-vm-backups/4> May 04 04:46:53 xo-ce xo-server[8919]: }, May 04 04:46:53 xo-ce xo-server[8919]: step: 'writer.updateUuidAndChain()', May 04 04:46:53 xo-ce xo-server[8919]: writer: 'IncrementalRemoteWriter' May 04 04:46:53 xo-ce xo-server[8919]: } May 04 04:46:58 xo-ce xo-server[8919]: 2026-05-04T04:46:58.298Z xo:xapi WARN retry { May 04 04:46:58 xo-ce xo-server[8919]: attemptNumber: 0, May 04 04:46:58 xo-ce xo-server[8919]: delay: 5000, May 04 04:46:58 xo-ce xo-server[8919]: error: XapiError: VDI_IN_USE(OpaqueRef:50dc4331-ae9e-5cfe-fbb0-d5f60e311ee6, data_d> May 04 04:46:58 xo-ce xo-server[8919]: at XapiError.wrap (file:///opt/xen-orchestra/packages/xen-api/_XapiError.mjs:16>
  • XO Console: Modifier keys stuck, unable to enter passwords

    14
    0 Votes
    14 Posts
    2k Views
    poddingueP
    Thanks for the clarification, @dsmteam !
  • Edit a Bond to Remove a NIC?

    2
    0 Votes
    2 Posts
    60 Views
    poddingueP
    Take it with a grain of salt, but I think bonds are usually managed as a whole rather than edited port by port in the UI. As far as I can tell, the supported route is from the network section in Xen Orchestra (the bonding part of the infrastructure docs is here: https://docs.xen-orchestra.com/xo5/manage_infrastructure#network-bonding), and on the CLI side, the bond commands are documented at https://docs.xcp-ng.org/appendix/cli_reference#bond-create (there's a matching bond-destroy command alongside it). My honest guess is you may end up destroying and recreating the bond with the four ports you want to keep, since I'm not sure removing a single member in place is exposed anywhere, but I could easily be wrong. If there's a cleaner way that avoids the recreate, someone will let us know.
  • Install XO from sources.

    25
    3 Votes
    25 Posts
    3k Views
    poddingueP
    This is a nice bit of community tooling, and thanks for keeping it updated and being upfront about the "use at your own risk" part. On the naming point a few people raised, I think the distinction folks are drawing is fair: XOA is the Vates-built appliance, and anything you compile yourself is XO from sources. The official docs cover that path at https://docs.xen-orchestra.com/xo5/installation#from-the-sources, including the note that there is no pro support for that method. Hope the project keeps going well!
  • 0 Votes
    16 Posts
    539 Views
    poddingueP
    Thanks for the ping and for narrowing it down; that live-migration repro is a really useful signal. I don't know enough about how the guest tools report IPs back through XAPI to say where the canonicalisation should happen, but it sounds like something @Team-Hypervisor-Kernel might want to look at since the trigger is on the agent side after migration. If it turns out to be reproducible on another Windows guest version (2022, 2019), that might help narrow it further; no pressure though, you've already done the hard part.
  • 0 Votes
    14 Posts
    420 Views
    C
    Dug a little deeper. For a VM where the disks are not shown the following XO API call fails: /rest/v0/vms/a519e879-3971-9210-51b6-7df14336e7b7/vdis { "error": "no such VDI ac37700d-3157-4df7-b8e8-e1799a994591", "data": { "id": "ac37700d-3157-4df7-b8e8-e1799a994591", "type": [ "VDI" ] } } Also the VDI cannot be retrieved over the XO API: /rest/v0/vms/a519e879-3971-9210-51b6-7df14336e7b7 ... "$VBDs": [ "4ea8a3cd-0d1b-dc60-4d9c-fd70e060f06c", "9f4ca686-9fc2-35a9-c3e9-c871c9f68aba" ], ... /rest/v0/vbds/9f4ca686-9fc2-35a9-c3e9-c871c9f68aba { "type": "VBD", "attached": false, "bootable": false, "device": "xvda", "is_cd_drive": false, "position": "0", "read_only": false, "VDI": "ac37700d-3157-4df7-b8e8-e1799a994591", "VM": "a519e879-3971-9210-51b6-7df14336e7b7", "id": "9f4ca686-9fc2-35a9-c3e9-c871c9f68aba", "uuid": "9f4ca686-9fc2-35a9-c3e9-c871c9f68aba", "$pool": "93d361b7-f549-53b7-a3aa-c9695bf0abe4", "$poolId": "93d361b7-f549-53b7-a3aa-c9695bf0abe4", "_xapiRef": "OpaqueRef:1d424d94-f540-2eb4-9e52-2a9b21ec0a19" } /rest/v0/vdis/ac37700d-3157-4df7-b8e8-e1799a994591 { "error": "no such VDI ac37700d-3157-4df7-b8e8-e1799a994591", "data": { "id": "ac37700d-3157-4df7-b8e8-e1799a994591", "type": "VDI" } } However the VDI can be listed using the xe cli: $ xe vm-list uuid=a519e879-3971-9210-51b6-7df14336e7b7 uuid ( RO) : a519e879-3971-9210-51b6-7df14336e7b7 name-label ( RW): XXX power-state ( RO): halted $ xe vbd-list vm-uuid=a519e879-3971-9210-51b6-7df14336e7b7 uuid ( RO) : 4ea8a3cd-0d1b-dc60-4d9c-fd70e060f06c vm-uuid ( RO): a519e879-3971-9210-51b6-7df14336e7b7 vm-name-label ( RO): XXX vdi-uuid ( RO): <not in database> empty ( RO): true device ( RO): xvdd uuid ( RO) : 9f4ca686-9fc2-35a9-c3e9-c871c9f68aba vm-uuid ( RO): a519e879-3971-9210-51b6-7df14336e7b7 vm-name-label ( RO): XXX vdi-uuid ( RO): ac37700d-3157-4df7-b8e8-e1799a994591 empty ( RO): false device ( RO): xvda $ xe vdi-list uuid=ac37700d-3157-4df7-b8e8-e1799a994591 uuid ( RO) : ac37700d-3157-4df7-b8e8-e1799a994591 name-label ( RW): XXX Disk 0 name-description ( RW): Created by XO sr-uuid ( RO): 977b7e63-bb84-57b2-3e0d-206afea553bf virtual-size ( RO): 34359738368 sharable ( RO): false read-only ( RO): false Seems almost like something changed in the XCP-ng API which XO cannot consume.
  • Xen Orchestra has stopped updating commits

    34
    0 Votes
    34 Posts
    10k Views
    florentF
    @ducatijosh did you do a yarn build ?
  • XOA - Memory Usage

    45
    2
    0 Votes
    45 Posts
    3k Views
    florentF
    @acebmxer not yet (a little under the water with the release patch, but we will do it )
  • 0 Votes
    4 Posts
    156 Views
    K
    Ok I think I have resolved the issue. It appears that if you do not activate either a paid license or the trial, it fails with the import because many of the features are not active until you enable the license and then update the XOA appliance. Once I activated the trial and then updated the appliance again, I was able to successfully import the backup. My hesitation with activating the license before importing the config as the licenses are bound and I didn't want to have to redo the setup if the config did not import. Again, it looks like I need to activate the license first and then I can import the config.
  • Default console username and password on XOA Appliance

    Solved
    12
    0 Votes
    12 Posts
    30k Views
    olivierlambertO
    Hi, See https://docs.xen-orchestra.com/troubleshooting#recover-web-login-password
  • XOA Unable to connect xo server every 30s

    4
    0 Votes
    4 Posts
    273 Views
    poddingueP
    Good news, or at least, that's my understanding. This was a known bug and it's fixed in XO 6.4 (released April 29, PR #9681). Upgrading should make those alerts disappear for good. Thanks for the video, it made the report unambiguous.
  • Building from source, now introduces local changes in typed-router.d.ts?

    11
    0 Votes
    11 Posts
    436 Views
    J
    @MathieuRA I noticed you merged https://github.com/vatesfr/xen-orchestra/pull/9787 I just tried it. And it does seem to fix my original issue! Thank you! I am always impressed by you guys. Making testing and reporting upstream (to you guys) a good experience! Elise-FZI opened this pull request in vatesfr/xen-orchestra closed fix(xo6): remove dev routes from prod #9787
  • load-balancer : Affinity to Host groups

    6
    0 Votes
    6 Posts
    417 Views
    Mitchel-APDM
    @olivierlambert In my understanding, Anti affinity tags only looks for the tags that are attached to the VM. For example: Datacenter 1 Host 1 VM1-1 Host 2 VM1-2 Datacenter 2 Host 3 VM2-1 Host 4 VM2-2 VM1-1 and VM1-2 should be able to migrate to Host 1 and Host 2. VM2-1 and VM2-2 should be able to migrate to Host 3 and Host 4. But VM1-1 and VM1-2 should never be able to migrate to Host 3 and Host 4. VM2-1 and VM2-2 should never be able to migrate to Host 1 and Host 2. With the current (Anti) Affinity tags, it will only look to the tags attached to the VM, so in the example it would be possible for VM1-1 to go to Host 4, if VM2-2 would be at Host 3 together with VM2-1. But if we could tag the hosts, it would not be possible for VM1-1 and VM1-2 to be on Host 3 and Host 4
  • Lost connection to ISO Repository

    10
    2
    0 Votes
    10 Posts
    463 Views
    A
    @Pilow Apologies for the late reply. Thank you for sharing the work around. I have tried it and confirmed that the work around works. I hope they can find a solution for this issue.
  • Managing vAPPs with XOA

    11
    0 Votes
    11 Posts
    3k Views
    G
    @olivierlambert +1 For creating vApps GUI in XO Reason: I recently had this configuration: VM1 - Delay 90 Seconds VM2 - Delay 100 Seconds VM3 - Delay 0 Seconds The VM3 instead of starting first, always starts last without fail. One difference I noticed is that VM3 is UEFI vs VM1 & 2 being in BIOS mode. I read elsewhere in the forum that vApps is the only reliable way to have an order. Maybe if we can somehow ensure that delay works, vApps will become less significant ?
  • Ignition and creating a SUSE MicroOS VM

    11
    0 Votes
    11 Posts
    4k Views
    G
    @Bytevenidos That's an interesting way of doing this, I'll have to remember it. I think the Fuel Ignition tool has a vhd output, it also produces both ignition and combustion parts for you. Worked pretty good on one test machine, but I need to go deeper into some of the other choices you can type in.
  • libfuse.so: error adding symbols: File in wrong format

    48
    0 Votes
    48 Posts
    24k Views
    florentF
    @Mark-C this is not forgotten, but file level restore has been under priorised, so it didn't get much work it is now quite high on our backlog , so expect good news in the next months
  • Auth LDAP "unable to get local issuer certificate"?

    3
    0 Votes
    3 Posts
    714 Views
    D
    @omatsei said: @omatsei I figured out the problem. There appears to be a bug in XO that requires you to check "Check Certificate" and/or "Start TLS", save the configuration, then uncheck them, then save again. Then it should work. The bug is that they're unchecked by default, but apparently they're enabled in the background. Thanks for that, I was stump on this one trying to reconfigure a new instance. This is defintely the case even with the latest auth-ldap (v0.10.11) plugin.
  • How do I apply host patches in XO-6?

    3
    0 Votes
    3 Posts
    203 Views
    BrantleyHobbsB
    @DustinB thank you! I suspected as much, but as my wife points out all the time, I am terrible at finding things, so I figured I would ask.