[SOLVED] Proxmox getting error while installing Open-VZ VM

[pejman_view]

Hello,

I installed proxmox V3.1 , I would create a Open-VZ virtual machine , I got this error after confirming!

Directory /proc/vz not found, assuming non-OpenVZ kernel
Container init failed: Cgroup is not mounted
TASK ERROR: command 'vzctl --skiplock create 112 --ostemplate /var/lib/vz/template/cache/centos-5-standard_5.8-1_i386.tar.gz --private /var/lib/vz/private/112' failed: exit code 5

 

[Ric]

Did you complete the install with "apt-get update" and apt-get dist-upgrade"? My own upgrade to 3.1 went a bit wonky until I remembered to complete those steps. Ric

 

[pejman_view]

Did you complete the install with "apt-get update" and apt-get dist-upgrade"? My own upgrade to 3.1 went a bit wonky until I remembered to complete those steps. Ric

Hi Eric,
thank you for your reply.
I run the command , nothing has changed!

 

[tom]

are you sure you run the right kernel? post the output of:

pveversion -v

 

[Ric]

If you downloaded a bunch of files during the upgrade, including a kernel, then you need to reboot. I'm just trouble shooting with a shotgun here! And, where did you get this VM? If you installed one from Turnkey Linux, then you need to report it on their forum. If you rolled your own, no telling where the error is.

But, with all Turnkey containers, you have to ssh in, then type: vzctl enter XXX (number of container) and type "turnkey-init" to answer all of the setup questions, as root user.

Any particular reason for installing CentOS? Installing Debian would be safer as Proxmox has no clue what RPM means natively, and their library layout is different. You might be better served to install CentOS into a KVM, just so two different OS's aren't beating each other up.

Again, just trouble-shooting with a shotgun. Ric

 

[pejman_view]

If you downloaded a bunch of files during the upgrade, including a kernel, then you need to reboot. I'm just trouble shooting with a shotgun here! And, where did you get this VM? If you installed one from Turnkey Linux, then you need to report it on their forum. If you rolled your own, no telling where the error is.

But, with all Turnkey containers, you have to ssh in, then type: vzctl enter XXX (number of container) and type "turnkey-init" to answer all of the setup questions, as root user.

Any particular reason for installing CentOS? Installing Debian would be safer as Proxmox has no clue what RPM means natively, and their library layout is different. You might be better served to install CentOS into a KVM, just so two different OS's aren't beating each other up.

Again, just trouble-shooting with a shotgun. Ric

There was an option when I bought a dedicated server which what OS you want?! I choosed Proxmox
So it means it's installed by Datacenter.

 

[pejman_view]

are you sure you run the right kernel? post the output of:

pveversion -v

Hello, Tom

This is output
root@us2:~# pveversion -v
proxmox-ve-2.6.32: 3.1-109 (running kernel: 3.2.0-4-amd64)
pve-manager: 3.1-3 (running version: 3.1-3/dc0e9b0e)
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-23-pve: 2.6.32-109
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-1
pve-cluster: 3.0-7
qemu-server: 3.1-1
pve-firmware: 1.0-23
libpve-common-perl: 3.0-6
libpve-access-control: 3.0-6
libpve-storage-perl: 3.0-10
pve-libspice-server1: 0.12.4-1
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.0-2

 

[pejman_view]

Still looking forward to find a solution.

 

[Ric]

...and you picked this VM to install from the pick-list in "storage" provided by the Proxmox HTML front-end? This was a ready-made container provided by Proxmox? Or, did you roll your own? Can you do what you need to do with a Debian based VM, instead?

 

[screenie]

root@us2:~# pveversion -v
proxmox-ve-2.6.32: 3.1-109 (running kernel: 3.2.0-4-amd64)

boot into the correct kernel and it should work;

see the wiki for installation instructions - this is what you missed:
apt-get remove linux-image-amd64 linux-image-3.2.0-4-amd64
update-grub

 

[pejman_view]

boot into the correct kernel and it should work;

see the wiki for installation instructions - this is what you missed:
apt-get remove linux-image-amd64 linux-image-3.2.0-4-amd64
update-grub

thanks your guideline so helpful!

 

[rmoglia]

root@xray:/# pveversion -v
proxmox-ve-2.6.32: 3.3-139 (running kernel: 3.10.0-5-pve)
pve-manager: 3.3-5 (running version: 3.3-5/bfebec03)
pve-kernel-2.6.32-32-pve: 2.6.32-136
pve-kernel-3.10.0-5-pve: 3.10.0-19
pve-kernel-2.6.32-34-pve: 2.6.32-139
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-1
pve-cluster: 3.0-15
qemu-server: 3.3-3
pve-firmware: 1.1-3
libpve-common-perl: 3.0-19
libpve-access-control: 3.0-15
libpve-storage-perl: 3.0-25
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.1-10
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1

Not working.

 

[rmoglia]

proxmox-ve-2.6.32: 3.3-139 (running kernel: 2.6.32-34-pve)
pve-manager: 3.3-5 (running version: 3.3-5/bfebec03)
pve-kernel-2.6.32-32-pve: 2.6.32-136
pve-kernel-3.10.0-5-pve: 3.10.0-19
pve-kernel-2.6.32-34-pve: 2.6.32-139
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-1
pve-cluster: 3.0-15
qemu-server: 3.3-3
pve-firmware: 1.1-3
libpve-common-perl: 3.0-19
libpve-access-control: 3.0-15
libpve-storage-perl: 3.0-25
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.1-10
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1

Works

 

[dietmar]

OpenVZ does not work with 3.10.0 kernel. You need kernel 2.6.32 for OpenVZ.