Yes… after the container stop/start and the error, ip link showed the host machine had eno1 and eth1 but not eno2. I guess the internal logic of LXD needs to ‘undo’ the passthrough when the container is stopped … so the host again would show eno2 and when the container is started eno2 is once again available to be exclusively assigned.
–edit: When the process worked correctly, stopping the container with lxc stop it DID correctly return eno2 to the host, so that’s good.
–edit2:
Regadring my own question of creating the container with host physical nic, if the profile is:
devices:
eth0:
name: eth0
nictype: physical
parent: eno2
type: nic
seems to have worked!