How to deal with SAN boot
olivierlambert opened this issue · comments
Quick question for you @robhoes 😉
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).