New vzctl and dab, updated appliances


Proxmox Staff Member
Staff member
Apr 28, 2005
We just released a new vzctl package, supporting the immediate reboot of a container using vzeventd. (you need a current 2.6.18 or 2.6.32 kernel, 2.6.24 will NOT work).

Additionally, we fixed some issue in dab (supports now dependency based init) and updated a lot of appliances based on latest Debian Squeeze. If you build your own appliances with dab, you should take a look on the example appliances.

Release notes:

- vzctl (3.0.26-1pve3)
  • vzeventd support
  • update to vzctl- release
  • remove stale cron scripts
  • fix /etc/init.d/vzeventd - do not fail on non-openvz kernels
  • change openvz startup priority from 20 to 21
- pve-manager (1.8-17)
  • update appliance infos
  • disable chrooted environment (remove pvebash). That feature is not really used and is considered dangerous.
- dab (1.1-14) - updates for dependency based init
  • include SUITE-updates for squeeze
  • use insserv instead of update-rc.d (for newer versions)
- new and updated OS appliances
  • Debian 6 (i386 and amd64)
  • Ubuntu 10.04 and 11.04 (i386 and amd64)
  • Fedora 14 (i386 and amd64)
  • Centos 4 and 5 (i386 and amd64)
- updated application templates
  • Request Tracker (with RTFM)
  • Joomla
  • SugarCRM
  • Drupal
  • Wordpress
More info:
Best regards,
View attachment
Those who wish to retain chroot capability of /usr/bin/pvebash after upgrading to pve-manager v1.8.17 can do the following:

In case the file /usr/bin/pvebash is missing, it can be created with the following contents:

export PS1="VM$1 $2:\\w\\\$ ";
umask 022

exec /usr/sbin/chroot /var/lib/vz/$2/$1 /bin/bash --norc
exec /usr/sbin/chroot /var/lib/vz/$2/$1 /bin/sh --norc
Line 1102 in s/usr/share/perl5/PVE/
[FONT=Courier New][SIZE=2][COLOR=#0000ff]     $vzcmd = [  '/usr/sbin/vzctl', 'enter', $veid ];
should be replaced with
[FONT=Courier New][SIZE=2][COLOR=#0000ff]     if ($status eq  'running') {
  $vzcmd = [ '/usr/sbin/vzctl', 'enter', $veid ];
     }  elsif ($status eq 'mounted') {
  $vzcmd = [ "/usr/bin/pvebash", $veid,  'root'];
     } else {
  $vzcmd = [ "/usr/bin/pvebash", $veid,  'private'];
This is a nice feature and in my opinion not a security risk - if anyone has control of the Proxmox Host they can pretty much do as they will with the OpenVZ containers anyway.

This command has not been very well publicised and it can be used to chroot into a stopped or mounted container with:
/usr/bin/pvebash #VEID private
/usr/bin/pvebash #VEID root

No rc startup scripts will be run in these cases.
Last edited:
A new article in the Wiki shows off the working method for post OpenVZ VM creation script execution for first boot. insserv is the preferred method now although the file-rc method works as well rather than the old broken copying of files into the rc*.d folders method that Lenny containers revelled in earlier. This is especially applicable for Squeeze based containers.


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 your own in 60 seconds.

Buy now!