Subcategories

• Management

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

  4k Posts

  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?
• Advanced features

  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.
• Backup

  All XO backup features: full and incremental, replication, mirrors...
  504 Topics

  5k Posts

  F

  the last rewrite of the stream processing ( spring 2025 ) focused on stability and memory footprint, and , on a standard cpu, it tops at around 300MB/s per backup job. Your benchmarks are very interesting, and they confirm most of it. this limit was not really an issue since, in most case the xapi was limiting around 100MB/s per disk , but it will be more a more visible limit Note that master have some fixes on the memory usage (not related to backups) That's why we have started an internal workforce focused on performance, with all the teams from the kernel to the backups, including storage, network and xapi. If I can brag a little : [image: 1779106650898-afd7b59b-a4f0-4a92-88ee-2c7ba52d18bf-image.jpeg] i9 , nvme disk , backup to a nvme disk in passthrough, xoa and vm are on the same host, so it's quite far from real world data, but it shows where the limit is
• REST API

  Everything related to Xen Orchestra's REST API
  85 Topics

  633 Posts

  D

  @florent OK cool, thank you for the info.
• Infrastructure as Code

  Terraform, Packer or any tool to do IaC
  50 Topics

  470 Posts

  C

  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