We got a use case for a "complex" deployment using a "bare metal cloud" provider. In this case, we need to:
boot in UEFI
using iPXE (we chainload to Grub2, then Xen)
on iSCSI (SAN) for system drives
We managed to get it until host boot (also we improved our doc for this!). However, as soon xcp-networkd started, it's taking control on NICs, and cut the iSCSI connection.
Is there a way to tell xcp-networkd to leave the iSCSI NIC alone? (here, eth0 is the dedicated iSCSI NIC, and eth1 management).
Quick question for you @robhoes :wink:
We got a use case for a "complex" deployment using a "bare metal cloud" provider. In this case, we need to:
We managed to get it until host boot (also we improved our doc for this!). However, as soon
xcp-networkdstarted, it's taking control on NICs, and cut the iSCSI connection.Is there a way to tell
xcp-networkdto leave the iSCSI NIC alone? (here,eth0is the dedicated iSCSI NIC, andeth1management).