XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. Popular
    Log in to post
    • All Time
    • Day
    • Week
    • Month
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics

    • All categories
    • stormiS

      XCP-ng 8.3 updates announcements and testing

      Watching Ignoring Scheduled Pinned Locked Moved News
      525
      1 Votes
      525 Posts
      232k Views
      dthenotD
      @Andrew Hello, I'm also getting error on some VMs while trying to export a disk and also trying to even start some VMs from NFS (that were fine before). Is it still a problem? It might have multiple causes. If it's still an issue, could you share the logs: /var/log/{SMlog,xensource.log,daemon.log}. It contains information that could help us investigate. The VDI not detached cleanly means that the VDI still has a reference to the host it was running on before. It's might be caused by the xenopsd error earlier or maybe it's the cause. If you are sure no tapdisk are using the VDI, you can look at tap-ctl list output on each host. You can clean this reference with the script in /opt/xensource/sm/resetvdis.py single <VDI UUID>.
    • W

      VDI not showing in XO 5 from Source.

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Management
      49
      2
      0 Votes
      49 Posts
      6k Views
      A
      Just an update here that Vates were able to fix my pool. I assume they used the script that was just uploaded so if any one is wondering the impact, it should be fine.
    • N

      Create a new SR: qcow2 failure

      Watching Ignoring Scheduled Pinned Locked Moved Management
      6
      7
      0 Votes
      6 Posts
      119 Views
      N
      @julienXOvates said: so you're actually trying to import those QCOW2 VDIs, not creating them, right ? Yes... @julienXOvates said: You'll have to wait for the import feature for QCOW2 which is coming soon. You should be able to create a brand new SR with QCOW2, but be aware of the known issue on ZFS with large VDIs Okay... @julienXOvates said: Did you install ZFS on your host ? I installed XCP-ng using the defaults and recommended settings, I do not remember if ZFS was a default: [09:28 xcp-kbbn ~]# df -Th Filesystem Type Size Used Avail Use% Mounted on devtmpfs devtmpfs 3.6G 16K 3.6G 1% /dev tmpfs tmpfs 3.6G 316K 3.6G 1% /dev/shm tmpfs tmpfs 3.6G 9.3M 3.6G 1% /run tmpfs tmpfs 3.6G 0 3.6G 0% /sys/fs/cgroup /dev/sdb1 ext3 18G 2.1G 15G 13% / /dev/sdb4 vfat 512M 3.3M 509M 1% /boot/efi /dev/sdb5 ext3 3.9G 88M 3.6G 3% /var/log 192.168.130.102:/media/KbbnNFS04/ITDocuments/ITDocuments/Iso nfs 1.9T 259G 1.6T 14% /run/sr-mount/d7f0d912-ddc4-ab46-6693-39a6b0d49a14 /dev/mapper/XSLocalEXT--d318a008--a239--821f--a9cd--1f1b657e492e-d318a008--a239--821f--a9cd--1f1b657e492e ext4 2.6T 30G 2.5T 2% /run/sr-mount/d318a008-a239-821f-a9cd-1f1b657e492e tmpfs tmpfs 731M 0 731M 0% /run/user/0 [09:28 xcp-kbbn ~]# lsblk -f NAME FSTYPE LABEL UUID MOUNTPOINT sdf LVM2_member nl8bHb-caA4-aw3k-S1c2-rm3h-zfXc-4urbyC └─XSLocalEXT--d318a008--a239--821f--a9cd--1f1b657e492e-d318a008--a239--821f--a9cd--1f1b657e492e ext4 9cf95f7d-249b-45e3-9584-a02f1b2a367a /run/sr-mount/d318a008-a239-821f-a9cd-1f1b657e492e sdd xfs KbbnNFS03 3ff0be13-df43-455f-8af5-bb5278378279 sdb ├─sdb4 vfat BOOT-TZOZOJ 1B19-9FAC /boot/efi ├─sdb2 ├─sdb5 ext3 logs-tzozoj d09535b9-cd49-4bac-8aeb-17872bda910e /var/log ├─sdb3 LVM2_member 0kSCqD-PNaB-0E2Q-xJ1o-rvTW-NAC0-zEzM6D │ └─XSLocalEXT--d318a008--a239--821f--a9cd--1f1b657e492e-d318a008--a239--821f--a9cd--1f1b657e492e ext4 9cf95f7d-249b-45e3-9584-a02f1b2a367a /run/sr-mount/d318a008-a239-821f-a9cd-1f1b657e492e ├─sdb1 ext3 root-tzozoj 70792b7e-b92d-4913-a2cc-4ed6f8fe014e / └─sdb6 swap swap-tzozoj 46d5a332-2728-452e-9c30-1e837fb6cf25 [SWAP] tdc tda sde LVM2_member xRwg78-m9o1-mGki-KfO7-MSY3-gLjD-UKZjQo └─XSLocalEXT--d318a008--a239--821f--a9cd--1f1b657e492e-d318a008--a239--821f--a9cd--1f1b657e492e ext4 9cf95f7d-249b-45e3-9584-a02f1b2a367a /run/sr-mount/d318a008-a239-821f-a9cd-1f1b657e492e sdc xfs KbbnNFS02 765ca566-c434-45a5-9b9f-f066c770a7d4 sda xfs KbbnNFS01 a91987c0-1c2e-4e88-bcf6-fe7662e77cb6 tdd tdb but you can see sd(a,d,c) are from the 3 HDs I did not include in the install are ZFS, I attached them as SRs so I can move the data later to a Storage Device using this method: [15:27 xcp-kbbn NAS]# xe host-list uuid ( RO) : 9a5e5bb3-bdb9-41ea-9505-6f6fe630f369 name-label ( RW): xcp-kbbn ----------------------------- Disk NAS ----------------------------- xe sr-create type=udev device-config:location=/srv/NAS name-label="NAS Disks" host-uuid=9a5e5bb3-bdb9-41ea-9505-6f6fe630f369 1) [16:08 xcp-kbbn srv]# xe sr-create type=udev device-config:location=/srv/NAS name-label="NAS Disks" host-uuid=9a5e5bb3-bdb9-41ea-9505-6f6fe630f369 929ccfc5-b810-89c4-1cdd-e9ee77f38bcf ----------------------------- Disk KbbnNFS01 ----------------------------- 2) ln -s /dev/sda /srv/NAS/sda #although it might be better to use a stable identifier if you have multiple disks 3) xe sr-scan uuid=929ccfc5-b810-89c4-1cdd-e9ee77f38bcf (info from fdisk -l) Disk /dev/sda: 2000.4 GB, 2000398934016 bytes, 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes ----------------------------- Disk KbbnNFS03 ----------------------------- 2) ln -s /dev/sdd /srv/NAS/sdd #although it might be better to use a stable identifier if you have multiple disks 3) xe sr-scan uuid=929ccfc5-b810-89c4-1cdd-e9ee77f38bcf (info from fdisk -l) Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes, 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes ----------------------------- Disk KbbnNFS02 ----------------------------- 2) ln -s /dev/sdc /srv/NAS/sdc #although it might be better to use a stable identifier if you have multiple disks 3) xe sr-scan uuid=929ccfc5-b810-89c4-1cdd-e9ee77f38bcf (info from fdisk -l) Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes, 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes and both systems (well be converting the other one later) are Redhat 10s formatted with ZFS, and was importing from the other Redhat. Well this be a and/or the reason for the import failure?
    • N

      Attach a Physical HD to a VM?

      Watching Ignoring Scheduled Pinned Locked Moved Management
      6
      0 Votes
      6 Posts
      101 Views
      N
      @dthenot said: you will also likely need to give the host-uuid of the host the disk is on Thanks, and I'm assuming this UUID or Machine ID from: [14:45 xcp-kbbn NAS]# dmidecode --type SYSTEM # dmidecode 3.0 Getting SMBIOS data from sysfs. SMBIOS 3.3.0 present. # SMBIOS implementations newer than version 3.0 are not # fully supported by this version of dmidecode. Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: ASUS Product Name: System Product Name Version: System Version Serial Number: System Serial Number UUID: E7AE9723-CB08-A278-5C45-7C10C9473BD0 Wake-up Type: Power Switch SKU Number: SKU Family: To be filled by O.E.M. OR [12:46 xcp-kbbn NAS]# hostnamectl Static hostname: xcp-kbbn Icon name: computer-desktop Chassis: desktop Machine ID: c668f529e66c42b9815fe12f3401df82 Boot ID: dd70b200b25341c688aee9fbc58d20a2 Virtualization: xen Operating System: XCP-ng 8.3 Kernel: Linux 4.19.0+1 Architecture: x86-64 the command would look like this correct: xe sr-create type=udev device-config:location=/srv/NAS name-label="NAS Disks" host-uuid=E7AE9723-CB08-A278-5C45-7C10C9473BD0 or c668f529e66c42b9815fe12f3401df82 UPDATE: I tried the new command but I got these error messages: [14:45 xcp-kbbn NAS]# xe sr-create type=udev device-config:location=/srv/NAS name-label="NAS Disks" host-uuid=E7AE9723-CB08-A278-5C45-7C10C9473BD0 The uuid you supplied was invalid. type: host uuid: E7AE9723-CB08-A278-5C45-7C10C9473BD0 [15:14 xcp-kbbn NAS]# ls [15:19 xcp-kbbn NAS]# xe sr-create type=udev device-config:location=/srv/NAS name-label="NAS Disks" host-uuid=c668f529e66c42b9815fe12f3401df82 The uuid you supplied was invalid. type: host uuid: c668f529e66c42b9815fe12f3401df82 then I was successful (I believe with you confirmation) when I left our the host-uuid param: [15:19 xcp-kbbn NAS]# xe sr-create type=udev device-config:location=/srv/NAS name-label="NAS Disks" b802722e-67ac-5aba-8d6c-e565d2d7fa0d and then it was listed as a SR: [image: 1779139583485-screenshot-from-2026-05-18-15-24-03.png] now to the next task command: xe sr-scan uuid=b802722e-67ac-5aba-8d6c-e565d2d7fa0d was successful, but I have another Question, the size of the device is not showing, is this normal being that it was done this way? UPDATE 2.0: I just discovered the xe command: [15:27 xcp-kbbn NAS]# xe host-list uuid ( RO) : 9a5e5bb3-bdb9-41ea-9505-6f6fe630f369 name-label ( RW): xcp-kbbn the uuid does not match the ones provided above, do I need to remove the SR and do it over again using this uuid? I will give it a try using another folder.... UPDATE 2.1: I executed the command using the above uuid: [15:35 xcp-kbbn srv]# xe sr-create type=udev device-config:location=/srv/NAS name-label="NAS Disks" host-uuid=9a5e5bb3-bdb9-41ea-9505-6f6fe630f369 6fc531a0-19a0-b9c1-c78e-c687fce5ff84 and was successful, but now my question for the device size, is it normal or not due to creating it this way? UPDATE 2.2: I forgot to do: ln -s /dev/sda /srv/NAS/sda #although it might be better to use a stable identifier if you have multiple disks xe sr-scan uuid=<UUID of the udev SR> be right back..... UPDATE 3.0: Success, I have all HDs attached to my VM, access all files and the sizes are reported! : [image: 1779147782991-screenshot-from-2026-05-18-17-25-38.png] List of attached disks: [image: 1779147797114-screenshot-from-2026-05-18-17-18-07.png] The VM: [image: 1779148373193-screenshot-from-2026-05-18-17-51-19.png] Thanks for your help!...
    • acebmxerA

      Some dashboard loading issues with v6

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      7
      5
      0 Votes
      7 Posts
      156 Views
      acebmxerA
      @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)
    • Y

      Test results for Dell Poweredge R770 with NVMe drives

      Watching Ignoring Scheduled Pinned Locked Moved Hardware
      27
      7
      0 Votes
      27 Posts
      5k Views
      Y
      @yllar @mik @Pilow @marcvds Hello, we think we now understand better this issue. We think it's a Xen issue with regard to PCI devices on segment 0001 (which is your case) and not a dom0 driver issue. Could you give a try to this ISO installer please? Please note that this is a custom test ISO and it is therefore not officially supported, do not use it for production, it is just to confirm that it fixes your issue, we will release a supported ISO in the future (target date for now is June). unsupported test ISO for you to test: https://nextcloud.vates.tech/index.php/s/iHf8sqq39EqE683 Regards, Yann
    • maximsachsM

      XCP-ng 8.3: Broadcom BCM57414 `bnxt_en` Driver Fails to Probe on HPE DL380a Gen12

      Watching Ignoring Scheduled Pinned Locked Moved Hardware
      9
      2 Votes
      9 Posts
      651 Views
      Y
      Hello @maximsachs, on top of trying what @thierryescande told you, could you also give a try to this ISO installer please? We have done some internal investigations and we think that the issue could be because of an issue in Xen handling of PCI devices that are on 0001 segment which seems to be your case. Please note that this is a custom test ISO and it is therefore not officially supported, do not use it for production, it is just to confirm that it fixes your issue, we will release a supported ISO in the future (target date for now is June). unsupported test ISO for you to test: https://nextcloud.vates.tech/index.php/s/iHf8sqq39EqE683 Regards, Yann
    • johnnezeroJ

      Server Admin Guide: A Tale of Two Servers: BIOS, GPU, and NUMA Tuning for XCP-ng: Preserving the valuable work done by Tobias Kreidl (@tjkreidl)

      Watching Ignoring Scheduled Pinned Locked Moved Hardware
      4
      2 Votes
      4 Posts
      125 Views
      tjkreidlT
      @poddingue said: This is great to see, thank you for taking the time to rescue this; and thanks to @john.c for the recovery work and to @tjkreidl for writing it in the first place. I went looking, and there is a small XCP-ng-specific piece on this in the official docs under NUMA affinity (https://docs.xcp-ng.org/compute#numa-affinity), but it's nothing like the depth of the Tale of Two Servers series, so having the originals archived is genuinely useful. I won't pretend to judge how much of the 2019 BIOS and GPU-scheduler guidance still maps cleanly onto current hardware and XCP-ng versions; others here will know where it's aged and where it hasn't. I'll make sure this is on our radar on the docs side, because it keeps coming up. Really appreciate you keeping this from disappearing. Thank you kindly for your positive comments and appreciation. To me, it's amazing how some information can stay relevant for long periods of time, even given the rapid state of evolution in the technology sectors. I will try to get the full HTML docs uploaded soon, as well. There are a number of other XenServer articles I discovered a while back on a Polish server, and will see what else I can retrieve. My original avocation for 15 years was that of an astronomer, so research is in my blood and diving into specific issues and doing extensive testing have always been a big part of my motivation to better understand as well as share knowledge.
    • M

      Questions About ESXi to XCP-ng Migration Methods (VDDK vs Non-VDDK)

      Watching Ignoring Scheduled Pinned Locked Moved Solved Migrate to XCP-ng
      4
      0 Votes
      4 Posts
      95 Views
      M
      @julienXOvates Thanks for the quick reply, that’s very helpful!