03-29-2019, 05:43 AM
OpenVZ is easy to spot in most cases:
- venet0 network adapters in "ifconfig" or "ip a" output
- 2.6.32 kernel on no matter which OS (i.e. uname -a)
- simfs or ploop filesystem on "df -h" output
- lack of most system processes in ps and htop output (since almost all system and kernel processes are ran by the host and simply shared with to the VMs)
There is probably more to it.
- venet0 network adapters in "ifconfig" or "ip a" output
- 2.6.32 kernel on no matter which OS (i.e. uname -a)
- simfs or ploop filesystem on "df -h" output
- lack of most system processes in ps and htop output (since almost all system and kernel processes are ran by the host and simply shared with to the VMs)
There is probably more to it.
![[Image: zHHqO5Q.png]](https://i.imgur.com/zHHqO5Q.png)