this post was submitted on 30 Jun 2023
10 points (100.0% liked)

Selfhosted

40006 readers
1247 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 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
HybridSarcasm@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
10
Upgraded Proxmox 7 to 8 (lemmy.fwgx.uk)
submitted 1 year ago by blackstrat@lemmy.fwgx.uk to c/selfhosted@lemmy.world
8 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
[–] thomas@lemmy.zell-mbc.com 1 points 1 year ago* (last edited 1 year ago) (1 children)

:-)

But seriously, I was wondering about the requirement to shutdown the VM's and couldn't come up with a solid reason? I mean, even if QEMU/KVM/Kernel get replaced during a version upgrade or a more common update, all of these kick in only after the reboot? And how's me shutting down VMs manually different from the OS shutting down during a reboot?

I know I am speculating and may not have the fill picture, probably a question for the Proxmox team, there may be some corner case where this is indeed important.

By the way, Mexican or US black strat? :-)

[–] blackstrat@lemmy.fwgx.uk 0 points 1 year ago (1 children)

I have no idea why, but I thought there must be some good reason to document it and put the check in to the test tool.

I don't yet have a black strat. I'm considering the Player series of a non-Fender option of a Vintage V6.

[–] jackiebrown@lemmy.world 1 points 1 year ago

I don't know why but figured the same as you. If they bothered to document it, I'd bother to follow it. I did the download only option too since I also run opnsense from a VM.