Okay, so, digging a little deeper, it appears that the Proxmox Ceph 15.2.15 packages for Buster and Bullseye are just different enough (they have different CEPH_GIT_VERs) to trigger this warning after the first node has been upgraded. I'm not sure if this constitutes a bug or not, since the...
I'm finally getting around to upgrading to PVE 7 on my three-node hyperconverged cluster, and I'm following the upgrade guide in the Wiki. I installed all the PVE 6.4 upgrades on all three nodes, then upgraded the cluster to Ceph Octopus. Once that was done, I ran pve6to7 on one of the three...
In my experience (and that of others, according to the links I mentioned above) kvm64 along with the default flags guarantees failure (well, technically, "migration success", followed by a total hard-lock of the VM at some point afterwards).
The blog post I referenced suggested the following...
Following on from this forum thread and this bug report, I was wondering what the current recommendation is for Linux VM CPU flags (or other settings) to allow migrating VMs between AMD- and Intel-based hosts? I couldn't find anything in the documentation, the most recent advice on that forum...
nginx isn't used directly by the Proxmox GUI; it only exists as a kind of overlay. The only way you'd lose access to the Proxmox GUI or SSH is if you configured nginx to use port 8006 or 22 (which would be basically impossible following the instructions above), and even then restarting nginx...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.