I'd start with checking the usual logs (notably xensource.log) when the issue happens.
See https://docs.xcp-ng.org/troubleshooting/log-files/
Yes, I know, getting logs about an issue getting logs. Of course, I mean checking them via CLI on XCP-ng hosts :).
@MJGZ51 said in XCP-ng 8.3 PCI Passthrough issue:
For anyone experiencing this issue, it happens when you enable Passthrough via CLI (hide devices from DOM).
After a clean install of xcp-ng 8.3, Passthrough would work via XOA GUI. However, as soon as I enabled PCI Passthrough for a device via CLI, the errors appeared.
I've moved to just passing the devices via GUI and not CLI. Everything is now working.
What's the involved CLI command?
@markxc said in create a new vm using a iso setting cpu ram network via api:
Out of curiosity: how do you handle the Xen Orchestra appliance installation?
We use Packer, a Debian iso and an Ansible playbook in the ansible provisioner. See https://developer.hashicorp.com/packer/integrations/hashicorp/ansible/latest/components/provisioner/ansible
With this setup, we achieve these tasks:
We also have a CI/CD pipeline doing this automatically.
@archw It's written in the blog post 
