@s-pam Yikes, thanks for the reply!

@s-pam said in Rename Networks on XO Hosts:

@olivierlambert said in Rename Networks on XO Hosts:

If you use a pool, it's for sharing a network and/or a storage.

If you don't want to share a network across PIFs between hosts, then don't use a pool

I get it. Though I would prefer not having to buy another server when I can run a VM. And in fact it works fine, just naming networks is a little odd at the moment.

What I would like to see is that networks can be connected to different physical nics on different hosts.

I.e. something like this:

Network Management:
Host 1: eth0
Host 2: eth1
Host 3: eth0
Host 4: eth4

Network Someother:
Host 1: eth1
Host 2: n/a
Host 3: eth1
Host 4: eth1

Network Another:
Host 1: eth2
Host 2: eth2
Host 3: eth2
Host 4: eth2

Then in the VM you can assign the "Network" as normal. If the VM is migrated to another host, then XCP-ng would choose the correct PIF/NIC. This can be an advantage where one or several hosts have extra NICs, maybe with higher speeds. But during migration (rolling upgrades, service, or whatnot), the VMs still work but with reduced performance when moved to another host.

Another example would be if we have a spare host off-site/another building where the network layout cannot be fully replicated as in the datacenter.

Did you ever find a solution to this? I'm literally trying to do the same thing because I have hosts with uneven numbers of NICs...