Proxmox Virtual Environment 9.0 with Debian 13 released
www.proxmox.com
Latest announcements for Proxmox.
  • Midnight Wolf@lemmy.worldEnglish
    7·
    5 hours ago

    Yay, it only took 2 hours and the help of an llm since the upgrade corrupted my lvm metadata! Little bit of post cleanup and verifying everything works. Now I can go to sleep (it’s 5am).

    Wasn’t that bad, but not exactly relaxing. And when my VMs threw a useless error (‘can’t start need manual fix’) I might have slightly panicked…

  • Damage@feddit.itEnglish
    6·
    7 hours ago

    ZFS now supports adding new devices to existing RAIDZ pools with minimal downtime.

    Yes!!

    • non_burglar@lemmy.worldEnglish
      21·
      2 hours ago

      Edit2: the following is no longer true, so ignore it.

      Why do you want this? There are very few valid use cases for it.

      Edit: this is a serious question. Adding a member to a vdev does not automatically move any of the parity or data distribution off the old vdev. You’ll not only have old data distributed on old vdev layout until you copy it back, but you’ll also now have a mix of io requests for old and new vdev layout, which will kill performance.

      Not to mention that the metadata is now stored for new layout, which means reads from the old layout will cause rw on both layouts. It’s not actually something anyone should want, unless they are really, really stuck for expansion.

      And we’re talking about a hypervisor here, so performance is likely a factor.

      Jim Salter did a couple writeups on this.

      • Saik0@lemmy.saik0.comEnglish
        3·
        3 hours ago

        Adding a member to a vdev does not automatically move any of the parity or data distribution off the old vdev.

        Yes it does. ZFS does a full resilver after the addition. Jim Salter’s write ups are from 4 years ago. Shit changes.

        Edit: and even if it didn’t… It’s trivial to write a script that rewrites all the data to move it into the new structure. To say there’s no valid cases when even in 2021 there was an answer to the problem is a bit crazy.

  • littleomid@feddit.orgEnglish
    15·
    10 hours ago

    For beginners here: do not run apt upgrade!! Read the documentation on how to upgrade properly.

    • beerclue@lemmy.worldOPEnglish
      9·
      9 hours ago

      It’s always good to read the docs, but I often skip myself :)

      They have this nifty tool called pve8to9 that you could run before upgrading, to check if everything is healthy.

      I have a 3 node cluster, so I usually migrate my VMs to a different node and do my maintenance then, with minimal risks.

  • TheUnicornOfPerfidy@feddit.ukEnglish
    4·
    10 hours ago

    As a person who just installed proxmox for the first time a couple of weeks ago, does this allow me to fix some of my mistakes and convert VMs to LXCs?

      • ikidd@lemmy.worldEnglish
        23·
        14 hours ago

        Probably for the best. Upgrades on the first release haven’t had a stellar record

        • Moonrise2473@feddit.itEnglish
          3·
          11 hours ago

          Exactly, for example I missed the note that updating truenas to the latest version disables and hides all the virtual machines (theoretically they can get migrated to the new engine but it gave me some weird error. Luckily truenas can be downgraded easily.)

          Now, 3 months after the First release of the update, those virtual machines aren’t disabled and hidden anymore

            • Moonrise2473@feddit.itEnglish
              4·
              10 hours ago

              scale, they got rid of the kvm emulator in the last release and i was devastated to see all my VM gone. The “migration” consists in you migrate the disk image to the new directory, then you make a new VM… IF you knew that BEFORE the update and took note of all the settings because the old VM menu is gone!

              but also it’s clear than core is on life support

  • coffeetastesbadlikecoffee@sh.itjust.worksEnglish
    4·
    11 hours ago

    This is awesome, I am going to imediatly get a test cluster set up when I get to work. Snapshots with FC support was the only major thing (appart from Veeam support) holding us back from switching to Proxmox. The HA improvements also sound nice!

  • etchinghillside@reddthat.comEnglish
    12·
    15 hours ago

    Not sure I want to check how far behind I am. How rough are these upgrades? I’ve got most things under Terraform and Ansible but am still procrastinating under the fear of losing a weekend regiggling things.

    • phanto@lemmy.caEnglish
      10·
      13 hours ago

      I just did three nodes this evening from 8.4.1 to 9, no issues other than a bit of farting around with my sources.list files.

      Not noticing anything significant, but I haven’t tried the mobile interface yet.

    • CmdrShepard49@sh.itjust.worksEnglish
      6·
      15 hours ago

      I’d also like to know.

      I built a new machine seceral months back with PVE and got the hang of it but it’s been “set it and forget it” since then due to everything running smoothly. Now I don’t remember half the things I learned and don’t want to get in over my head running into issues during a major upgrade. I definitely do want the ability to expand my ZFS pool so I will need to bite the bullet eventually.