So, what's happening here is the BOOTIF parameter specifies a MAC of a device, but that device is *not* found; then we see the errors here.
So let's get confirmation that the BOOTIF parameter mac matches with one or more of the interfaces on the system. I recreated this same failure by booting a bionic instance with these parameters: ip=::::amused-guinea:BOOTIF ip6=off BOOTIF=01-00-25-90-4c-f0-38 With a default virio nic whose MAC does not match and I see the exact same output. I repeated that with a Xenial instance and it fails in the same way; so I suspect there's something misconfigured w.r.t the MAC on the boot params; or possible since this is hardware, something is going on with the MAC addrs on the system with the e1000e nics. ** Bug watch added: Red Hat Bugzilla #1525523 https://bugzilla.redhat.com/show_bug.cgi?id=1525523 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761573 Title: Network not configured on bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1761573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
