Time="" level=debug msg="runCmds(on eth0): " Time="" level=debug msg="Config: &netconf.NetworkConfig" Time="" level=info msg="Apply Network Config" On rancheros instance running under VirtualBox you ~]$ cat /var/log/boot/netconf.log What do the rancheros boot logs show ( /var/log/boot/netconf.logĪs you are using ESXI, why rely on nested virtualisation? Why not set up a separate rancher VM directly under ESXI? NIC type used was e1000 on FreeNAS and of course in rancheros. This test FreeNAS VM was created with CPU set to "host-passthrough" on a debian host set up for nested-virtualisation, whch might explain why rancheros sees this as "Booting paravirtualized kernel on bare hardware". Inet6 fe80::42:deff:fe12:7312/64 scope linkħ: mtu 1500 qdisc noqueue master docker0 state UP group default Inet6 fe80::446a:10ff:fe20:166b/64 scope linkĥ: docker0: mtu 1500 qdisc noqueue state UP group default
#Setup nested esxi mac pro 1.1 driver
VMware vmxnet3 virtual NIC driver - version ~]$ ip a Booting paravirtualized kernel on bare hardware CPU MTRRs all blank - virtualized system. Ifmaxaddr 0 port 3 priority 128 path cost 2000000 Ifmaxaddr 0 port 1 priority 128 path cost 20000 Maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 Inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 Valid_lft forever preferred_lft ~]$ ip route showġ72.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdownġ72.18.0.0/16 dev docker-sys proto kernel scope link src 172.18.42.2 linkdownġ92.168.1.0/24 dev eth0 proto kernel scope link src # ifconfig Inet6 fe80::90d5:d9ff:fe6f:369f/64 scope linkĥ: docker0: mtu 1500 qdisc noqueue state DOWN group default Inet6 fe80::2a0:98ff:fe48:1a03/64 scope linkģ: docker-sys: mtu 1500 qdisc noqueue state DOWN group default qlen 1000 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1