User:Grin/Debian

From Proxmox VE
Jump to navigation Jump to search

Short Debian installation:

  • install etch as you please, but keep in mind that the root path of the private machines (/var/lib/vz/private/) should use ext3 (or ext2 if you're retro) filesystem as quota and other interesting features won't work on real filesystems like xfs. (this is a limitation of OpenVZ, not proxmox.)
  • install openvz kernel ( linux-image-openvz-686 ) if you want, it'll save you some errors when installing openvz kernel dependent packages. alternatively you can do dpkg -a --configure later.
  • use the apt repository deb http://download.proxmox.com/debian etch pve
  • install packages: proxmox-ve, libhtml-embperl-perl, apache2-mpm-prefork (with their dependencies, I suggest to use aptitude and a repo like file:/cdrom/proxmox/ from the CD image)
    • embperl will be fscked if you do not use prefork apache:
[Tue Dec 09 11:52:05 2008] [error] [6987]ERR:  24:  Error in Perl code: \t(in cleanup) Can't call method "app" on an undefined value at /usr/lib/perl5/Embperl/Util.pm line 107.
[Tue Dec 09 11:52:05 2008] [error] [6987]ERR:  24:  Error in Perl code: \t(in cleanup) Can't call method "component" on an undefined value at /var/www/pve/base.epl line 109.
[Tue Dec 09 11:52:05 2008] [error] [6987]ERR:  24:  Error in Perl code: \t(in cleanup) Can't call method "component" on an undefined value at /var/www/pve/base.epl line 103.
[Tue Dec 09 11:52:05 2008] [error] [6987]ERR:  24:  Error in Perl code: \t(in cleanup) Illegal declaration of subroutine Embperl::__1::_ep_sub_ at /var/www/pve/base.epl line 101.
  • keep -pve kernel if you do not need some advanced kernel features, or use an OpenVZ/Debian one if you do (like software RAID)
  • reboot with your newly installed system, and follow the installation instructions.

Cluster

If you need clustering do not forget to set your static address in /etc/interfaces, as cluster utilities depend on finding it there.

Miscelleous

  • Proxmox for some weird reason depends on postfix (instead of mail-transport-agent), but I don't see any direct requirement yet. TBD
  • Proxmox suggest ntpd, which is a good idea, but you can survive with chrony just as well.
  • It seems that using bridge interface makes life much easier. Put in /etc/network/interfaces (obviously replacing IP and mask):
auto vmbr0
iface vmbr0 inet static
       address 10.1.1.17
       netmask 255.255.255.0
       gateway 10.1.1.1
       bridge_ports eth0
       bridge_stp off
       bridge_fd 0