@simonp With node = 22.22.3 [image: 1779185768816-screenshot_20260519_061514.png] [image: 1779185784652-screenshot_20260519_061535.png] with node = 24.15.0 [image: 1779186811968-screenshot_20260519_062729.png] [image: 1779186816369-screenshot_20260519_063025.png] [image: 1779186920952-screenshot_20260519_063457.png] ❯ sudo journalctl -u xo-server -n 75 May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.516Z xo:plugin INFO register sdn-controller May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.517Z xo:plugin INFO register test-plugin May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.517Z xo:plugin INFO register transport-email May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.518Z xo:plugin INFO register transport-icinga2 May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.518Z xo:plugin INFO register transport-nagios May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.519Z xo:plugin INFO register transport-slack May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.519Z xo:plugin INFO register transport-xmpp May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.519Z xo:plugin INFO register usage-report May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.520Z xo:plugin INFO register web-hooks May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.890Z xo:xo-server-openmetrics INFO Plugin initialized May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.936Z xo:plugin INFO successfully register auth-github May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.936Z xo:plugin INFO successfully register auth-google May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.936Z xo:plugin INFO successfully register auth-oidc May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.936Z xo:plugin INFO successfully register auth-saml May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.936Z xo:plugin INFO successfully register auth-ldap May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.936Z xo:plugin INFO successfully register netbox May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.936Z xo:plugin INFO successfully register test-plugin May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.936Z xo:plugin INFO successfully register transport-icinga2 May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.936Z xo:plugin INFO successfully register transport-slack May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.936Z xo:plugin INFO successfully register transport-nagios May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.936Z xo:plugin INFO successfully register transport-xmpp May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.936Z xo:plugin INFO successfully register usage-report May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.936Z xo:xo-server-openmetrics INFO Starting OpenMetrics server { port: 9004, bindAddress: 'localhost' } May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.942Z xo:plugin INFO successfully register web-hooks May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.942Z xo:plugin INFO successfully register backup-reports May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.942Z xo:plugin INFO successfully register load-balancer May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.942Z xo:plugin INFO successfully register transport-email May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.942Z xo:plugin INFO successfully register perf-alert May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.952Z xo:plugin INFO successfully register audit May 19 10:26:16 xo-ce xo-server[77015]: 2026-05-19T10:26:16.020Z xo:plugin INFO successfully register sdn-controller May 19 10:26:16 xo-ce xo-server[77015]: 2026-05-19T10:26:16.034Z xo:plugin INFO successfully register openmetrics May 19 10:26:16 xo-ce xo-server[77015]: 2026-05-19T10:26:16.035Z xo:main INFO Setting up /v5 → /opt/xen-orchestra/packages/xo-web/dist May 19 10:26:16 xo-ce xo-server[77015]: 2026-05-19T10:26:16.035Z xo:main INFO Setting up /v6 → /opt/xen-orchestra/@xen-orchestra/web/dist May 19 10:26:16 xo-ce xo-server[77015]: 2026-05-19T10:26:16.035Z xo:main INFO Setting up / → /opt/xen-orchestra/@xen-orchestra/web/dist May 19 10:26:16 xo-ce sudo[77059]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=999) May 19 10:26:16 xo-ce sudo[77059]: xo-service : PWD=/opt/xen-orchestra/packages/xo-server ; USER=root ; COMMAND=/usr/bin/mount -o -t nfs 10.100.2.23:/volume1/Backups /run/xo-server/mounts/a5e54e04-d7e4-48cb-bafc-b2f306d39679 May 19 10:26:16 xo-ce sudo[77060]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=999) May 19 10:26:16 xo-ce sudo[77060]: xo-service : PWD=/opt/xen-orchestra/packages/xo-server ; USER=root ; COMMAND=/usr/bin/mount -o -t nfs 10.100.2.23:/volume1/backup /run/xo-server/mounts/3ba9eed2-55f1-4760-ac08-655c252aa316 May 19 10:26:16 xo-ce sudo[77059]: pam_unix(sudo:session): session closed for user root May 19 10:26:16 xo-ce sudo[77060]: pam_unix(sudo:session): session closed for user root May 19 10:26:30 xo-ce xo-server[77015]: 2026-05-19T10:26:30.018Z xo:rest-api:error-handler INFO [POST] /events/2203cd6f-1023-456b-9cf0-338f35f67be9/subscriptions (401) May 19 10:26:30 xo-ce xo-server[77015]: 2026-05-19T10:26:30.030Z xo:rest-api:error-handler INFO duplicates of the previous log were hidden { nDuplicates: 2 } May 19 10:26:30 xo-ce xo-server[77015]: 2026-05-19T10:26:30.030Z xo:rest-api:error-handler INFO [GET] /srs (401) May 19 10:26:30 xo-ce xo-server[77015]: 2026-05-19T10:26:30.031Z xo:rest-api:error-handler INFO [GET] /alarms (401) May 19 10:26:31 xo-ce xo-server[77015]: 2026-05-19T10:26:31.900Z xo:rest-api:error-handler INFO [GET] /srs (401) May 19 10:26:35 xo-ce xo-server[77015]: 2026-05-19T10:26:35.617Z xo:rest-api:error-handler INFO [GET] /tasks (401) May 19 10:26:36 xo-ce xo-server[77015]: 2026-05-19T10:26:36.842Z xo:rest-api:error-handler INFO [GET] /backup-jobs (401) May 19 10:26:36 xo-ce xo-server[77015]: 2026-05-19T10:26:36.845Z xo:rest-api:error-handler INFO [DELETE] /events/62644a6b-b513-42be-97a4-8fd478f995a6/subscriptions/alarm (401) May 19 10:26:47 xo-ce xo-server[77015]: 2026-05-19T10:26:47.014Z xo:rest-api:error-handler INFO [POST] /events/126a3f5b-672e-418b-b632-28aa7f83b3fd/subscriptions (401) May 19 10:26:52 xo-ce xo-server[77015]: 2026-05-19T10:26:52.622Z xo:rest-api:error-handler INFO [GET] /dashboard (401) May 19 10:26:52 xo-ce xo-server[77015]: 2026-05-19T10:26:52.643Z xo:rest-api:error-handler INFO [GET] /vm-controllers (401) May 19 10:26:54 xo-ce xo-server[77015]: 2026-05-19T10:26:54.260Z xo:rest-api:error-handler INFO [GET] /hosts (401) May 19 10:26:54 xo-ce xo-server[77015]: 2026-05-19T10:26:54.261Z xo:rest-api:error-handler INFO [GET] /tasks (401) May 19 10:26:56 xo-ce xo-server[77015]: 2026-05-19T10:26:56.101Z xo:rest-api:error-handler INFO [GET] /hosts (401) May 19 10:26:57 xo-ce xo-server[77015]: 2026-05-19T10:26:57.546Z xo:rest-api:error-handler INFO [POST] /events/bb27f28f-7660-4ce5-a31c-fcb9b64fdb9f/subscriptions (401) May 19 10:26:57 xo-ce xo-server[77015]: 2026-05-19T10:26:57.587Z xo:rest-api:error-handler INFO [GET] /vdis (401) May 19 10:26:59 xo-ce xo-server[77015]: (node:77015) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead. May 19 10:26:59 xo-ce xo-server[77015]: (Use `node --trace-deprecation ...` to show where the warning was created) May 19 10:26:59 xo-ce xo-server[77015]: 2026-05-19T10:26:59.509Z xo:xo-server WARN Node warning { May 19 10:26:59 xo-ce xo-server[77015]: error: DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead. May 19 10:26:59 xo-ce xo-server[77015]: at ProxyServer.ws (/opt/xen-orchestra/node_modules/http-proxy/lib/http-proxy/index.js:50:26) May 19 10:26:59 xo-ce xo-server[77015]: at app.<anonymous> (file:///opt/xen-orchestra/packages/xo-server/src/index.mjs:697:15) May 19 10:26:59 xo-ce xo-server[77015]: at app.emit (node:events:509:28) May 19 10:26:59 xo-ce xo-server[77015]: at app.emit (/opt/xen-orchestra/@xen-orchestra/log/configure.js:52:17) May 19 10:26:59 xo-ce xo-server[77015]: at Server.<anonymous> (file:///opt/xen-orchestra/packages/xo-server/src/index.mjs:977:13) May 19 10:26:59 xo-ce xo-server[77015]: at Server.emit (node:events:521:24) May 19 10:26:59 xo-ce xo-server[77015]: at Server.patchedEmit [as emit] (/opt/xen-orchestra/@xen-orchestra/log/configure.js:52:17) May 19 10:26:59 xo-ce xo-server[77015]: at onParserExecuteCommon (node:_http_server:987:14) May 19 10:26:59 xo-ce xo-server[77015]: at onParserExecute (node:_http_server:891:3) { May 19 10:26:59 xo-ce xo-server[77015]: code: 'DEP0060' May 19 10:26:59 xo-ce xo-server[77015]: } May 19 10:26:59 xo-ce xo-server[77015]: } May 19 10:27:21 xo-ce xo-server[77015]: 2026-05-19T10:27:21.248Z xo:rest-api:error-handler INFO [GET] /tasks (401) May 19 10:27:21 xo-ce xo-server[77015]: 2026-05-19T10:27:21.251Z xo:rest-api:error-handler INFO [GET] /srs (401) May 19 10:29:55 xo-ce xo-server[77015]: 2026-05-19T10:29:55.798Z xo:rest-api:error-handler INFO [DELETE] /events/8c7df237-3069-4c8e-8b63-d2b7a1233799/subscriptions/SR (401) lines 4-75/75 (END) Back to node 22.22.3 [image: 1779187737830-screenshot_20260519_064831.png] [image: 1779187651651-screenshot_20260519_064527.png] ❯ sudo journalctl -u xo-server -n 75 May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.721Z xo:main INFO Setting up /robots.txt → /opt/xen-orchestra/packages/xo-server/robots.txt May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.796Z xo:plugin INFO register audit May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.796Z xo:plugin INFO register auth-github May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.796Z xo:plugin INFO register auth-google May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.797Z xo:plugin INFO register auth-ldap May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.797Z xo:plugin INFO register auth-oidc May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.797Z xo:plugin INFO register auth-saml May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.797Z xo:plugin INFO register backup-reports May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.797Z xo:plugin INFO register load-balancer May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.797Z xo:plugin INFO register netbox May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.797Z xo:plugin INFO register openmetrics May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.798Z xo:plugin INFO register perf-alert May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.798Z xo:plugin INFO register sdn-controller May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.798Z xo:plugin INFO register test-plugin May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.798Z xo:plugin INFO register transport-email May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.798Z xo:plugin INFO register transport-icinga2 May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.798Z xo:plugin INFO register transport-nagios May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.799Z xo:plugin INFO register transport-slack May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.799Z xo:plugin INFO register transport-xmpp May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.799Z xo:plugin INFO register usage-report May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.799Z xo:plugin INFO register web-hooks May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.184Z xo:xo-server-openmetrics INFO Plugin initialized May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.232Z xo:plugin INFO successfully register auth-google May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.232Z xo:plugin INFO successfully register auth-github May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.232Z xo:plugin INFO successfully register auth-ldap May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.232Z xo:plugin INFO successfully register auth-oidc May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.232Z xo:plugin INFO successfully register netbox May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.232Z xo:plugin INFO successfully register test-plugin May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.232Z xo:plugin INFO successfully register transport-icinga2 May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.233Z xo:plugin INFO successfully register transport-nagios May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.233Z xo:plugin INFO successfully register transport-xmpp May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.233Z xo:plugin INFO successfully register transport-slack May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.233Z xo:plugin INFO successfully register usage-report May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.233Z xo:plugin INFO successfully register web-hooks May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.233Z xo:plugin INFO successfully register auth-saml May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.233Z xo:xo-server-openmetrics INFO Starting OpenMetrics server { port: 9004, bindAddress: 'localhost' } May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.239Z xo:plugin INFO successfully register backup-reports May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.239Z xo:plugin INFO successfully register load-balancer May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.239Z xo:plugin INFO successfully register transport-email May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.239Z xo:plugin INFO successfully register perf-alert May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.321Z xo:plugin INFO successfully register audit May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.327Z xo:plugin INFO successfully register openmetrics May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.334Z xo:plugin INFO successfully register sdn-controller May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.336Z xo:main INFO Setting up /v5 → /opt/xen-orchestra/packages/xo-web/dist May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.336Z xo:main INFO Setting up /v6 → /opt/xen-orchestra/@xen-orchestra/web/dist May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.336Z xo:main INFO Setting up / → /opt/xen-orchestra/@xen-orchestra/web/dist May 19 10:44:36 xo-ce xo-server[79847]: (node:79847) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead. May 19 10:44:36 xo-ce xo-server[79847]: (Use `node --trace-deprecation ...` to show where the warning was created) May 19 10:44:36 xo-ce xo-server[79847]: 2026-05-19T10:44:36.542Z xo:xo-server WARN Node warning { May 19 10:44:36 xo-ce xo-server[79847]: error: DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead. May 19 10:44:36 xo-ce xo-server[79847]: at ProxyServer.ws (/opt/xen-orchestra/node_modules/http-proxy/lib/http-proxy/index.js:50:26) May 19 10:44:36 xo-ce xo-server[79847]: at Function.<anonymous> (file:///opt/xen-orchestra/packages/xo-server/src/index.mjs:697:15) May 19 10:44:36 xo-ce xo-server[79847]: at Function.emit (node:events:519:28) May 19 10:44:36 xo-ce xo-server[79847]: at Function.emit (/opt/xen-orchestra/@xen-orchestra/log/configure.js:52:17) May 19 10:44:36 xo-ce xo-server[79847]: at Server.<anonymous> (file:///opt/xen-orchestra/packages/xo-server/src/index.mjs:977:13) May 19 10:44:36 xo-ce xo-server[79847]: at Server.emit (node:events:531:35) May 19 10:44:36 xo-ce xo-server[79847]: at Server.patchedEmit [as emit] (/opt/xen-orchestra/@xen-orchestra/log/configure.js:52:17) May 19 10:44:36 xo-ce xo-server[79847]: at onParserExecuteCommon (node:_http_server:977:14) May 19 10:44:36 xo-ce xo-server[79847]: at onParserExecute (node:_http_server:881:3) { May 19 10:44:36 xo-ce xo-server[79847]: code: 'DEP0060' May 19 10:44:36 xo-ce xo-server[79847]: } May 19 10:44:36 xo-ce xo-server[79847]: } May 19 10:44:42 xo-ce xo-server[79847]: 2026-05-19T10:44:42.247Z xo:rest-api:error-handler INFO [GET] /tasks (401) May 19 10:44:47 xo-ce xo-server[79847]: 2026-05-19T10:44:47.602Z xo:rest-api:error-handler INFO [DELETE] /events/cd7bcc9d-15ba-4ce0-b31e-5d8798a4ff2e/subscriptions> May 19 10:44:50 xo-ce xo-server[79847]: 2026-05-19T10:44:50.643Z xo:rest-api:error-handler INFO [GET] /vms/ff7214ce-de09-fe31-bfe9-5994af558ddb/alarms (401) May 19 10:44:50 xo-ce sudo[79915]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=999) May 19 10:44:50 xo-ce sudo[79915]: xo-service : PWD=/opt/xen-orchestra/packages/xo-server ; USER=root ; COMMAND=/usr/bin/mount -o -t nfs 10.100.2.23:/volume1/bac> May 19 10:44:50 xo-ce sudo[79916]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=999) May 19 10:44:50 xo-ce sudo[79916]: xo-service : PWD=/opt/xen-orchestra/packages/xo-server ; USER=root ; COMMAND=/usr/bin/mount -o -t nfs 10.100.2.23:/volume1/Bac> May 19 10:44:50 xo-ce sudo[79915]: pam_unix(sudo:session): session closed for user root May 19 10:44:50 xo-ce sudo[79916]: pam_unix(sudo:session): session closed for user root May 19 10:45:09 xo-ce xo-server[79847]: 2026-05-19T10:45:09.413Z xo:rest-api:error-handler INFO [GET] /vms/138538a8-ef52-4d0a-4433-5ebb31d7e152/alarms (401) May 19 10:45:10 xo-ce xo-server[79847]: 2026-05-19T10:45:10.197Z xo:rest-api:error-handler INFO [GET] /backup-repositories (401) May 19 10:45:10 xo-ce xo-server[79847]: 2026-05-19T10:45:10.197Z xo:rest-api:error-handler INFO [POST] /events/cd7bcc9d-15ba-4ce0-b31e-5d8798a4ff2e/subscriptions (> May 19 10:45:15 xo-ce xo-server[79847]: 2026-05-19T10:45:15.187Z xo:rest-api:error-handler INFO [GET] /schedules (401) lines 33-75/75 (END)

So the scheduled backup at 1pm this afternoon ran with no issue. As stated previously the Coalesces are adding now now show 2 for vm. edit - Apr 21 11:22:55 xo-ce xo-server[15617]: }, Apr 21 11:22:55 xo-ce xo-server[15617]: summary: { duration: '6m', cpuUsage: '4%', memoryUsage: '29.01 MiB' } Apr 21 11:22:55 xo-ce xo-server[15617]: } Apr 21 13:00:00 xo-ce xo-server[16924]: 2026-04-21T17:00:00.320Z xo:backups:worker INFO starting backup Apr 21 13:00:00 xo-ce sudo[16938]: xo-service : PWD=/opt/xen-orchestra/packages/xo-server ; USER=root ; COMMAND=/usr/bin/mount -o -t nf> Apr 21 13:00:00 xo-ce sudo[16938]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=996) Apr 21 13:00:00 xo-ce sudo[16938]: pam_unix(sudo:session): session closed for user root Apr 21 13:00:06 xo-ce xo-server[16924]: 2026-04-21T17:00:06.941Z xo:backups:MixinBackupWriter INFO deleting unused VHD { Apr 21 13:00:06 xo-ce xo-server[16924]: path: '/xo-vm-backups/138538a8-ef52-4d0a-4433-5ebb31d7e152/vdis/9f7daac4-80a1-41f9-8af0-99b6fe> Apr 21 13:00:06 xo-ce xo-server[16924]: } Apr 21 13:00:19 xo-ce xo-server[16924]: 2026-04-21T17:00:19.536Z xo:backups:MixinBackupWriter INFO deleting unused VHD { Apr 21 13:00:19 xo-ce xo-server[16924]: path: '/xo-vm-backups/6d733582-0728-b67c-084b-56abe6047bfc/vdis/9f7daac4-80a1-41f9-8af0-99b6fe> Apr 21 13:00:19 xo-ce xo-server[16924]: } Apr 21 13:01:23 xo-ce xo-server[16924]: 2026-04-21T17:01:23.971Z xo:backups:worker INFO backup has ended Apr 21 13:01:23 xo-ce sudo[16971]: xo-service : PWD=/opt/xen-orchestra/packages/xo-server ; USER=root ; COMMAND=/usr/bin/umount /run/xo-> Apr 21 13:01:23 xo-ce sudo[16971]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=996) Apr 21 13:01:23 xo-ce sudo[16971]: pam_unix(sudo:session): session closed for user root Apr 21 13:01:24 xo-ce xo-server[16924]: 2026-04-21T17:01:24.029Z xo:backups:worker INFO process will exit { Apr 21 13:01:24 xo-ce xo-server[16924]: duration: 83708608, Apr 21 13:01:24 xo-ce xo-server[16924]: exitCode: 0, Apr 21 13:01:24 xo-ce xo-server[16924]: resourceUsage: { Apr 21 13:01:24 xo-ce xo-server[16924]: userCPUTime: 31147905, Apr 21 13:01:24 xo-ce xo-server[16924]: systemCPUTime: 14319055, Apr 21 13:01:24 xo-ce xo-server[16924]: maxRSS: 65888, Apr 21 13:01:24 xo-ce xo-server[16924]: sharedMemorySize: 0, Apr 21 13:01:24 xo-ce xo-server[16924]: unsharedDataSize: 0, Apr 21 13:01:24 xo-ce xo-server[16924]: unsharedStackSize: 0, Apr 21 13:01:24 xo-ce xo-server[16924]: minorPageFault: 367979, Apr 21 13:01:24 xo-ce xo-server[16924]: majorPageFault: 1, Apr 21 13:01:24 xo-ce xo-server[16924]: swappedOut: 0, Apr 21 13:01:24 xo-ce xo-server[16924]: fsRead: 5648, Apr 21 13:01:24 xo-ce xo-server[16924]: fsWrite: 16101272, Apr 21 13:01:24 xo-ce xo-server[16924]: ipcSent: 0, Apr 21 13:01:24 xo-ce xo-server[16924]: ipcReceived: 0, Apr 21 13:01:24 xo-ce xo-server[16924]: signalsCount: 0, Apr 21 13:01:24 xo-ce xo-server[16924]: voluntaryContextSwitches: 65983, Apr 21 13:01:24 xo-ce xo-server[16924]: involuntaryContextSwitches: 7745 Apr 21 13:01:24 xo-ce xo-server[16924]: }, Apr 21 13:01:24 xo-ce xo-server[16924]: summary: { duration: '1m', cpuUsage: '54%', memoryUsage: '64.34 MiB' } Apr 21 13:01:24 xo-ce xo-server[16924]: } lines 617-656/656 (END)

