| OpenVZ 7 Containers suddenly missing venet0 [message #53279] |
Tue, 15 May 2018 11:03  |
wsap
Messages: 62
Registered: March 2018
Location: Halifax, NS
|
Member |
|
|
Hey there,
- Upon reboot of a container yesterday, it suddenly no longer had a venet0 adapter and (of course) all networking failed to function. We migrated it to another node and all then worked.
- We created a brand new container on another node and it encountered the exact same problem: no venet0
- Rebooting these containers does not result in anything different
- vzlist shows the IP associated.
- /var/log/vzctl.log shows a successful container start
- Comparing the ve.conf between the ones without the venet0 adapter and the ones that are currently running successfully shows no differences other than the usual things like IP address and hostname.
Does anyone have any suggestions as to where to look to solve this?
Thanks so much in advance for your ideas.
|
|
|
|
| Re: OpenVZ 7 Containers suddenly missing venet0 [message #53282 is a reply to message #53279] |
Tue, 15 May 2018 13:19  |
wsap
Messages: 62
Registered: March 2018
Location: Halifax, NS
|
Member |
|
|
I asked Virtuozzo support to see if they've encountered this before. They provided this bug report, which suggests either:
1. Manually patching the kernel, upgrade, and reboot, or
2. Downgrading the iproute package on the container
Since the kernel with the patch included has yet to be released, we downgraded iproute on the container and upon downgrading the iproute package, networking was fixed.
I really wish KernelCare would add support for Virtuozzo 7 OR the Virtuozzo team would supply dedicated ReadyKernel licenses without requiring a full Virtuozzo node license.
[Updated on: Tue, 05 June 2018 02:01] Report message to a moderator |
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
