@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

@julienXOvates said: 1/ are you running the latest XO from source ? Yes, I used the Xen Orchestra Installer / Updater on a Debian 13. @julienXOvates said: 2/ did you follow this to create the ZFS volume => https://docs.xcp-ng.org/storage/#zfs ? No, I have 3 extra 2TB HDs I did not include in the install, because I have data on them I want to move to a Storage Device first. @julienXOvates said: 3/ did you try with "ext" type instead ? or your requirement is QCOW2 with ZFS ? I just tried it, but it requires an another device I don't have available as stated above. The QCOWS are coming from the two Redhat 10 Server/Workstations, 1) I just converted to XCO-ng, 2) the other Redhat will convert soon after solving other setup tasks with the first.

@limezest said: ISOs in my NFS ISO SR The simplest way to correct those is to forget the VDI and then rescan the SR. Note: The ISO names will be lost if they were uploaded via XOA, which causes them to be renamed to .IMG files.

I managed to down grade to node 22.22.3 and still same issue. Its seem better on node 22.22.3 but still an issue.

Hi @mdm, Here is the response from a SME 1- XO get the VM metadata through soap api and create the vm /network XO use the nbdkit + nbdkit-vddk package , connecting to each disk XO connect through NBD to nbdkit XO list the allocated blocks XO create the disk XO read the block and import the data into the disk (though a vhd or qcow2 stream depending on the size) 2- though XO. There is a lot of disk transform occuring here 3- not anymore, it was too brittle, especially on when the disk are locked or not. Also it was not scaling too well 4- see 3- + vddk transfer is overwhelmly faster that previous access through http, is compatible with VSAN and don't lock the disks. (+ also see https://xen-orchestra.com/blog/xen-orchestra-5-110/ section "VMware to Vates (V2V)" where we made key improvements)

@taghjichte From my testing you would need to passthought a device for audio. If need for professional audio work then yes a pci passthough would be the perferred option. With that said. @dinhngtu As for sound I have never looked much into it but the only vm I heard make sound is from Fedora even while booted from install iso. Kubuntu or windows with xen drivers installed no audio. (find for me at the moment) While audio seems to work in Fedora from iso it seems to be limited to left channel. Local system is connected to 5.1 sound.

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

@tsukraw I am taking the ticket and will keep you informed as soon as possible

@JL457 Hi, For now it looks like Wasabi is not sending us the correct date format, which is strange because we support this provider and don't usually have issues. In order to allow us to investigate further, could you send us the full backup job logs ? You can find them by clicking on the failed backup status and then on the download logs button: [image: 1779106635704-export-logs.png] Relevant XO logs would also help. If you are a client, also don't hesitate to open a ticket with an open support tunnel. Thanks.