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.

@nasheayahu Hello, I do this with a my homelab disk since I imported it from a physical machine: mkdir /srv/NAS xe sr-create type=udev sm-config:location=/srv/NAS name-label="NAS Disks" Then you make a symlink to the device: 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> The disk will appear as a VDI in the SR that you can then plug to a VM. I also renamed the VDI [NOSNAP][NOBAK] NAS Drive [NOSNAP][NOBAK] instruct XO to not snapshot and export the disk in backups (since it can't). It's not passthrough, as in the disk is not directly given to the VM, but tapdisk (the process virtualizing storage) will give access to the whole disk to the guest, so it can mount any FS on it. The udevSR is usually used for plugging USB from what I could gather from existing code. But users in homelabs have been using it like this for a while. Though you will likely not have native performance level since it's not exactly passthrough.

Hi @nasheayahu, 1/ are you running the latest XO from source ? 2/ did you follow this to create the ZFS volume => https://docs.xcp-ng.org/storage/#zfs ? 3/ did you try with "ext" type instead ? or your requirement is QCOW2 with ZFS ? The "import QCOW2" is currently not yet implemented, hence the API error (it should have been not permitted actually); it should be merged in the next XO release.

@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.

@simonp I keep asking that about Node version. And every time i was told use the latest LTS which is 24.15... Yet i see 22 being used. I can try later today and report back.

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.

@andrewperry I have support with XOA so will create a ticket.