It wasn't my first time doing this. Previously I successfully passedthrough FibreChannel HBA to VM.
But I understand your point. This is output form history command. I copied only interesting part:
18 lspci | grep hailo
19 lspci
20 /opt/xensource/libexec/xen-cmdline --set-dom0 "xen-pciback.hide=(0000:08:00.0)"
21 /opt/xensource/libexec/xen-cmdline --get-dom0 xen-pciback.hide
22 reboot
and this is output from lspci -vn
08:00.0 0b40: 1e60:2864 (rev 01)
Subsystem: 1e60:2864
Physical Slot: 3
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at 39ff0604000 (64-bit, prefetchable) [size=16K]
Memory at 39ff0608000 (64-bit, prefetchable) [size=4K]
Memory at 39ff0600000 (64-bit, prefetchable) [size=16K]
Capabilities: [80] Express Endpoint, MSI 00
Capabilities: [e0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [f8] Power Management version 3
Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 Len=008 <?>
Capabilities: [108] Latency Tolerance Reporting
Capabilities: [110] L1 PM Substates
Capabilities: [128] Alternative Routing-ID Interpretation (ARI)
Capabilities: [200] Advanced Error Reporting
Capabilities: [300] #19
Kernel driver in use: pciback
Kernel modules: hailo_pci
As you can see there is hailo_pci kernel module (currently not used). But during my first attempts it was not present, so boot loop was caused without this driver. I only compiled it later during my debugging process.