Proxmox VE 2.0 rc1 released!

martin

Proxmox Staff Member
Staff member
Apr 28, 2005
748
1,626
223
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

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

Happy testing, waiting for feedback!
__________________
Best regards,

Martin Maurer
Proxmox VE project leader
 
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
 
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.
 
not yet, but I would really like to see a worry free spice, especially on the client side.
 
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.

Then you really should remove the dd info since its not working.
 
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.
 
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.
 
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
 
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
 
hello , what about supporting freeBSD? this current version freebsd is not working on it.
 
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.
 
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
Code:
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
Code:
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:
Code:
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
 
Last edited:
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
 
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.
 
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!
 
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.
 

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!