[Users] VM's not getting networking info on vz7 node
Mark Johanson
mjohanson at a2hosting.com
Thu Oct 5 21:48:15 MSK 2017
Hello,
I was wondering if someone might have some suggestions on a issue I am having with OpenVZ7. VM's based on (Debian, Slack, Gentoo, Ubuntu) all build fine from our production templates, but do not recieve any networking inside the vm. Our production Centos/Fedora templates build fine and get internal networking that is correct. Production environment is not vz7 but centos6 based.
The node networking looks like:
#ifconfig
br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether de:3d:9c:b7:e9:58 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 15 bytes 2970 (2.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet xxx.xxx.xxx.xxx netmask 255.255.255.0 broadcast xxx.xxx.xxx.255
ether 0c:c4:7a:42:4d:b2 txqueuelen 1000 (Ethernet)
RX packets 7106651 bytes 3866501198 (3.6 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3590592 bytes 4012280255 (3.7 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xdf720000-df73ffff
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
loop txqueuelen 1 (Local Loopback)
RX packets 5826 bytes 314380 (307.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 5826 bytes 314380 (307.0 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
venet0: flags=211<UP,BROADCAST,POINTOPOINT,RUNNING,NOARP> mtu 1500
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 0 (UNSPEC)
RX packets 383582 bytes 21059148 (20.0 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 552381 bytes 2625019111 (2.4 GiB)
TX errors 0 dropped 112 overruns 0 carrier 0 collisions 0
virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 10.37.130.2 netmask 255.255.255.0 broadcast 10.37.130.255
ether 52:54:00:84:0f:86 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8 bytes 936 (936.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
#arp -n
Address HWtype HWaddress Flags Mask Iface
xxx.xxx.xxx.xxx ether 00:17:df:06:9f:00 C eno1
xxx.xxx.xxx.xxx * <from_interface> MP virbr0
xxx.xxx.xxx.xxx * <from_interface> MP eno1
xxx.xxx.xxx.xxx * <from_interface> MP virbr0
xxx.xxx.xxx.xxx * <from_interface> MP eno1
xxx.xxx.xxx.xxx * <from_interface> MP virbr0
xxx.xxx.xxx.xxx * <from_interface> MP eno1
xxx.xxx.xxx.xxx * <from_interface> MP virbr0
xxx.xxx.xxx.xxx * <from_interface> MP eno1
xxx.xxx.xxx.xxx * <from_interface> MP virbr0
xxx.xxx.xxx.xxx * <from_interface> MP eno1
xxx.xxx.xxx.xxx * <from_interface> MP virbr0
xxx.xxx.xxx.xxx * <from_interface> MP eno1
xxx.xxx.xxx.xxx * <from_interface> MP virbr0
xxx.xxx.xxx.xxx * <from_interface> MP eno1
xxx.xxx.xxx.xxx * <from_interface> MP virbr0
xxx.xxx.xxx.xxx * <from_interface> MP eno1
#route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 xxx.xxx.xxx.xxx 0.0.0.0 UG 0 0 0 eno1
10.37.130.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0
xxx.xxx.xxx.0 0.0.0.0 255.255.255.0 U 0 0 0 eno1
xxx.xxx.xxx.xxx 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
xxx.xxx.xxx.xxx 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
xxx.xxx.xxx.xxx 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
xxx.xxx.xxx.xxx 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
xxx.xxx.xxx.xxx 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
xxx.xxx.xxx.xxx 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
xxx.xxx.xxx.xxx 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
xxx.xxx.xxx.xxx 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0 eno1
The non-working VM's (Debian 8 in this example) have networking that looks like:
root at server:/# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:127.0.0.2 P-t-P:127.0.0.2 Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:232 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:232 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:18701 (18.2 KiB) TX bytes:0 (0.0 B)
venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:WRONG-IP P-t-P:WRONG-IP Bcast:WRONG-IP Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
root at server:/# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 venet0
Working vm networking (Fedora 26 in this example) looks like:
CT-238 /# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: venet0: <BROADCAST,POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default
link/void
inet 127.0.0.1/32 scope host venet0
valid_lft forever preferred_lft forever
inet xxx.xxx.xxx.xxx/32 brd xxx.xxx.xxx.xxx scope global venet0:0
valid_lft forever preferred_lft forever
CT-238 /# arp -n
CT-238 /# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 venet0
169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0 venet0
More information about the Users
mailing list