@olivierlambert: kudos to the XCP-ng team and congratulation for achieving the first 100K downloads. It is a good sign that XCP-ng is well recognized, giving the product, your services and the community a good reputation. Keep up the good work!

Updated a two node XCP-ng 8.0 homelab without any issues

Don't forget to stop the dynamic NIC naming by adding net.ifnames=0 to the grub boot menu (see this article by Eric Eikrem). Worked for my USB-NIC (Startech, ASIX Electronics Corp. AX88179 USB 3.0 to Gigabit Ethernet) as described in Prevent USB-NIC device renaming - valid approach on xcp-ng?. Not sure if it really is mandatory to add the on-board NIC to the rules file as well, but I do it.

@stormi nice and way to simple - should have read the documentation more carefully

Anyway, did a clean install and update of xcp-ng 8.1 and ran sysbench (sysbench cpu --cpu-max-prime=20000 --threads=4 --time=30 run) without and with the microcode update.
Even with maxing out all threads, there is no noticeable impact on CPU performance on my Intel NUC ( i5-6260U, 2 Cores, 4 Threads).
But mileage may vary with different CPU types.

@stormi updated my homelab / playlab Intel NUC ( i5-6260U, Skylake, XCP-ng 8.1) with no problem.

/var/log/xen/hypervisor.log indeed shows SRBDS_CTRL (log shortend for better reading):

CPU0: Intel machine check reporting enabled
Speculative mitigation facilities:
Hardware features: IBRS/IBPB STIBP L1D_FLUSH SSBD MD_CLEAR SRBDS_CTRL
Compiled-in support: INDIRECT_THUNK SHADOW_PAGING
Xen settings: BTI-Thunk JMP, SPEC_CTRL: IBRS+ SSBD-, Other: SRB_LOCK+ IBPB L1D_FLUSH VERW BRANCH_HARDEN
   L1TF: believed vulnerable, maxphysaddr L1D 46, CPUID 39, Safe address 8000000000
   Support for HVM VMs: MSR_SPEC_CTRL RSB EAGER_FPU MD_CLEAR
   Support for PV VMs: MSR_SPEC_CTRL RSB EAGER_FPU MD_CLEAR
   XPTI (64-bit PV only): Dom0 enabled, DomU enabled (with PCID)
   PV L1TF shadowing: Dom0 disabled, DomU enabled

Using 7zip benchmark on DOM0 (installed from EPEL repository) does not show any significant impact on performance.
Most likely, this benchmark is not that relevant with respect to the affected cpu functions (e.g. random number generation).
Would love to run sysbenchbut have no idea how to install it on XCP-ng.

@olivierlambert: kudos to the XCP-ng team and congratulation for achieving the first 100K downloads. It is a good sign that XCP-ng is well recognized, giving the product, your services and the community a good reputation. Keep up the good work!

You need to enable and configure the backup-reports and transport-email plugin under setting - plugins. backup-reports just needs the recipient mail address. transport-email needs the mail service connection settings in the transport section (you get this settings from your mail provider) and a valid sender mail address.

When you configure a backup job, you can then choose when you want to receive a notification (settings block bottom left). Settings are self explanatory (Always vs. Failure). That's it and I hope it helped.

@borzel: I second that! From time to time, I try to move over to XOA, but I always keep coming back to XCP-ng Center. XCP-ng Center supports my administrative tasks in a straight forward way (at least apart from backups ) and gives me all the information I need. Thank's for doing a great job!

Updated a two node XCP-ng 8.0 homelab without any issues

I wonder if the backup (and restore) traffic is going through XO (on the management network) or does XO advise the xcp-ng host where the backup remote store (on the storage network) is, so that the traffic stays on the storage network? Read some articles on the XO forum and the internet, but did not get a clear picture on the recommended architecture.