Running kernel is not OpenVZ kernel. here is some info from the server [root@localhost grub]# service vz start Running kernel is not OpenVZ kernel. [FAILED] [root@localhost grub]# stat /dev/vzctl stat: cannot stat `/dev/vzctl': No such file or directory [root@localhost grub]# uname -a
Kernel Count; 2.6.32-431.el6.x86_64: 9037: 2.6.32-042stab113.11: 6549: 2.6.32-042stab127.2: 5851: 2.6.32-042stab112.15: 5467: 2.6.32-042stab092.3: 4794: 2.6.32-573 As OpenVZ employs a single kernel model, it is as scalable as the 2.6 Linux kernel; that is, it supports many CPUs and many gigabytes of RAM. A single container can scale up to the whole physical box, i.e. use all the CPUs and all the RAM. Indeed, some people are using OpenVZ with a single Virtual Environment. After you've built and installed the kernel (steps not covered in this article), update the boot loader and reboot to see if the kernel boots correctly. Host environment. To maintain your virtual servers you need the sys-cluster/vzctl package which contains all necessary programs and many useful features: OpenVZ is free open source software, available under GNU GPL. OpenVZ is the basis of Virtuozzo , a virtualization solution offered by Virtuozzo company. Virtuozzo is optimized for hosters and offers hypervisor (VMs in addition to containers), distributed cloud storage , dedicated support, management tools, and easy installation.
Kernel Count; 2.6.32-431.el6.x86_64: 9037: 2.6.32-042stab113.11: 6549: 2.6.32-042stab127.2: 5851: 2.6.32-042stab112.15: 5467: 2.6.32-042stab092.3: 4794: 2.6.32-573
The OpenVZ software for Linux kernel 2.6.20 includes improvements in the following areas: Support for read-only bind mounts, which allows a read-only view into a read-write file system. This
Installing linux kernel from repository, grub, updating grub (this is widely spread advice I googled out) and rebooting machine has little effect. Grub finds one system image, the freshly installed one, /boot gets populated, but system still runs kernel mentioned above.
ms/af_key: do not use GFP_KERNEL in atomic contexts pfkey_broadcast() might be called from non process contexts, we can not use GFP_KERNEL in these cases [1]. This patch partially reverts commit ba51b6be38c1 ("net: Fix RCU splat in af_key"), only keeping the GFP_ATOMIC forcing under rcu_read_lock() section.