@MathieuRA said: Hi, regarding your backups which do not appear on the XO5 restore page, I suggest you to open a new topic Forgot to include the link to the new topic https://xcp-ng.org/forum/topic/12040/restore-only-showing-1-vm

@gregbinsd let us know. If you do use my script. It pulls nodejs from NodeSource so it may not install the latest 24.15.0 tls. If you specific 24.15.0 it will install that version. If you need to change node version with my script use the rebuild option.

@Pilow While that could be true only 1 vm was shuffled to another SR. But all VMs now being backup with CBT enabled. Well... i just check again at backups and after the last scheduled backup at 1am all vms fell back to full backup again.

Hi @acebmxer, I've made some tests with a small infrastructure, which helped me understand the behaviour you encounter. With the performance plan, the load balancer can trigger migrations in the following cases: to better satisfy affinity or anti-affinity constraints if a host has a memory or CPU usage exceeds a threshold (85% of the CPU critical threshold, of 1.2 times the free memory critical threshold) with vCPU balancing behaviour, if the vCPU/CPU ratio differs too much from one host to another AND at least one host has more vCPUs than CPUs with preventive behaviour, if CPU usage differs too much from one host to another AND at least one host has more than 25% CPU usage After a host restart, your VMs will be unevenly distributed, but this will not trigger a migration if there are no anti-affinity constraints to satisfy, if no memory or CPU usage thresholds are exceeded, and if no host has more CPUs than vCPUs. If you want migrations to happen after a host restart, you should probably try using the "preventive" behaviour, which can trigger migrations even if thresholds are not reached. However it's based on CPU usage, so if your VMs use a lot of memory but don't use much CPU, this might not be ideal as well. We've received very few feedback about the "preventive" behaviour, so we'd be happy to have yours. As we said before, lowering the critical thresholds might also be a solution, but I think it will make the load balancer less effective if you encounter heavy load a some point.

