Proxmox VE 4.0 beta2 released!

martin

Proxmox Staff Member
Staff member
Apr 28, 2005
754
1,740
223
We are proud to announce the release of the second beta of our Proxmox VE 4.x family - based on the great Debian Jessie 8.2.0 and latest Linux Kernel 4.2.

So what's new in Proxmox VE 4.0 beta2?

  • Countless improvements for LXC, especially the integration in our storage model
  • Migration path from OpenVZ to LXC
  • Linux Kernel 4.2
  • Ceph Server packages (0.94.x - hammer release)
  • Embedded NoVNC console
  • Improved IPv6 support
  • Countless bug fixes
New and important wiki articles and release notes

Download
http://www.proxmox.com/en/downloads

Alternate ISO download:
http://download.proxmox.com/iso/

Bugtracker
https://bugzilla.proxmox.com

Source code
https://git.proxmox.com

FAQ

  • Beta2 installations can be updated to 4.0 stable without any problem (apt)
  • Beta1 installation can be also upgraded just via "apt-get update && apt-get dist-upgrade", using the pvetest repository
  • Upgrading from 3.4 to 4.x will be possible via an upgrade script, which we will provide later.
Please help us reaching the final release date by testing this beta2 and by providing feedback.

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

Martin Maurer
Proxmox VE project leader
 
Either I didn't read enough or the custom LXC bind mounts are broken in Beta2.
The config file /etc/pve/lxc/XXX/config is converted to /etc/pve/lxc/XXX.conf but the "lxc.mount.entry" lines don't reach the new config. As expected the custom mounts are not there on container startup.

LE: In case there are more idi^H^H^H users that don't pay attention like me: http://pve.proxmox.com/wiki/LXC_Bind_Mounts
 
Last edited:
The config file /etc/pve/lxc/XXX/config is converted to /etc/pve/lxc/XXX.conf but the "lxc.mount.entry" lines don't reach the new config.

Sorry, you need to re-add those change manually. It is not really possible to convert custom settings automatically.
 
That one you really have to explain. In what way is LVM limited?. As far as I can understand it's no more limited than any image based solution? ZFS is _not_ an option for allot of people. I know that you strive for perfect solutions, but the reality is that different needs requires different solutions.
 
Is there a way to upgrade from 3.4 to 4.x beta2? Looks like my issues with beta1 have been ironed out, and I'd like to kick the tires on my testing boxen without a fresh reinstall.

That one you really have to explain. In what way is LVM limited?. As far as I can understand it's no more limited than any image based solution? ZFS is _not_ an option for allot of people. I know that you strive for perfect solutions, but the reality is that different needs requires different solutions.

How is ZFS not an option? It's become a stable, mature file system that does a hell of a job.
 
How is ZFS not an option? It's become a stable, mature file system that does a hell of a job.

ZFS use quite allot of resources, and for a production critical environment I don't want to use zfs on Linux for a loooong while... I've lost enough filesystems due to bugs.... Don't get me wrong, zfs has allot of nice features.
I'm not going to create a discussion out of this, just want a simple answer why lvm aint an option. LXC has native support for lvm, so I don't understand why :(
 
Am I right in thinking that OpenVZ > LXC conversion requires two nodes? I only run a single node, is there still an upgrade path possible for me?
 
Good news ! Could you tell us when it is planned to release the stable/production-ready version ?

Thanks !
 
Hi,

All you need is a correct vzdump backup from the old OpenVZ container.

we had issues while running the migration. Please see other thread.
One import step was to put the following line into the config file, otherwise so login was possible
Code:
lxc.pts = 1024

Update: This is not visible in the new <VM-ID>.conf file anymore !!!

Br
Mr.X
 
I can't restore a lxc vzdump backup from proxmox 4.0 beta1 to beta2 (TASK ERROR: ERROR: archive contains no configuration file).
Have you a solution for this ??
 

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!