CentOS 7 в XEN VM: чудеса в работе сетевых интерфейсов, да и только. Что это может быть?

# ifconfig eth0
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.3.32  netmask 255.255.255.0  broadcast 192.168.3.255
        ether 00:16:3e:13:4d:d6  txqueuelen 1000  (Ethernet)
        RX packets 3423  bytes 257941 (251.8 KiB)
        RX errors 0  dropped 1018  overruns 0  frame 0
        TX packets 572  bytes 204463 (199.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

# ifconfig eth2
eth2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.4.32  netmask 255.255.255.0  broadcast 192.168.4.255
        ether 00:16:3e:52:e8:00  txqueuelen 1000  (Ethernet)
        RX packets 764  bytes 75664 (73.8 KiB)
        RX errors 0  dropped 554  overruns 0  frame 0
        TX packets 15  bytes 2205 (2.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         192.168.3.1      0.0.0.0         UG    0      0        0 eth0
default         192.168.4.1      0.0.0.0         UG    100    0        0 eth2
192.168.3.0      0.0.0.0         255.255.255.0   U     0      0        0 eth0
192.168.4.0      0.0.0.0         255.255.255.0   U     0      0        0 eth2
link-local      0.0.0.0         255.255.0.0     U     1002   0        0 eth0
link-local      0.0.0.0         255.255.0.0     U     1003   0        0 eth1
link-local      0.0.0.0         255.255.0.0     U     1004   0        0 eth2
192.168.2.0     0.0.0.0         255.255.255.0   U     0      0        0 eth1

# iptables -L -v
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination


# nmtui
NetworkManager не работает.

# sestatus
SELinux status:                 disabled

# ping -I eth0 192.168.3.1
PING 192.168.3.1 (192.168.3.1) from 192.168.3.32 eth0: 56(84) bytes of data.
64 bytes from 192.168.3.1: icmp_seq=1 ttl=255 time=1.29 ms
64 bytes from 192.168.3.1: icmp_seq=2 ttl=255 time=1.93 ms
64 bytes from 192.168.3.1: icmp_seq=3 ttl=255 time=2.17 ms

# ping -I eth0 192.168.1.65
PING 192.168.1.65 (192.168.1.65) from 192.168.3.32 eth0: 56(84) bytes of data.
64 bytes from 192.168.1.65: icmp_seq=1 ttl=63 time=0.267 ms
64 bytes from 192.168.1.65: icmp_seq=2 ttl=63 time=0.269 ms
64 bytes from 192.168.1.65: icmp_seq=3 ttl=63 time=0.260 ms
64 bytes from 192.168.1.65: icmp_seq=4 ttl=63 time=0.264 ms

# ping -I eth2 192.168.4.1
PING 192.168.4.1 (192.168.4.1) from 192.168.4.32 eth2: 56(84) bytes of data.
64 bytes from 192.168.4.1: icmp_seq=1 ttl=255 time=3.50 ms
64 bytes from 192.168.4.1: icmp_seq=2 ttl=255 time=1.35 ms
64 bytes from 192.168.4.1: icmp_seq=3 ttl=255 time=2.71 ms
64 bytes from 192.168.4.1: icmp_seq=4 ttl=255 time=0.936 ms

#tcpdump -qn -i eth2 host 192.168.1.65
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth2, link-type EN10MB (Ethernet), capture size 65535 bytes
15:27:12.952547 IP 192.168.4.32 > 192.168.1.65: ICMP echo request, id 5086, seq 1, length 64
15:27:12.952829 IP 192.168.1.65 > 192.168.4.32: ICMP echo reply, id 5086, seq 1, length 64
15:27:13.952357 IP 192.168.4.32 > 192.168.1.65: ICMP echo request, id 5086, seq 2, length 64
15:27:13.952698 IP 192.168.1.65 > 192.168.4.32: ICMP echo reply, id 5086, seq 2, length 64
15:27:14.952361 IP 192.168.4.32 > 192.168.1.65: ICMP echo request, id 5086, seq 3, length 64
15:27:14.952766 IP 192.168.1.65 > 192.168.4.32: ICMP echo reply, id 5086, seq 3, length 64
15:27:15.952365 IP 192.168.4.32 > 192.168.1.65: ICMP echo request, id 5086, seq 4, length 64
15:27:15.952766 IP 192.168.1.65 > 192.168.4.32: ICMP echo reply, id 5086, seq 4, length 64

# ping -I eth2 192.168.1.65
PING 192.168.1.65 (192.168.1.65) from 192.168.4.32 eth2: 56(84) bytes of data.
--- 192.168.1.65 ping statistics ---
6 packets transmitted, 0 received, 100% packet loss, time 4999ms