PDA

View Full Version : Proxmox VE 2.0 rc1 released!



martin
02-16-2012, 05:16 PM
Hi all!

We just uploaded the first release candidate of Proxmox VE 2.0 (new ISO and also updated the repository). Just run "aptitude update && aptitude full-upgrade" to update from a previous beta, same as always.

This version can be upgraded to upcoming 2.0 releases including the stable release without problems. Its also the first 2.0 release which is based on a stable Kernel.

(Upgrading from 1.9 to 2.0 is not yet supported but will be possible via upgrade script.)

A big Thank-you to our active community for all feedback, testing, bug reporting and patch submissions.

New Features

- Role based user- and permission management for all objects (VM´s, storages, nodes, etc.)
- Support for multiple authentication sources

Microsoft Active Directory
LDAP
Linux PAM
Proxmox VE internal authentication
- New Kernel, based on vzkernel-2.6.32-042stab049.6.src.rpm
- vzdump uses now LZO compression by default (faster)
- Countless bug fixes

Overview
http://pve.proxmox.com/wiki/Roadmap#Roadmap_for_2.x

Documentation (work in progress)
http://pve.proxmox.com/wiki/Category:Proxmox_VE_2.0

Video Tutorials
http://www.youtube.com/proxmoxve

Get involved (incl. links to the public git repository and bugzilla bugtracker):
http://www.proxmox.com/products/proxmox-ve/get-involved

Proxmox VE 2.0 beta/rc forum
http://forum.proxmox.com (http://forum.proxmox.com/)

Download
http://www.proxmox.com/downloads/pro.../17-iso-images (http://www.proxmox.com/downloads/proxmox-ve/17-iso-images)

Happy testing, waiting for feedback!
__________________
Best regards,

Martin Maurer
Proxmox VE project leader

ksosez
02-16-2012, 09:09 PM
Still doesnt work for USB key booting:

Ran dd if=promox-ve_2.0-8d4f53a0-20.iso of=/dev/sdb bs=1M

Doesnt recognize it as a bootable drive

fake
02-16-2012, 09:23 PM
is there any SPICE on that dish yet? ;-)

tom
02-16-2012, 09:39 PM
Still doesnt work for USB key booting:

Ran dd if=promox-ve_2.0-8d4f53a0-20.iso of=/dev/sdb bs=1M

Doesnt recognize it as a bootable drive

