Virtualization issues w/ recent images

[Philip Prindeville]

Hi,

I built an image today for x86_64/generic with a recent sync to master on openwrt and packages.

I dd'd the image (squashfs-combined) to the raw disk, zero padded the disk to grow it, and booted.

The VM comes up with the following devices:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000\    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ip6tnl0 at NONE: <NOARP> mtu 1452 qdisc noop state DOWN mode DEFAULT group default qlen 1000\    link/tunnel6 :: brd :: permaddr 6efb:55c3:e992::
3: tunl0 at NONE: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000\    link/ipip 0.0.0.0 brd 0.0.0.0
4: sit0 at NONE: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000\    link/sit 0.0.0.0 brd 0.0.0.0
5: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000\    link/ether 96:e1:89:d6:a2:3e brd ff:ff:ff:ff:ff:ff
6: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000\    link/ether 52:54:00:e0:53:8c brd ff:ff:ff:ff:ff:ff
7: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000\    link/ether 52:54:00:b0:7f:fa brd ff:ff:ff:ff:ff:ff
8: gre0 at NONE: <NOARP> mtu 1476 qdisc noop state DOWN mode DEFAULT group default qlen 1000\    link/gre 0.0.0.0 brd 0.0.0.0
9: gretap0 at NONE: <BROADCAST,MULTICAST> mtu 1462 qdisc noop state DOWN mode DEFAULT group default qlen 1000\    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
10: erspan0 at NONE: <BROADCAST,MULTICAST> mtu 1450 qdisc noop state DOWN mode DEFAULT group default qlen 1000\    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
11: ip6gre0 at NONE: <NOARP> mtu 1448 qdisc noop state DOWN mode DEFAULT group default qlen 1000\    link/gre6 :: brd :: permaddr e61c:48fa:cb53::
12: teql0: <NOARP> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 100\    link/void 


But looking at the console:

[    4.063546] igbvf: Intel(R) Gigabit Virtual Function Network Driver
[    4.065506] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
[    4.075553] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver
[    4.077456] ixgbe: Copyright (c) 1999-2016 Intel Corporation.
[    4.081776] ixgbevf: Intel(R) 10 Gigabit PCI Express Virtual Function Network Driver
[    4.084057] ixgbevf: Copyright (c) 2009 - 2018 Intel Corporation.
[    4.101502] ixgbevf 0000:00:03.0: 52:54:00:e0:53:8c
[    4.103049] ixgbevf 0000:00:03.0: MAC: 4
[    4.104268] ixgbevf 0000:00:03.0: Intel(R) 82599 Virtual Function
[    4.121116] ixgbevf 0000:00:04.0: 52:54:00:b0:7f:fa
[    4.122630] ixgbevf 0000:00:04.0: MAC: 4
[    4.123839] ixgbevf 0000:00:04.0: Intel(R) 82599 Virtual Function
...
[    6.538991] 8021q: adding VLAN 0 to HW filter on device eth0
[    6.541444] ixgbevf 0000:00:03.0: NIC Link is Up 10 Gbps
[    6.542867] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready


It seems like "eth0" is only ever getting tickled, not "eth1".

Is there a way to debug this and figure out what's going on?

I can bring up the interface just fine manually:


root at OpenWrt-bios2:~# ip addr add 24.116.100.91/255.255.255.248 broadcast 24.116.100.95 dev eth1
root at OpenWrt-bios2:~# ip link set up dev eth1
root at OpenWrt-bios2:~# ip route add 0/0 via 24.116.100.89 dev eth1 proto static
root at OpenWrt-bios2:~# ping -c5 24.116.100.89
PING 24.116.100.89 (24.116.100.89): 56 data bytes
64 bytes from 24.116.100.89: seq=0 ttl=64 time=1.160 ms
64 bytes from 24.116.100.89: seq=1 ttl=64 time=1.475 ms
64 bytes from 24.116.100.89: seq=2 ttl=64 time=1.809 ms
64 bytes from 24.116.100.89: seq=3 ttl=64 time=1.610 ms
64 bytes from 24.116.100.89: seq=4 ttl=64 time=0.731 ms

--- 24.116.100.89 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.731/1.357/1.809 ms
root at OpenWrt-bios2:~# 


What am I missing?

Thanks,

-Philip