That would be an interesting lead to see if the issue is triggered by live migrations, this could be a hint on the issue.

Your setup is different enough that folks here might not have hit this exact thing. The Failed to parse ACPI DMAR. Disabling VT-d line usually points at the laptop firmware's ACPI tables rather than anything Xen is doing wrong, which would explain why the grub iommu=1 tweaks aren't moving the needle. You've already cross-posted to the QubesOS forum, which is probably where the people who've wrestled with E15 firmware quirks hang out. If it helps, the XCP-ng docs have a short note on reading the DMAR/IVRS ACPI tables to debug IOMMU issues at https://docs.xcp-ng.org/troubleshooting/log-files#dmarivrs-acpi-tables. It's XCP-ng-specific, but the Xen-level idea of dumping and inspecting those tables carries over.

@unreal-shizzle said: @olivierlambert said: Hi, Somewhere between Q1 and Q2 next year, hard to be more precise My company is desperately looking to get away from VMware because of the predatory pricing. I showed my boss XCP-ng because it looks a lot like ESXi. He looked into the software and asked why XO lite has been "coming soon" for 5 years now. What should I tell him? It may be help to actually look at Xen Orchestra as XO Lite is targeted at basic functions. Anyway network creation is present in Xen Orchestra 5 and/or 6. Maybe more extensive, but will allow for better ACL (via RBAC) capabilities. https://docs.xen-orchestra.com/xo5/sdn_controller#network-creation The pieces are coming together it’s a new software XO Lite, the teams at Vates are growing more of XO Lite is being developed and tested. Though Xen Orchestra is a more suitable base for a business environment, with multiple departments and teams, due to XO Lite only using and allowing the use of root account authentication. The root account of XO Lite refers to the XCP-ng host server administrator account - full access!

@itservices Can you check your health dashboard where you should see " Unhealthy VDIs" ? If there are too many VDI in it, they need to be coalesced before restarting a backup.

@poddingue My colleage managed to workaround the issue by re-installing the lab on other hardware, I think it is now Cisco UCS-servers. It was HP ProLiant-servers before. Maybe it was an issue with some of the NIC or firmware, im not really sure, but it works now.