USB booting works since a long time, I personally installed more than 100 server´s form my USB key ...
I am using the Suse Studio ImageWriter, not dd, see wiki (http://pve.proxmox.com/wiki/Install_from_USB_Stick).

tom
02-16-2012, 09:42 PM
not yet, but I would really like to see a worry free spice, especially on the client side.

ksosez
02-16-2012, 09:49 PM
USB booting works since a long time, I personally installed more than 100 server´s form my USB key ...
I am using the Suse Studio ImageWriter, not dd, see wiki (http://pve.proxmox.com/wiki/Install_from_USB_Stick).

Then you really should remove the dd info since its not working.

tom
02-16-2012, 09:56 PM
Then you really should remove the dd info since its not working.

Just did it with dd using the latest ISO, just to make sure. works here as expected. check your USB media and boot bios settings.

ksosez
02-16-2012, 11:02 PM
Just did it with dd using the latest ISO, just to make sure. works here as expected. check your USB media and boot bios settings.


Not sure what to tell you. Tried it with the Suse Image Writer on Windows same problem. Its a Dell Poweredge 1950. Using unbootin I can boot anything else off the usb stick.

bd5hty
02-17-2012, 06:14 AM
cool

blackfox
02-17-2012, 11:12 AM
Update problem vzctl


root@Proxmox-VE ~ # aptitude full-upgrade
The following packages will be upgraded:
vzctl
1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/241 kB of archives. After unpacking 20.5 kB will be used.
Do you want to continue? [Y/n/?] y
(Reading database ... 112049 files and directories currently installed.)
Preparing to replace vzctl 3.0.29-3pve8 (using .../vzctl_3.0.30-2pve1_amd64.deb) ...
unable to backup existing configuration
dpkg: error processing /var/cache/apt/archives/vzctl_3.0.30-2pve1_amd64.deb (--unpack):
subprocess new pre-installation script returned error exit status 1
configured to not write apport reports
Errors were encountered while processing:
/var/cache/apt/archives/vzctl_3.0.30-2pve1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:


root@Proxmox-VE ~ # pveversion -v
pve-manager: 2.0-28 (pve-manager/2.0/30bb4d33)
running kernel: 2.6.32-7-pve
proxmox-ve-2.6.32: 2.0-60
pve-kernel-2.6.32-6-pve: 2.6.32-55
pve-kernel-2.6.32-7-pve: 2.6.32-60
lvm2: 2.02.88-2pve1
clvm: 2.02.88-2pve1
corosync-pve: 1.4.1-1
openais-pve: 1.1.4-1
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-1
pve-cluster: 1.0-22
qemu-server: 2.0-17
pve-firmware: 1.0-15
libpve-common-perl: 1.0-14
libpve-access-control: 1.0-11
libpve-storage-perl: 2.0-11
vncterm: 1.0-2
vzctl: 3.0.29-3pve8
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-3
ksm-control-daemon: 1.1-1

dietmar
02-17-2012, 12:23 PM
Update problem vzctl

There seems to be a stale vzctl backup from a previous installation. Please try to remove that with:

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

Then try again.

I assume there are no old containers on that system? If so you can safely remove /root/old-vz-conf.org

svan
02-17-2012, 01:04 PM
hello , what about supporting freeBSD? this current version freebsd is not working on it.

blackfox
02-17-2012, 01:17 PM
Hi Dietmar,

Your suggestion resolved the problem and vzclt updated correctly.

After update I found that /etc/vz/conf.org was recreated with the original date.

Should this be removed again for future updates? because the directory is empty as was the original I removed.

dietmar
02-17-2012, 02:36 PM
Should this be removed again for future updates? because the directory is empty as was the original I removed.

Yes, please remove it.

bread-baker
02-18-2012, 12:30 AM
Thank you for the release!

the vzdump lvm issues I posted are fixed.

Note that the 1-st time a snapshot vzdump is done it may fail due to an old lock.

running the backup again fixes that.

here is the log from mail


7162: Feb 17 15:45:06 INFO: Starting Backup of VM 7162 (openvz)
7162: Feb 17 15:45:06 INFO: CTID 7162 exist mounted running
7162: Feb 17 15:45:06 INFO: status = running
7162: Feb 17 15:45:06 INFO: backup mode: snapshot
7162: Feb 17 15:45:06 INFO: ionice priority: 7
7162: Feb 17 15:45:06 INFO: trying to remove stale snapshot '/dev/pve/vzsnap-fbc240-0'
7162: Feb 17 15:45:06 INFO: umount: /mnt/vzsnap0: not mounted
7162: Feb 17 15:45:06 ERROR: command 'umount /mnt/vzsnap0' failed: exit code 1
7162: Feb 17 15:45:07 INFO: Unable to deactivate open pve-data-real (253:4)
7162: Feb 17 15:45:07 INFO: Failed to resume data.
7162: Feb 17 15:45:07 ERROR: command 'lvremove -f /dev/pve/vzsnap-fbc240-0' failed: exit code 5
7162: Feb 17 15:45:07 INFO: creating lvm snapshot of /dev/mapper/pve-data ('/dev/pve/vzsnap-fbc240-0')
7162: Feb 17 15:45:07 INFO: Logical volume "vzsnap-fbc240-0" already exists in volume group "pve"
7162: Feb 17 15:45:07 ERROR: Backup of VM 7162 failed - command 'lvcreate --size 4000M --snapshot --name vzsnap-fbc240-0 /dev/pve/data' failed: exit code 5


then


7162: Feb 17 17:00:07 INFO: Starting Backup of VM 7162 (openvz)
7162: Feb 17 17:00:07 INFO: CTID 7162 exist mounted running
7162: Feb 17 17:00:07 INFO: status = running
7162: Feb 17 17:00:07 INFO: backup mode: snapshot
7162: Feb 17 17:00:07 INFO: ionice priority: 7
7162: Feb 17 17:00:07 INFO: creating lvm snapshot of /dev/mapper/pve-data ('/dev/pve/vzsnap-fbc240-0')
7162: Feb 17 17:00:11 INFO: Logical volume "vzsnap-fbc240-0" created
7162: Feb 17 17:00:11 INFO: creating archive '/data/pve-storage//dump/vzdump-openvz-7162-2012_02_17-17_00_07.tar.lzo'
7162: Feb 17 17:01:15 INFO: Total bytes written: 534353920 (510MiB, 13MiB/s)
7162: Feb 17 17:01:15 INFO: archive file size: 274MB
7162: Feb 17 17:01:16 INFO: delete old backup '/data/pve-storage//dump/vzdump-openvz-7162-2012_02_17-14_13_00.tar.lzo'
7162: Feb 17 17:01:18 INFO: Finished Backup of VM 7162 (00:01:11)


that was done on a system which would freeze every time a snapshot backup was done.

note in the pve log this was included , but I did not see in the email:


INFO: Starting Backup of VM 7162 (openvz)
INFO: CTID 7162 exist mounted running
INFO: status = running

** Note:
WARNING: UNLOCKED /var/lib/vz/lock/103.lck (stale lock by PID 10705)



INFO: backup mode: snapshot
INFO: ionice priority: 7

t.bloo
02-19-2012, 12:26 AM
updated one system, works as expected, thanks

kcalliauw
02-20-2012, 10:04 AM
Hi all,

I currently have a 3-node cluster running on the previous beta release, should this procedure be safe:

1. migrate vm's away from beta node
2. upgrade beta node
3. reboot
4. migrate vm's to rc1 node
5. repeat

I'm hoping to not have to shut down all vm's, since we're talking 60+. So really my question is: are there any know compatibility issues between an rc1 cluster member and a beta cluster member?

Thanks in advance.

Kind regards,
Koen

tom
02-20-2012, 10:53 AM
there are countless fixes and changes between beta3 and rc1 and as a beta is not intended for production use I assume not many have tried this.
so be prepared for issues.

kcalliauw
02-20-2012, 11:04 AM
there are countless fixes and changes between beta3 and rc1 and as a beta is not intended for production use I assume not many have tried this.
so be prepared for issues.

Hey Tom,

Sure, I knew what I was getting into when getting started with the pre-releases.
In any case, I'll try it out in a somewhat more contained environment during the coming days and report back on issues (if any) I ran into.

Cheers,
K!

Faye
02-20-2012, 09:30 PM
Hey Tom,

Sure, I knew what I was getting into when getting started with the pre-releases.
In any case, I'll try it out in a somewhat more contained environment during the coming days and report back on issues (if any) I ran into.

Cheers,
K!

I've just successfully completed this process without apparent issue.

sohaib
02-21-2012, 12:20 AM
Is this RC1 stable enough to be install in LIVE Production server ?

bread-baker
02-21-2012, 12:29 AM
Is this RC1 stable enough to be install in LIVE Production server ?

Please read Tom's post above, as I think that he answered that.

I've used 2.0 testing since it first came out, but not for any production data. We use version 2 for servers which have data we can recover elsewhere like approx, dhcp server, etc. We run weekly pve backups and hourly backups using rsnapshot for things like /etc . So using 2.0 rc1 in production totally depends on how well you know you know your data. After all protection of data is the number one priority .

For our order entry and accounting systems, we'll wait for 2.1 .

chewbaccus
02-21-2012, 04:36 PM
Hi Guys,

today i have tried to install the Proxmox RC1 on Debian Squeeze (http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze)

My Problem begin after the packages unzipping and by the settings of the packages.
Some problems with the dependency !! I have no more idea !!
Have a look on my logs !!



pve-cluster (1.0-22) wird eingerichtet ...
Starting pve cluster filesystem : pve-cluster[main] crit: Unable to get local IP address
(warning).
invoke-rc.d: initscript pve-cluster, action "start" failed.
dpkg: Fehler beim Bearbeiten von pve-cluster (--configure):
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 255 zurück
corosync-pve (1.4.1-1) wird eingerichtet ...
openais-pve (1.1.4-2) wird eingerichtet ...
libxml2-utils (2.7.8.dfsg-2+squeeze2) wird eingerichtet ...
libxslt1.1 (1.1.26-6) wird eingerichtet ...
xsltproc (1.1.26-6) wird eingerichtet ...
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von redhat-cluster-pve:
redhat-cluster-pve hängt ab von pve-cluster; aber:
Paket pve-cluster ist noch nicht konfiguriert.
dpkg: Fehler beim Bearbeiten von redhat-cluster-pve (--configure):
Abhängigkeitsprobleme - verbleibt unkonfiguriert
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von fence-agents-pve:
fence-agents-pve hängt ab von redhat-cluster-pve; aber:
Paket redhat-cluster-pve ist noch nicht konfiguriert.
dpkg: Fehler beim Bearbeiten von fence-agents-pve (--configure):
Abhängigkeitsprobleme - verbleibt unkonfiguriert
ifenslave-2.6 (1.1.0-17) wird eingerichtet ...
update-alternatives: /sbin/ifenslave-2.6 wird verwendet, um /sbin/ifenslave (ifenslave) im Auto-Modus bereitzustellen.
libapreq2 (2.12-2) wird eingerichtet ...
libapache2-mod-apreq2 (2.12-2) wird eingerichtet ...
libdevel-symdump-perl (2.08-3) wird eingerichtet ...
libapache2-mod-perl2 (2.0.4-7) wird eingerichtet ...
Enabling module perl.
Run '/etc/init.d/apache2 restart' to activate new configuration!
libapache2-reload-perl (0.10-2) wird eingerichtet ...
libapache2-request-perl (2.12-2) wird eingerichtet ...
libasound2 (1.0.23-2.1) wird eingerichtet ...
libauthen-pam-perl (0.16-2) wird eingerichtet ...
libcommon-sense-perl (3.3-1) wird eingerichtet ...
libconvert-asn1-perl (0.22-1) wird eingerichtet ...
libcrypt-openssl-bignum-perl (0.04-2) wird eingerichtet ...
libcrypt-openssl-random-perl (0.04-1+b1) wird eingerichtet ...
libcrypt-openssl-rsa-perl (0.25-1+b1) wird eingerichtet ...
libsysfs2 (2.1.0+repack-1) wird eingerichtet ...
tsconf (1.0-7) wird eingerichtet ...
libts-0.0-0 (1.0-7) wird eingerichtet ...
libdirectfb-1.2-9 (1.2.10.0-4) wird eingerichtet ...
libfile-readbackwards-perl (1.04-3) wird eingerichtet ...
libfile-sync-perl (0.09-4+b1) wird eingerichtet ...
libfilesys-df-perl (0.92-3+b1) wird eingerichtet ...
libfont-afm-perl (1.20-1) wird eingerichtet ...
libfont-freetype-perl (0.03-1) wird eingerichtet ...
libglib2.0-data (2.24.2-1) wird eingerichtet ...
libhtml-format-perl (2.04-2) wird eingerichtet ...
libintl-perl (1.20-1) wird eingerichtet ...
libnet-ssleay-perl (1.36-1) wird eingerichtet ...
libio-socket-ssl-perl (1.33-1+squeeze1) wird eingerichtet ...
libjpeg62 (6b1-1) wird eingerichtet ...
libjson-xs-perl (2.290-1) wird eingerichtet ...
liblog-agent-perl (0.307-2) wird eingerichtet ...
liblockfile-simple-perl (0.207-1) wird eingerichtet ...
liblzo2-2 (2.03-2) wird eingerichtet ...
libtimedate-perl (1.2000-1) wird eingerichtet ...
libmailtools-perl (2.06-1) wird eingerichtet ...
libnet-ip-perl (1.25-2) wird eingerichtet ...
libnet-dns-perl (0.66-2) wird eingerichtet ...
libnet-ldap-perl (1:0.4001-2) wird eingerichtet ...
libnet-libidn-perl (0.12.ds-1+b1) wird eingerichtet ...
libterm-readline-gnu-perl (1.20-1) wird eingerichtet ...
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von libpve-access-control:
libpve-access-control hängt ab von pve-cluster; aber:
Paket pve-cluster ist noch nicht konfiguriert.
dpkg: Fehler beim Bearbeiten von libpve-access-control (--configure):
Abhängigkeitsprobleme - verbleibt unkonfiguriert
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von clvm:
clvm hängt ab von redhat-cluster-pve; aber:
Paket redhat-cluster-pve ist noch nicht konfiguriert.
dpkg: Fehler beim Bearbeiten von clvm (--configure):
Abhängigkeitsprobleme - verbleibt unkonfiguriert
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von libpve-storage-perl:
libpve-storage-perl hängt ab von clvm; aber:
Paket clvm ist noch nicht konfiguriert.
dpkg: Fehler beim Bearbeiten von libpve-storage-perl (--configure):
Abhängigkeitsprobleme - verbleibt unkonfiguriert
libx86-1 (1.1+ds1-6) wird eingerichtet ...
libsvga1 (1:1.4.3-29) wird eingerichtet ...
libsdl1.2debian-alsa (1.2.14-6.1) wird eingerichtet ...
libsdl1.2debian (1.2.14-6.1) wird eingerichtet ...
libvncserver0 (0.9.7-2+b1) wird eingerichtet ...
libxfont1 (1:1.4.1-3) wird eingerichtet ...
lzop (1.02~rc1-2) wird eingerichtet ...
perl-suid (5.10.1-17squeeze3) wird eingerichtet ...
vncterm (1.0-2) wird eingerichtet ...
libaio1 (0.3.107-7) wird eingerichtet ...
pve-qemu-kvm (1.0-3) wird eingerichtet ...
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von qemu-server:
qemu-server hängt ab von libpve-storage-perl; aber:
Paket libpve-storage-perl ist noch nicht konfiguriert.
qemu-server hängt ab von pve-cluster; aber:
Paket pve-cluster ist noch nicht konfiguriert.
qemu-server hängt ab von redhat-cluster-pve; aber:
Paket redhat-cluster-pve ist noch nicht konfiguriert.
dpkg: Fehler beim Bearbeiten von qemu-server (--configure):
Abhängigkeitsprobleme - verbleibt unkonfiguriert
vlan (1.9-3) wird eingerichtet ...
iputils-arping (3:20100418-3) wird eingerichtet ...
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von resource-agents-pve:
resource-agents-pve hängt ab von redhat-cluster-pve; aber:
Paket redhat-cluster-pve ist noch nicht konfiguriert.
dpkg: Fehler beim Bearbeiten von resource-agents-pve (--configure):
Abhängigkeitsprobleme - verbleibt unkonfiguriert
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von pve-manager:
pve-manager hängt ab von qemu-server (>= 1.1-1); aber:
Paket qemu-server ist noch nicht konfiguriert.
pve-manager hängt ab von pve-cluster; aber:
Paket pve-cluster ist noch nicht konfiguriert.
pve-manager hängt ab von libpve-storage-perl; aber:
Paket libpve-storage-perl ist noch nicht konfiguriert.
pve-manager hängt ab von libpve-access-control; aber:
Paket libpve-access-control ist noch nicht konfiguriert.
pve-manager hängt ab von redhat-cluster-pve; aber:
Paket redhat-cluster-pve ist noch nicht konfiguriert.
pve-manager hängt ab von resource-agents-pve; aber:
Paket resource-agents-pve ist noch nicht konfiguriert.
pve-manager hängt ab von fence-agents-pve; aber:
Paket fence-agents-pve ist noch nicht konfiguriert.
dpkg: Fehler beim Bearbeiten von pve-manager (--configure):
Abhängigkeitsprobleme - verbleibt unkonfiguriert
vzquota (3.0.12-3) wird eingerichtet ...
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von vzctl:
vzctl hängt ab von pve-cluster; aber:
Paket pve-cluster ist noch nicht konfiguriert.
dpkg: Fehler beim Bearbeiten von vzctl (--configure):
Abhängigkeitsprobleme - verbleibt unkonfiguriert
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von proxmox-ve-2.6.32:
proxmox-ve-2.6.32 hängt ab von pve-manager; aber:
Paket pve-manager ist noch nicht konfiguriert.
proxmox-ve-2.6.32 hängt ab von qemu-server; aber:
Paket qemu-server ist noch nicht konfiguriert.
proxmox-ve-2.6.32 hängt ab von vzctl (>= 3.0.29); aber:
Paket vzctl ist noch nicht konfiguriert.
dpkg: Fehler beim Bearbeiten von proxmox-ve-2.6.32 (--configure):
Abhängigkeitsprobleme - verbleibt unkonfiguriert
shared-mime-info (0.71-4) wird eingerichtet ...
ssl-cert (1.0.28) wird eingerichtet ...
ttf-dejavu-extra (2.31-1) wird eingerichtet ...
ttf-dejavu (2.31-1) wird eingerichtet ...
xfonts-encodings (1:1.0.3-1) wird eingerichtet ...
xfonts-utils (1:7.5+2) wird eingerichtet ...
x-ttcidfont-conf (32) wird eingerichtet ...
Updating font configuration of x-ttcidfont-conf...
Cleaning up category cmap..
Cleaning up category cid..
Cleaning up category truetype..
Updating category truetype..
Updating category cid..
Updating category cmap..
fancontrol (1:3.1.2-6) wird eingerichtet ...
libbsd-resource-perl (1.2904-1) wird eingerichtet ...
lm-sensors (1:3.1.2-6) wird eingerichtet ...
Trigger für python-central werden verarbeitet ...
Trigger für python-support werden verarbeitet ...
Fehler traten auf beim Bearbeiten von:
pve-cluster
redhat-cluster-pve
fence-agents-pve
libpve-access-control
clvm
libpve-storage-perl
qemu-server
resource-agents-pve
pve-manager
vzctl
proxmox-ve-2.6.32

dietmar
02-21-2012, 04:42 PM
Hi Guys,
today i have tried to install the Proxmox RC1 on Debian Squeeze (http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze)


Please make sure that your hostname is resolvable via /etc/hosts, i.e you need an entry in /etc/hosts which assigns an IP address to that hostname.

chewbaccus
02-21-2012, 04:53 PM
Please make sure that your hostname is resolvable via /etc/hosts, i.e you need an entry in /etc/hosts which assigns an IP address to that hostname.

I still have an entry in /etc/hosts !!!

Here my hosts file:


127.0.0.1 localhost
127.0.1.1 prox
192.168.0.245 prox

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

dietmar
02-21-2012, 05:43 PM
I still have an entry in /etc/hosts !!!


Please remove '127.0.1.1 prox'

Loredo
02-21-2012, 06:27 PM
I just realized that citadel gets installed on the host. I am not sure for what reason, as least it seems there are unneeded services running like pop3, imap etc...
Could somebody explain to me for what citadel is being used inside of Proxmox?

kcalliauw
02-21-2012, 08:14 PM
I just realized that citadel gets installed on the host. I am not sure for what reason, as least it seems there are unneeded services running like pop3, imap etc...
Could somebody explain to me for what citadel is being used inside of Proxmox?

This is not the case with the ISO install. I have these open ports 22 (ssh),25 (mail), 80, 443 and 8006 (apache), 85 (pvedaemon) + portmap (111) and rpc.statd port (1732 here) for NFS.

Can't speak for the standalone install on top of an existing OS as I've never used that.

Best regards,
Koen

chewbaccus
02-21-2012, 10:41 PM
I think that the official installation-manual contains an incorrect order.

I would like to present my way of installation for Proxmox 2.0 RC1 on Debian Squeeze



01.
Install Debian Squeeze (amd64). Version 6.0.3 with LVM based Partitioning

02.
- Set a fixed IP and make an entry in /etc/hosts
Caution: Debian sets an Value like "127.0.1.1".
This must be delete !!
Only two entries: 127.0.0.1 and your Host-IP
-Reboot

03.
- edit sources.list
- download the repository key
- aptitude update
- aptitude full-upgrade

04.
- Install the packages: ntp, ssh, postfix, ksm-control-daemon vzprocps
( I think LVM2 is not necessary, because it was installed by Debian and
upgraded by "aptitude full-upgrade")
- Install grub2
- Reboot

05.
- install pve-kernel-2.6.32-7-pve
- reboot

06.
- install pve-firmware
- reboot

07.
- install proxmox-ve-2.6.32
- a2ensite pve-redirect.conf
- reboot


INSTALLATION FINISHED

In this way i could perform an error-free installation

Loredo
02-22-2012, 03:46 AM
I think that the official installation-manual contains an incorrect order.
...
In this way i could perform an error-free installation

Thnx, I think you are right. Installing postfix beforehand resolved the issue.
Although one could simply remove the citadel stuff after going through the official install guide I prefer a more perfect clean install :-)

jleg
02-22-2012, 12:44 PM
user stuff looks quite nice - though i seem to have a little issue; trying to add a user based on PAM, i only and always get

create user failed: command '/usr/sbin/usermod -p '$5$eoeBVGSZ$mppiCb2wN3CCMZOsY8gYQcRSltGvoWOnEWAG0 7z1XM/' gnagna' failed: exit code 6 (500)

(which makes somehow sense since there is no user yet for 'usermod'...)

another small glitch - updating from last beta was only possible after doing a manual
update-rc portmap defaults

otherwise, dependency "nfs-common" broke, and all pve* packages subsequently...

kcalliauw
02-22-2012, 01:29 PM
I saw the same thing with the usermod error, then switched to Proxmox VE authentication.
Didn't have to do the NFS stuff though (beta3 installed through ISO).

/K


user stuff looks quite nice - though i seem to have a little issue; trying to add a user based on PAM, i only and always get

create user failed: command '/usr/sbin/usermod -p '$5$eoeBVGSZ$mppiCb2wN3CCMZOsY8gYQcRSltGvoWOnEWAG0 7z1XM/' gnagna' failed: exit code 6 (500)

(which makes somehow sense since there is no user yet for 'usermod'...)

another small glitch - updating from last beta was only possible after doing a manual
update-rc portmap defaults

otherwise, dependency "nfs-common" broke, and all pve* packages subsequently...

dietmar
02-22-2012, 02:25 PM
(which makes somehow sense since there is no user yet for 'usermod'...)


You can only add existing pam users (we do not create them).

jleg
02-22-2012, 03:34 PM
You can only add existing pam users (we do not create them).

ah, i see...
(perhaps worth a hint in message...)

ashes
02-23-2012, 03:44 PM
hello , what about supporting freeBSD? this current version freebsd is not working on it.


[root@freebsd ~]# pciconf -lv
hostb0@pci0:0:0:0: class=0x060000 card=0x11001af4 chip=0x12378086 rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '440FX - 82441FX PMC [Natoma]'
class = bridge
subclass = HOST-PCI
isab0@pci0:0:1:0: class=0x060100 card=0x11001af4 chip=0x70008086 rev=0x00 hdr=0x00
vendor = 'Intel Corporation'
device = '82371SB PIIX3 ISA [Natoma/Triton II]'
class = bridge
subclass = PCI-ISA
atapci0@pci0:0:1:1: class=0x010180 card=0x11001af4 chip=0x70108086 rev=0x00 hdr=0x00
vendor = 'Intel Corporation'
device = '82371SB PIIX3 IDE [Natoma/Triton II]'
class = mass storage
subclass = ATA
none0@pci0:0:1:3: class=0x068000 card=0x11001af4 chip=0x71138086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = '82371AB/EB/MB PIIX4 ACPI'
class = bridge
vgapci0@pci0:0:2:0: class=0x030000 card=0x11001af4 chip=0x11111234 rev=0x00 hdr=0x00
vendor = 'Technical Corp.'
class = display
subclass = VGA
virtio_pci0@pci0:0:3:0: class=0x020000 card=0x00011af4 chip=0x10001af4 rev=0x00 hdr=0x00
vendor = 'Red Hat, Inc'
device = 'Virtio network device'
class = network
subclass = ethernet
virtio_pci1@pci0:0:4:0: class=0x050000 card=0x00051af4 chip=0x10021af4 rev=0x00 hdr=0x00
vendor = 'Red Hat, Inc'
device = 'Virtio memory balloon'
class = memory
subclass = RAM
virtio_pci2@pci0:0:5:0: class=0x010000 card=0x00021af4 chip=0x10011af4 rev=0x00 hdr=0x00
vendor = 'Red Hat, Inc'
device = 'Virtio block device'
class = mass storage
subclass = SCSI


[root@freebsd ~]# uname -a
FreeBSD freebsd.xxx.xxx 9.0-STABLE FreeBSD 9.0-STABLE #0: Wed Feb 22 13:34:16 EET 2012 root@freebsd.xxx.xxx:/usr/obj/usr/src/sys/fbsd amd64

between two guests ( freebsd - linux )

[root@freebsd ~]# iperf -s
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 64.0 KByte (default)
------------------------------------------------------------
[ 4] local yy.yy.yy.yy port 5001 connected with xx.xx.xx.xx port 45727
[ ID] Interval Transfer Bandwidth
[ 4] 0.0-10.0 sec 13.5 GBytes 11.6 Gbits/sec

erikje
02-23-2012, 09:57 PM
Since the upgrade to RC1 i've lost VNC connectivity, the console popup appears but no content, apache error log complains:

File does not exist: /usr/share/pve-manager/root/com.tigervnc.vncviewer.VncViewer, referer: https://192.168.178.3:8006/?console=shell&node=proxmox

dietmar
02-24-2012, 06:40 AM
Since the upgrade to RC1 i've lost VNC connectivity

Please can you open new thread for that?

muzzol
02-29-2012, 03:14 PM
what pam service is pve using?

dietmar
02-29-2012, 05:19 PM
what pam service is pve using?

The service is called 'common-auth'

muzzol
03-07-2012, 11:15 AM
all our servers are usually ldaped with specific settings, mainly group filtering.

is there any diference in using your integrated ldap auth than tipical pam+ldap setup?

dietmar
03-07-2012, 11:31 AM
is there any diference in using your integrated ldap auth than tipical pam+ldap setup?

I can't see the advantage of using pam here.

muzzol
03-07-2012, 12:52 PM
i've installed RC1 and when configuring ldap in auth settings i can't see any way to filter ldap query. on most servers we usually only allow to appear on system (getent passwd) a subset of our whole user tree.

is that possible in PVE 2?

dietmar
03-07-2012, 01:25 PM
i've installed RC1 and when configuring ldap in auth settings i can't see any way to filter ldap query. on most servers we usually only allow to appear on system (getent passwd) a subset of our whole user tree.


We do not automatically import any user (you need to add/enable them manually). LDAP is only used to verify the password.

spacemind
03-19-2012, 12:09 PM
Hi There,

I have px 2.0 rc1 running with an KVM windows xp but i cannot get the audio card working for windows xp, when i add the args: -soundhw all to vm100.conf i could not get the vm to run, i have a stream server for the hotel.


Thanks

tin
03-20-2012, 05:58 AM
I know the official and safe answer to this, but is RC1 close enough to finished that anyone here would use it for a low performance production server? Is it roughly on par with 1.9 now anyway?

preocupao
03-21-2012, 01:31 PM
We use it on production, 2 servers with about 20 CT in each one.

We dont have more CT because have a non optimal hardware, no physical RAID controller and dont have write-back mode as option :(

charnov
03-22-2012, 05:10 PM
My entire enterprise of Windows 2003/2008 R2 servers are running on this. 100 users, 80GB exchange 2003 with two front ends, BES server, AD, etc. 17 windows servers and 6 Linux/BSD on two physical Dell R410's with 32GB ram each. Barely gets above a .5 load and with KSM uses less than 20GB on each. Works like a champ and when it's time to expand, I get another R410, have it up and running in about 15 minutes and migrate some VM's. Awesome!

Networking, backups, and ISO's are the only annoyances I have. VMWare spoiled me.

rmoglia
03-25-2012, 04:08 AM
I´m change my remote machine then i gain a oportunity to make a test try migrate to lenny to squeeze. I removed every packages from pmox 1.9. Upgrade to debian squezee and try install packages of 2.0 without sucess.

pve kernel up and running but dont started bridged interface remote team put eth0 and bringup the machine. I make dump of every machine to try a simulated "migration". Some data on /var/lib/vz then i move the data and restore the dump of machine without data directories and move back thats my idea.

I recive some errors. i have more 2 days for any tests. anyone have any idea? If upgrade or reinstall over existent machine can be done i need buy a new machine for upgrade every pmox 1.9 instalation.

Now all machines of this machine ready migrated to pmox 2.0 and all on prodution enviroment on new machine squeeze fresh install. But i can´t use existent machine with lenny upgrated to squezze for install pmox 2.0 i try many times without sucess. I don´t need upgrade just a complete reinstall using existent machine.


dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve-2.6.32:
proxmox-ve-2.6.32 depends on pve-manager; however:
Package pve-manager is not configured yet.
dpkg: error processing proxmox-ve-2.6.32 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libpve-access-control:
libpve-access-control depends on pve-cluster; however:
Package pve-cluster is not configured yet.
dpkg: error processing libpve-access-control (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of qemu-server:
qemu-server depends on pve-cluster; however:
Package pve-cluster is not configured yet.
dpkg: error processing qemu-server (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of redhat-cluster-pve:
redhat-cluster-pve depends on pve-cluster; however:
Package pve-cluster is not configured yet.
dpkg: error processing redhat-cluster-pve (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of vzctl:
vzctl depends on pve-cluster; however:
Package pve-cluster is not configured yet.
dpkg: error processing vzctl (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of resource-agents-pve:
resource-agents-pve depends on redhat-cluster-pve; however:
Package redhat-cluster-pve is not configured yet.
dpkg: error processing resource-agents-pve (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of fence-agents-pve:
fence-agents-pve depends on redhat-cluster-pve; however:
Package redhat-cluster-pve is not configured yet.
dpkg: error processing fence-agents-pve (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of clvm:
clvm depends on redhat-cluster-pve; however:
Package redhat-cluster-pve is not configured yet.
dpkg: error processing clvm (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libpve-storage-perl:
libpve-storage-perl depends on clvm; however:
Package clvm is not configured yet.
dpkg: error processing libpve-storage-perl (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
pve-cluster
pve-manager
proxmox-ve-2.6.32
libpve-access-control
qemu-server
redhat-cluster-pve
vzctl
resource-agents-pve
fence-agents-pve
clvm
libpve-storage-perl



I have 2 days for tests before drop the remote machine and i can put the machine for senior team tests. i keep some data on /var/lib/vz and this monted and i dumped 2 machines for tests one KVM with windows and one openvz. my /etc/hosts is correct any ideas?

tom
03-26-2012, 04:54 PM
we will release the upgrade script very soon, so please wait for 1.9 to 2.0 upgrades.

sistemas.defensorba
03-29-2012, 12:14 AM
Hi!, i have a little question for proxmox forum guys :D
We're testing the new release candidate to use it in the future in our production servers.
We've installed proxmox 2.0 -8d4f53a0-20 (downloaded from the proxmox website).
But... we faced a problem when we need to install iscsi-scst package and have it as a module too, to export a iscsi target (tape device in this case).
Anyone could help us? please we're really interested in using proxmox 2.0

Thanks in advance!
Maximiliano (from Argentina).

P/D: any estimated date for the release of version 2.0??

rmoglia
03-29-2012, 12:25 AM
I try help today lenny repositories droped. I belive No more updates to lenny.


Install these packages without verification [y/N]? y
Err http://debian.mirror.iweb.ca lenny/main netselect 0.3.ds1-12.1
404 Not Found [IP: 70.38.0.135 80]
Err http://debian.mirror.iweb.ca lenny/main netselect-apt 0.3.ds1-12.1
404 Not Found [IP: 70.38.0.135 80]
Failed to fetch http://debian.mirror.iweb.ca/debian/pool/main/n/netselect/netselect_0.3.ds1-12.1_amd64.deb 404 Not Found [IP: 70.38.0.135 80]
Failed to fetch http://debian.mirror.iweb.ca/debian/pool/main/n/netselect/netselect-apt_0.3.ds1-12.1_all.deb 404 Not Found [IP: 70.38.0.135 80]
E: Some files failed to download

I´m searched on us repositories for lenny or old stable dist everyting appers totally droped.

rmoglia
03-29-2012, 12:29 AM
I´m using basic features running 2 windows machine with KVM and 2 linux instances with openvz. High traffic aplications on linux. I have a little latence problem on one windows machine but on rest everyting is fine. For me appers ready production servers. You try install kernel-headers package and compile your module? I don´t no if pmox kernel is avaliable with apt-get source try put source line for pmox repository and customize your kernel to include your module.

bread-baker
03-29-2012, 01:44 AM
Hi!, i have a little question for proxmox forum guys :D
We're testing the new release candidate to use it in the future in our production servers.
We've installed proxmox 2.0 -8d4f53a0-20 (downloaded from the proxmox website).
But... we faced a problem when we need to install iscsi-scst package and have it as a module too, to export a iscsi target (tape device in this case).
Anyone could help us? please we're really interested in using proxmox 2.0

Thanks in advance!
Maximiliano (from Argentina).

P/D: any estimated date for the release of version 2.0??



Hello

It would best I think for you to post a new thread.

best regards,
Rob

dietmar
03-29-2012, 07:19 AM
But... we faced a problem when we need to install iscsi-scst package and have it as a module too, to export a iscsi target (tape device in this case).

We was also unable to compile SCST for newer kernels, so we never included that in newer kernel releases. Instead we include the iscsi_trgt module. But
that does not support tapes AFAIK.

twister988
03-30-2012, 10:48 AM
Support and Updates for Lenny were cancelled in February...
I have the same problem.

Time to upgrade from 1.9 to 2.0 :)

Feedback is good, i think it is stable enough.