this post was submitted on 30 Jun 2023
56 points (95.2% liked)

Selfhosted

40756 readers
892 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud
Loki
CannaVet
devve
HybridSarcasm
[email protected]
56
Upgraded Proxmox 7 to 8 (lemmy.fwgx.uk)
submitted 2 years ago by [email protected] to c/selfhosted
20 comments fedilink hide all child comments
 

This was a very nerve racking experience as I'd never gone through a major version Proxmox update before and I had spent a lot of time getting everything just so with lots of config around disk and VLANs. The instructions were also a big long page, which never fills me with confidence as it normally means there's a lot of holes to fall in to.

My initial issue was that it says to perform the upgrade with no VM's running, but it requires an internet connection and my router is Opnsense in a VM. Thankfully apt dist-upgrade --download-only, shutdown the Opnsense VM and then apt dist-upgrade did the trick.

A few config files changed and I always hate this part of Debian upgrades, but nothing major or of importance was impacted.

A nervous reboot and everything was back up running the new Proxmox with the new kernel. Surprisingly smooth overall and the most time consuming part by far was backing up my VM's just in case. The upgrade itself including reboot was probably 15 mins, the backups and making sure I was prepared and mentally ready was about an hour.

Compared to upgrading ESXi on old hardware like I was doing last year, it was a breeze.

Highly recommended, would upgrade again.

you are viewing a single comment's thread
view the rest of the comments
[–] mrginger 2 points 2 years ago (1 children)

I did the same a few months ago and was extremely nervous. I have a 4 node cluster running 30 VMs in production. After migrating the VMS off of one node I quickly realized what a pleasure it was to do it. No muss no fuss. Migrated the VMs back and continued on with the other 3.

[–] [email protected] 3 points 2 years ago (1 children)

That's pretty cool that it worked so well. Does migrating the VM's result in any downtime or is it a seamless cross over?

I waited a few days before upgrading as I wanted to make sure I wasn't going to get stung by any teething troubles. Would have ideally waited longer but had an ideal few hours available to do it without the family being annoyed by any downtime.

[–] mrginger 1 points 2 years ago

Sorry for the late reply. Using ZFS and replicating the VM first makes it really quick. Less than 5 minutes of downtime.