IPv6 Issues - 3.10.0-1160.80.1.vz7.191.4

3.10.0-1160.80.1.vz7.191.4 (this does NOT happen with 3.10.0-1160.53.1.vz7.185.3)

Initially, when installing and settings things up, IPv6 on all VMs works fine.

I've noticed that after a while, IPv6 connectivity sort of just "dies" (on EVERY VPS)... and the only "fix" I've found is to run `service network restart` on the host node.

Again, there was no issue with the previous stable kernel (185.3), it only impacts 191.4

The host node however, is unaffected by this issue:

===========
[root@saxophone ~]# ping6 google.com
PING google.com(lax17s50-in-x0e.1e100.net (2607:f8b0:4007:815::200e)) 56 data bytes
64 bytes from lax17s50-in-x0e.1e100.net (2607:f8b0:4007:815::200e): icmp_seq=1 ttl=114 time=9.26 ms
64 bytes from lax17s50-in-x0e.1e100.net (2607:f8b0:4007:815::200e): icmp_seq=2 ttl=114 time=9.65 ms
64 bytes from lax17s50-in-x0e.1e100.net (2607:f8b0:4007:815::200e): icmp_seq=3 ttl=114 time=9.47 ms
64 bytes from lax17s50-in-x0e.1e100.net (2607:f8b0:4007:815::200e): icmp_seq=4 ttl=114 time=9.49 ms
^C
--- google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 9.264/9.471/9.652/0.137 ms
[root@saxophone ~]#
===========

Here is what happens within a VPS:

===========
[root@test ~]# ping6 google.com
PING google.com(ams17s10-in-x0e.1e100.net (2a00:1450:400e:801::200e)) 56 data bytes
^C
--- google.com ping statistics ---
83 packets transmitted, 0 received, 100% packet loss, time 82000ms

[root@test ~]#
===========