Proxmox VE 2.0 final release !!!

Thank for your on time release. I am wondering how I should go with upgrade. I can build a new server and go with clean install and restore vms. Or easier way, just use upgrade script. But wiki suggests first way. Is there a real advantages of going with clean install?

Thanks
 
Good to see it's finally final :p

Now I just have to find some time where I can take the server down for an hour or 2 and not get too many complaints.
 
we planned to migrate our 6 node environment by getting one node empty of mvs, updating and then moving vms again to that node.

as clustering system is completly diferent our approach is not possible. can we just dump mvs, move tgz over the network and import them again in new(updated) nodes?
 
thanks for quick response.

so, just to clarify and calm my admin-paranoic brain: any dump/export can be imported in 2.0 with 100% compatibility and without performing any additional task?
 
thanks for quick response.

so, just to clarify and calm my admin-paranoic brain: any dump/export can be imported in 2.0 with 100% compatibility and without performing any additional task?

depends on your VM´s and VM settings, especially windows KVM guests could complain about some hardware changes, in rare cases you need to boot in safe-mode to get networking again. but test, test and test.
 
Upgrading from RC1 to 2.0 Final gives me this:

root@vm1:~# aptitude full-upgrade
The following packages will be upgraded:
file libmagic1 libpve-access-control libpve-common-perl pve-manager pve-qemu-kvm qemu-server
7 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 4,222 kB of archives. After unpacking 16.4 kB will be used.
Do you want to continue? [Y/n/?] Y
Get:1 http://security.debian.org/ squeeze/updates/main file amd64 5.04-5+squeeze1 [49.9 kB]
Err http://download.proxmox.com/debian/ squeeze/pve libpve-common-perl all 1.0-17
404 Not Found
Get:2 http://download.proxmox.com/debian/ squeeze/pve libpve-access-control amd64 1.0-17 [29.6 kB]
Err http://download.proxmox.com/debian/ squeeze/pve pve-qemu-kvm amd64 1.0-5
404 Not Found
Err http://download.proxmox.com/debian/ squeeze/pve qemu-server amd64 2.0-25
404 Not Found
Err http://download.proxmox.com/debian/ squeeze/pve pve-manager all 2.0-38
404 Not Found
Get:3 http://security.debian.org/ squeeze/updates/main libmagic1 amd64 5.04-5+squeeze1 [235 kB]
Fetched 315 kB in 1s (201 kB/s)
Reading changelogs... Done
(Reading database ... 30506 files and directories currently installed.)
Preparing to replace file 5.04-5 (using .../file_5.04-5+squeeze1_amd64.deb) ...
Unpacking replacement file ...
Preparing to replace libmagic1 5.04-5 (using .../libmagic1_5.04-5+squeeze1_amd64.deb) ...
Unpacking replacement libmagic1 ...
Preparing to replace libpve-access-control 1.0-16 (using .../libpve-access-control_1.0-17_amd64.deb) ...
Unpacking replacement libpve-access-control ...
Processing triggers for man-db ...
Processing triggers for pve-manager ...
Restarting PVE Daemon: pvedaemon.
Restarting PVE Status Daemon: pvestatd.
Restarting web server: apache2 ... waiting .
Setting up libmagic1 (5.04-5+squeeze1) ...
Setting up file (5.04-5+squeeze1) ...
Setting up libpve-access-control (1.0-17) ...
E: Failed to fetch http://download.proxmox.com/debian/dists/squeeze/pve/binary-amd64/libpve-common-perl_1.0-17_all.deb: 404 Not Found

Am I missing something?
 
after upgrade got:
The following partially installed packages will be configured:
linux-image-2.6.32-5-amd64
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Setting up linux-image-2.6.32-5-amd64 (2.6.32-41squeeze2) ...
Running depmod.
Running update-initramfs.
update-initramfs: Generating /boot/initrd.img-2.6.32-5-amd64
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for module r8169
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 2.6.32-5-amd64 /boot/vmlinuz-2.6.32-5-amd64
run-parts: executing /etc/kernel/postinst.d/zz-lilo 2.6.32-5-amd64 /boot/vmlinuz-2.6.32-5-amd64
Warning: Not updating LILO; /etc/lilo.conf not found
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 2.6.32-5-amd64 /boot/vmlinuz-2.6.32-5-amd64
Generating grub.cfg ...
/usr/sbin/grub-probe: error: no such disk.
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-2.6.32-5-amd64.postinst line 799.
dpkg: error processing linux-image-2.6.32-5-amd64 (--configure):
subprocess installed post-installation script returned error exit status 2
configured to not write apport reports
Errors were encountered while processing:
linux-image-2.6.32-5-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up linux-image-2.6.32-5-amd64 (2.6.32-41squeeze2) ...
Running depmod.
Running update-initramfs.
update-initramfs: Generating /boot/initrd.img-2.6.32-5-amd64
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for module r8169
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 2.6.32-5-amd64 /boot/vmlinuz-2.6.32-5-amd64
run-parts: executing /etc/kernel/postinst.d/zz-lilo 2.6.32-5-amd64 /boot/vmlinuz-2.6.32-5-amd64
Warning: Not updating LILO; /etc/lilo.conf not found
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 2.6.32-5-amd64 /boot/vmlinuz-2.6.32-5-amd64
Generating grub.cfg ...
/usr/sbin/grub-probe: error: no such disk.
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-2.6.32-5-amd64.postinst line 799.
dpkg: error processing linux-image-2.6.32-5-amd64 (--configure):
subprocess installed post-installation script returned error exit status 2
Errors were encountered while processing:
linux-image-2.6.32-5-amd64


Any suggestions how to fix this?
 
Great news, congratulations to the proxmox team and everyone who waited for this to happen!
 
Just wanted to say how impressed I am with 2.0.

Have just moved 6 hosts plus SAN backend from 1.9 to 2.0 and it went seamlessly.

Many thanks to all the Proxmox team - you guys are absolute legends.

c:)
 
Thanks proxmox team!!! great product, great developers, great community...
I love Proxmox !!!

And, what are the storage requirements for open vz?
 
Last edited:
Holy cow! Proxmox VE 2.0 is absolutly amazing!!! I've got to admit Proxmox appears to be one of the best open source projects out there!

Look out VMware, here comes Proxmox :D
 
Yes have to agree Proxmox VE 2.0 is great works right out of the box. Easy and simple to use, but importantly it really maximises the hardware efficiently. I tried using alternatives but my host machine really struggled. This is a very good quality product. Well done to the team.
 

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!