I had pve 7.x running on a spare laptop that I had kicking around. Everything was working well until the upgrade. Until I realized that I couldn't spin up a new vm after it's creation. Took me a minute to realized that my issue was that I chose the default CPU type (x86-64-v2-AES). I then changed that to x86-64-v2. Then all was well in the world. At least my world that is.
9 Comments
andreluis034@lm.put.tf · 2 pts · 3y
I almost fucked it up because I forgot to update the ceph repo, but besides that all smooth.
peterbata@lemmy.ml · 1 pts · 3y
d4nm3d@lemmy.ml · 1 pts · 3y
I just did it, i hadn't realised 8.0 had gone gold..
Process was simple enough to be honest.. I did the in place upgrade detailed here :
https://pve.proxmox.com/wiki/Upgrade_from_7_to_8
thusband@lemmy.ml · 1 pts · 3y
Anybody use the tteck Proxmox upgrade script to upgrade? I've heard good things about it
g7s@lemmy.ml · 1 pts · 3y
Updated 3 nodes in a cluster, no problem at all.
Just update your sources with a $sed command, update the system, make sure to run pve7to8 a few times during that process and then start upgrading.
peterbata@lemmy.ml · 1 pts · 3y
I had pve 7.x running on a spare laptop that I had kicking around. Everything was working well until the upgrade. Until I realized that I couldn't spin up a new vm after it's creation. Took me a minute to realized that my issue was that I chose the default CPU type (x86-64-v2-AES). I then changed that to x86-64-v2. Then all was well in the world. At least my world that is.
techviator@lemmy.ml · 1 pts · 3y
I just upgraded a few minutes ago.
All went smooth except for an ssh script I use, because the ssh algorithms changed. It was easy to fix though.
peterbata@lemmy.ml · 1 pts · 3y
Good to hear
jeffers00n@lemmy.ml · 0 pts · 3y
I usually give it a few weeks before I upgrade to a new major version just to be safe.
peterbata@lemmy.ml · 1 pts · 3y
That's exactly what I usually do. But, I knew that if something did go wrong rolling back to an older version wasn't going to be a big deal.