Meanwhile, Proxmox VE updated to version 5.0

    Proxmox logoThis news cannot be called loud, but the guys who saw Proxmox VE for a year two days ago released a new version of their brainchild - 5.0 .

    Of course, we are interested in the changes - are they pulling on the new major version. In my opinion, it’s quite, but the details, according to tradition, are under the cut.

    (For those who are not familiar with the words Proxmox VE, I’ll give a few words of description: “Proxmox Virtual Environment (Proxmox VE) is an open source virtualization system based on Debian GNU / Linux. It uses KVM and LXC as hypervisors. Virtual Machine Management and administration of the server itself is done through the web interface or through the standard Linux command line interface. ”)

    The official list of changes tells rather sparingly:

    • The assembly is performed on the Debian 9.0 "Stretch" package base (the previous version was based on Debian 8.0 "Jessie");
    • Uses Linux kernel 4.10
    • Used by QEMU 2.9
    • LXC has been updated to 2.0.8;
    • The possibility of asynchronous replication of storage between several nodes of the cluster is implemented. The function works when using ZFS, and today it is marked as “technology preview”;
    • Updated templates for building isolated LXC environments based on Debian, Ubuntu, CentOS, Fedora, OpenSUSE, Arch Linux, Gentoo and Alpine;
    • New / significantly improved remote console noVNC;
    • The composition includes the implementation of the Ceph 12.1.0 Luminous distributed file system (also marked with “technology preview”), with support for the new BlueStore backend, assembled by Proxmox staff;
    • Support for live migration using local storage;
    • Improved web-interface: improved filtering and batch operations, display of USB and Host PCI addresses;
    • Improved installation ISO-image;
    • Added tools for importing virtual machines from other hypervisors, including
      VMware and Hyper-V.
    • Documentation improvements, plus multiple bug fixes in older releases.

    I’ll describe a couple of things in more detail, a few more changes are clearly visible in the video from the authors of Proxmox VE, which is given at the end of the post.

    Replication storage


    We are talking about asynchronous replication , when once in a certain time the snapshot of the storage state is sent to another storage. This reduces network traffic, and allows you to make less hardware requirements.

    Proxmox 5.0 replication

    You can specify what and how often we replicate, and have a “fairly fresh” copy of the data from the main one on the other storage. It all depends on the tasks, but in many cases, for the purpose of quick recovery, even this approach is just a great option. I’ll clarify again, this function works between zfs repositories.

    Import VMs from other hypervisors


    Such kind of import is not needed every day, but when it is needed, it takes a lot of time to deal with it - it seems that now the process will be able to be reduced. Of course, import is also a problem of starting a guest on the basis of a new hypervisor (different guest OSs will react differently, say, to changing the list of equipment), but the functionality itself is relevant. Import is supposed to come from the most popular formats (say, vmdk), but most hypervisors can export machines to VMWare format today - after which we use the new qm utility function (called as qm importdisk), and we are already fighting the OS in the virtual machine.

    Only registered users can participate in the survey. Please come in.

    Are you interested in changes in PVE 5.0, will you be updated?

    • 31.7% Yes, updated soon 92
    • 24.4% Yes, updated, but after a while 71
    • 16.8% Yes, updated, but after testing 49
    • 5.1% No, and the old version works fine 15
    • 0.3% No, the old version does not work 1
    • 21.3% What is Proxmox VE? 62

    Also popular now: