Container config file does not exist

[slm17]

dear all. have an issue when creating new CT machine. (it works fine with qemu).

i tried with different templates, but always the same problem.

when creating the task viewer shows (Description: CT 103 - Create):

extracting archive '/vm/templates/template/cache/debian-6.0-standard_6.0-4_amd64.tar.gz'
Total bytes read: 381470720 (364MiB, 88MiB/s)
Container config file does not exist
TASK ERROR: command 'vzctl --skiplock quotainit 103' failed: exit code 14

and the next entry (Description: CT 103 - Start):

Container config file does not exist
TASK ERROR: command 'vzctl start 103' failed: exit code 14

/var/log/vzctl.log says:

...
2011-12-09T09:42:54+0100 vzctl : CT 103 : WARNING: /etc/vz/conf/103.conf not found: No such file or directory
...

so do i have to create the config file in /etc/vz/conf/ manually? i assumed proxmox would to this for me.. or did i miss something?
thanks a lot for any advices..

 

[tom]

make sure you run the latest packages, run 'aptitude update && aptitude full-upgrade', reboot and test again. it the issue is still there, post the output of 'pveversion -v'

 

[slm17]

thanks for answering.
it is an updated install (aptitude update && aptitude full-upgrade does not install new packages).

pveversion -v:

pve-manager: 2.0-14 (pve-manager/2.0/6a150142)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 2.0-54
pve-kernel-2.6.32-6-pve: 2.6.32-54
lvm2: 2.02.86-1pve2
clvm: 2.02.86-1pve2
corosync-pve: 1.4.1-1
openais-pve: 1.1.4-1
libqb: 0.6.0-1
redhat-cluster-pve: 3.1.7-1
pve-cluster: 1.0-12
qemu-server: 2.0-11
pve-firmware: 1.0-13
libpve-common-perl: 1.0-10
libpve-access-control: 1.0-3
libpve-storage-perl: 2.0-9
vncterm: 1.0-2
vzctl: 3.0.29.3-1
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-1
ksm-control-daemon: 1.1-1

 

[slm17]

ah one more thing.. just noticed. when i create a vm through the web interface, the config file actually gets created - but not at the right location. they get stored at: (previous example, vm is id '103', host's name is 'dhananjay')

/etc/pve/nodes/dhananjay/openvz/103.conf

after symlinking this config file i'm able to start the vm:

ln -s /etc/pve/nodes/dhananjay/openvz/103.conf /etc/vz/conf/
vzctl start 103

hm... ??

 

[dietmar]

You run the wrong vzctl package! should be

vzctl: 3.0.29-3pve6

 

[slm17]

ah - thanks a lot! somehow overlooked the pve.

while installing it complained about 'unable to backup existing configuration' so i manually installed (the wrong) vzctl.

mv /etc/vz/conf.org /root/old-vz-conf.org

from http://forum.proxmox.com/threads/7675-unable-to-install-vzctl solved it!

 

[Erdenebileg Bayaraa]

ah - thanks a lot! somehow overlooked the pve.

while installing it complained about 'unable to backup existing configuration' so i manually installed (the wrong) vzctl.

mv /etc/vz/conf.org /root/old-vz-conf.org

from http://forum.proxmox.com/threads/7675-unable-to-install-vzctl solved it!

/etc/pve# qm list
VMID NAME STATUS MEM(MB) BOOTDISK(GB) PID
102 spendcontrol stopped 1024 0.00 0
103 internal-openerp.usi.mn stopped 1024 0.00 0
105 negerp stopped 1024 0.00 0
106 buuz stopped 2024 0.00 0

my servers can't started.
when i start command error message
/etc/pve# qm start 106
storage 'server' does not exists

 

[Erdenebileg Bayaraa]

please help
when i start to server
like that command
qm start 104
error message" storage 'server' does not exists"

pveversion -v
pve-manager: 1.9-26 (pve-manager/1.9/6567)
running kernel: 2.6.32-7-pve
proxmox-ve-2.6.32: 1.9-55+ovzfix-2
pve-kernel-2.6.32-6-pve: 2.6.32-55+ovzfix-1
pve-kernel-2.6.32-7-pve: 2.6.32-55+ovzfix-2
qemu-server: 1.1-32
pve-firmware: 1.0-15
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-3pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-2
ksm-control-daemon: 1.0-6

 

[dietmar]

please help
when i start to server
like that command
qm start 104
error message" storage 'server' does not exists"

First, you are posting in the wrong forum (this forum is for version 2.X and later).

Second, you VM uses a disk on a storage called 'server', but that storage does not longer exists.