The LXC images failed to start under linux-image-4.2.0-28-generic, with a kernel oops.
I also tried, in Xenial, linux-image-4.4.0-2-generic and that failed.
Setting /proc/sys/net/ipv4/xfrm4_gc_thresh to 5 causes the failure almost immediately.
I would like to confirm my procedure however. I've been changing /proc/sys/net/ipv4/xfrm4_gc_thresh inside the containers, not the host. Is this correct?
I'm still able to duplicate this bug using:
linux-image- 3.13.0- 78-generic (from trusty-backports) 3.19.0- 50-generic (from linux-image- generic- lts-vivid)
linux-image-
The LXC images failed to start under linux-image- 4.2.0-28- generic, with a kernel oops.
I also tried, in Xenial, linux-image- 4.4.0-2- generic and that failed.
Setting /proc/sys/ net/ipv4/ xfrm4_gc_ thresh to 5 causes the failure almost immediately.
I would like to confirm my procedure however. I've been changing /proc/sys/ net/ipv4/ xfrm4_gc_ thresh inside the containers, not the host. Is this correct?