During boot I get multiple
[FAILED] Failed to start Tell Plymouth To Write Out Runtime Data. messages that seem to be related to the number of Nics attached to the system. the number of these error differs between booting from a poweroff state or a reboot. This appears in the boot sequence where the networking and Nics should be coming online and (Somewhat Randomly) some of the Nics fail to come up correctly.
If I reduce the number of Nics in the system the issue is resolved. Is there a limit to the number of Nics Ubuntu can boot with attached?
The system is as follows:
Ubuntu Server 18.04.4 clean install, Into VM with one "real" Nic passed to it and nine virtual Nics.
The goal is to take the one Trunked Nic and bridge the vLans to the virtual Nics untagged. I'm using netplan to achieve this and it works well as long as I keep the number of vNics low. But if I scale it up it fails to consistently work after reboot or poweroff.
network: version: 2 renderer: networkd ethernets: eth_tohst: dhcp4: true match: # This will be vLan 1 Untagged macaddress: xx:xx:xx:xx:xx:xx set-name: eth_tohst eth_tohst.2: dhcp4: true match: macaddress: xx:xx:xx:xx:xx:xx set-name: eth_tohst.2
and so on for each vNic and the trunked uplink... then I added the vlans to the trunk.
vlans: vlan.2: id: 2 link: eth_uplnk vlan.3: id: 3 link: eth_uplnk
once again for all the vlans and then bridge them...
bridges: br1: dhcp4: true interfaces: [eth_tohst, eth_uplnk] br2: dhcp4: true interfaces: [eth_tohst.2, vlan.2]
Obviously with the correct MAC address and expanded out to match the number of vlans.. With only a couple Nics everything boots up and works as expected.
Thoughts on why this fails to scale up? Or is there a better way I should be going about this?