- 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.