Its a start of something great, need more functions though! For example:

• VM controls (start/stop)
• VM Information
• VM Import/Export
• Add/remove storage
• SR Information
• Insert/remove dvd
• Toolstacksrestart
• Warnings (low memory/storage space)

@gawlo if you can reboot then you can try, but if the process is started after the reboot, it will still block your mountpoint.

And the mountpoint is the result of this command

xe pbd-param-get param-name=device-config uuid=44e9e1b7-5a7e-8e95-c5f1-edeebbc6863c

@technot when you say performance was a bit on the low end when dom0 handled the drive, how low compared to when the controller is passthrough?

For ZFS, it is still good with few number of disks but the performance won't be high than raid10 until you have more vdevs (which means striping across multiple vdevs). You do need to passthrough the disks to dom0, so you'll have to destroy the raid as you mentioned and the more ram the better for ZFS, usually around 1GB per 1TB of storage for good caching performance.

One thing to note, you can't use ZFS for dom0 yet so you still need another drive for XCP-ng.

@gawlo to check mountpoint as olivier suggested

lsof +D /mountpoint

@gawlo have you try restarting the host? may be check if xapi service is running

systemctl status xapi.service

Machine type? Are you talking about QEMU stuff? If so that is only for emulation, XCP-ng is virtualization so you get the same hardware in your VM as the physical hardware on your host.

You can use the following command to display all the PCI devices being passthrough, and then just set them up again without the one you want to remove.

/opt/xensource/libexec/xen-cmdline --get-dom0 xen-pciback.hide

@kdm

The 2nd option is basically forcing the static IP through XCP-ng, if you have SSH access to your XOA VM then you can also use option 3 (hint: XOA is based on debian 10).

The steps for option 2 are:

• SSH into your XCP-ng host that XOA VM is running on.
• Use this command to find out your XOA VM's VIF UUID

xe vif-list vm-uuid=<UUID of your XOA VM>

• Use this command to set static IP for your XOA VM

xe vif-configure-ipv4 uuid=<UUID of your XOA VM VIF> mode=static address=<IP address/Subnet mask> gateway=<Gateway address>

There is so much you can do through a web browser, I think your best bet is to click SSH or SSH as... to open up putty instead.

While we're at it, most CPU icons have "legs" on 4 sides, and RAM icons have "legs" on 2 sides, the current CPU icon looks like RAM chips instead

@Vinylrider your understanding is correct, delta retention is just how many deltas to keep before merging the oldest delta with the full. Full backup interval is the time between each new full back up for use in case of corrupted back up.

To answer your question, yes it is recommended to have more than 1 full back up to fall back to in the event of corruption espcially of delta backups since delta backups rely on previous deltas meaning if one of your delta is corrupted, you'll loose all data from that point onward until another full backup is made, or worse your full backup could be corrupted (more likely because of the file size) then you loose the whole chain. And if your corrupted delta is merged with the full, you'll probably have a corrupted chain aswell.

@stevezemlicka are you using XO from sources? It looks like permission issue when creating local mount point, have you granted access to the user?