We've upgraded a few machines to a 4.18.3 kernel and we're running into
weird IPv6 neighbor discovery issues. Basically, the machines stop
responding to inbound IPv6 neighbor solicitation requests, which very
quickly breaks all IPv6 connectivity.
It seems like the routing table gets
1/19/2018 3:28 PM, Brian Rak wrote:
We've been running into a fairly persistent issue where virtio_net
adapters will suddenly stop sending packets when running under KVM.
This has persisted through several qemu versions, and a large number
of guest kernel upgrades.
What we end up seeing is
We've been running into a fairly persistent issue where virtio_net
adapters will suddenly stop sending packets when running under KVM.
This has persisted through several qemu versions, and a large number of
guest kernel upgrades.
What we end up seeing is the guest continuing to receive
(Existing email got kinda messy, starting over again):
So, I'm having an issue with the kernel where if I add a bunch of
routes, I see some of them go "missing". They don't show up in the 'ip
-4 route' list, but they do show up if I do 'ip -4 route get X'.
I managed to come up with a simple
have added a test that will force us to use child index 0 if
the key we are looking for is less than the key of the current tnode.
Fixes: 8be33e955cb9 ("fib_trie: Fib walk rcu should take a tnode and key instead of
a trie and a leaf")
Reported-by: Brian Rak <b...@gameservers.co
On 10/26/2015 11:28 AM, Alexander Duyck wrote:
On 10/24/2015 06:32 AM, Brian Rak wrote:
On 10/23/2015 6:32 PM, Alexander Duyck wrote:
On 10/23/2015 02:34 PM, Brian Rak wrote:
I've got a weird situation here. I have a route that the kernel knows
about, but won't display via the general
On 10/23/2015 6:32 PM, Alexander Duyck wrote:
On 10/23/2015 02:34 PM, Brian Rak wrote:
I've got a weird situation here. I have a route that the kernel knows
about, but won't display via the general RTM_GETROUTE call, but will
display if I query for that particular route:
# ip -4 route show
I've got a weird situation here. I have a route that the kernel knows
about, but won't display via the general RTM_GETROUTE call, but will
display if I query for that particular route:
# ip -4 route show | grep 108.61.171.x
# ip route get 108.61.171.x
108.61.171.x dev MYIF
cache
# cat
We've been encountering an issue in the virtio-net driver that cause it
to become unresponsive after a period of high load. This issue goes
away if we disable TSO on the interface.
Once this issue has been triggered, the interface can still receive
traffic, but will not transmit anything.
