New vzctl

Bestbeast

Well-Known Member
Jul 29, 2016
163
5
58
30
Hello,

Any idea on how can I update vzctl and use it with proxmox? I could update it following openvz instructions, but I am having problems when creating a container:

vztmpl-dl ERROR: template /var/lib/vz/template/cache/centos-5-standard_5.8-1_i386.tar.gz not found!
Cached OS template /vz/template/cache//var/lib/vz/template/cache/centos-5-standard_5.8-1_i386.tar.gz.tar[.gz|.bz2|.xz] not found
Creation of container private area failed
TASK ERROR: command 'vzctl --skiplock create 101 --ostemplate /var/lib/vz/template/cache/centos-5-standard_5.8-1_i386.tar.gz --private /var/lib/vz/private/101' failed: exit code 91

Any idea,
Thanks
 
Hello,

I finded out that what is failing is proxmox vzctl creation command, can anyone please tell me how to edit this command:
vzctl create 104 --ostemplate centos-5-standard_5.8-1_i386.tar.gz
runned by proxmox to this one:
vzctl create 104 --ostemplate centos-5-standard_5.8-1_i386
 
you cannot just "update" vzctl, you have to use the version provided by Proxmox VE.
 
you cannot just "update" vzctl, you have to use the version provided by Proxmox VE.
I do not want to use the version provided by proxmox because openvz is not updated, that is why I am updating its components, manually, and know I want to update the commands that proxmox send to vzctl
 
The question is, what you do expect posting in this forum - Proxmox VE 3.x is EOL already.

As you do something which is not supported or tested, no one here can assist.

The current version is 4.3, so you should plan the move as soon as possible.
 
The question is, what you do expect posting in this forum - Proxmox VE 3.x is EOL already.

As you do something which is not supported or tested, no one here can assist.

The current version is 4.3, so you should plan the move as soon as possible.
You are from proxmox staff member and you do not know in which part of proxmox code are the commands that execute the creation of a container? no matter if it is 4.3 or 3.x.
Also new proxmox uses lxc which has very serious bugs and it is not good for production that is why I am not going to move at the moment
 
In that case you are on your own.
Yes I am seing it... Good decision to say: Lets update proxmox to lxc which is now buggy instead of continuing updating openvz which is fine.

Thanks proxmox team, continue like that...
 
Yes I am seing it... Good decision to say: Lets update proxmox to lxc which is now buggy instead of continuing updating openvz which is fine.

Thanks proxmox team, continue like that...

You can of course stay with OpenVZ, but Proxmox VE moved to LXC for many good reasons.

If you see a bug in LXC, please report them and it will be addressed.
 
You can of course stay with OpenVZ, but Proxmox VE moved to LXC for many good reasons.

If you see a bug in LXC, please report them and it will be addressed.
Problems with lxc have already been told to you since you upgraded like the cpu limiting problems, or i/o and iops limiting that is already in openvz, and there are still there with no solution
 
Problems with lxc have already been told to you since you upgraded like the cpu limiting problems, or i/o and iops limiting that is already in openvz, and there are still there with no solution

Please post the link to the bugzilla bug reports, otherwise its hard to follow. For example, LXC CPU limiting is already implemented.
 
Please post the link to the bugzilla bug reports, otherwise its hard to follow. For example, LXC CPU limiting is already implemented.
And the i/o disk, iops and bandwidth limit? I think those this are primary for production if not anyone can affect the whole system
 
And the i/o disk, iops and bandwidth limit? I think those this are primary for production if not anyone can affect the whole system

Just to note, all this is available for qemu. But again, if you find a bug or miss a feature for LXC, please file a request on https://bugzilla.proxmox.com
 
Yes that is why I am asking when this primary functions will be implemented in containers, cause openvz almost have then all

OpenVZ missed a lot of very basic features, so please stop thinking that OpenVZ was perfect. Just think of the very limited storage support (only ext3/4, not perfect NFS). But we going off topic here.
 
OpenVZ missed a lot of very basic features, so please stop thinking that OpenVZ was perfect. Just think of the very limited storage support (only ext3/4, not perfect NFS). But we going off topic here.
You can run a company perfectly only with ext3/4 that no one can affect others with that. On the other hand not limiting i/o, iops or bandwidth can be very dangerous for production...
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!