No worries, it happens! Glad you found the problem

@acebmxer I’m sorry to say that if those Dells are at your workplace, the wrong edition of iDRAC was purchased. You see with at the very least iDRAC 9 access to the full granular IPMI sensor data, was placed behind an edition paywall by Dell Technologies. Outlet temperature is just one of the feeds, missing from the Enterprise or lower edition of iDRAC 9. You’ll get the temperature readings from the Dell iDRAC web browser based interface, but not IPMI with iDRAC 9 Enterprise. To obtain the full IPMI sensor data you need the Datacenter edition.

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!

@acebmxer not yet (a little under the water with the release patch, but we will do it )

@acebmxer welcome to freedom.

@acebmxer There are older versions of the guest tools still available on Github.

@dinhngtu I think it just have been a bad migration or the Win 11 Template did other things to the windows 10 os. Since new test vm did not show the time issues, and a fresh migration of the vim with correct template selected did not have the issues either. I dont know but maybe there is a way to put detect the correct VM template or make note. I didnt think using the win 11 template would have caused issues since using the "wrong" template on vm creation does not have the same effect.

@florent said in vmware vm migration: @acebmxer yes after the first migration, XO knwo that the migration is incomplete and that you may want to finish it later. But if you start this VM direvtly , it will write some data, thus it won't be in sync anymore with the Vmware snapshot. Then XO won't be able to resume You can start a copy of the VM ( XO will handle it for you ) and delete the copy when you're done My advice is to migrate this VM to the right SR and then do the resume. But keep in mind that the V2V tool is intended to target only one SR, so migrate all they disk to the same SR, and select the right one when resuming the V2V. You can change the network after My previous migration was successful with no issues. Previously test vm was fresh install so no vmtools installed. But I did shut the vm down myself prior to starting the migration. VM boots no issues no prompts. This time I decided to follow the steps listed in the documentation as i have been following the changes and updates for the v2v migration. Following the steps as mention XO presented me with that prompt which was not mention in the documentation. As i was typing the post to gather my information it was then i noticed i did not select the proper destination SR and the appropriate nic/vlan for networking. So I noted that in the post. With the assumption i could correct that on the final migration. With that said the I guess the documentation should state - Start vm to test if boots, etc.. When prompted choose "Start a copy". When done shutdown vm and remove.

@olivierlambert thank for that. Just to be clear the vm was not runing but shut down if that makes a difference. @ph7 Both firewalls are Unifi Enterprise fortress gateways. - https://techspecs.ui.com/unifi/cloud-gateways/efg?subcategory=all-cloud-gateways Both sites are setup with Site Magic VPN. So should be full 1.1gbps if accurate. [image: 1767705099263-screenshot-2026-01-06-081123.png]

@myles3 Hello Myles3. This post is over 20 days old. The issue was since been resolved by support. I dont remember the exact solution off the top of my head with out looking it up.

@olivierlambert Thank you for the reply. There was a thread on here about the iso not being mounted properly and I commented about having power off the vm and back and it will load the iso. This is specifically true with the 0.4.0 for linux. Image pulled from the XO Hub will not mount the ios if the vm is powered on. There is Yellow Explanation mark next to it. Power off vm and power on vm iso is ok. Reboot vm does not let the ios to work.

@acebmxer Great. These are some YAML basics. You should read more about it . Following AI instructions without understanding is not going to take you far.