Like you I have OPNsense in a VM on one of my PVEs. But I only made sure the nigthly VM back up ran and didnt even bother shutting down the VMs during the upgrade. The VMs got restarted during the final reboot, as the would with every other reboot, and I was back in business.
It's a bold strategy, Cotton. I'm glad it worked out for you.
:-)
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? :-)
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.
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.
I've really come to appreciate having test systems working as a systems engineer. A simple virtualised install of Proxmox that replicates some small part of your environment is great to simply go through the upgrade once or twice.
I'd like to run a small cluster of mini PCs or have extra hardware running a mirror setup, but the cost has put me off.
I just did mine yesterday. One stopped responding mid-upgrade and I wasn't able to reconnect, but I was able to log in at the console and run dpkg --reconfigure -a until I got the network back, then apt install --reinstall proxmox-ve pve-manager got those packages to finish installing, then everything worked.
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.
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.
Sorry for the late reply. Using ZFS and replicating the VM first makes it really quick. Less than 5 minutes of downtime.
This is one of the reasons I am very against virtualizing core foundational services like routers and NAS. It just causes way too many headaches.
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:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!