zstd uncompress failed with error code 20
FATAL ERROR: writer: failed to read/uncompress file /target/usr/lib/python3.11/re/__pycache__/_parser.cpython-311.pyc
Yes, no matter which repository you use (enterprise or no-subscription), the upgrade should work. And with a valid subscription you are likely using the enterprise repository anyway.
make sure the machine has enough RAM - these errors sound like it runs OOM - I'd suggest at least 4G (for the installer - definitely quite a bit more if you want to run any kind of workload on it).
I am using Proxmox with my IBM M3 x3650 rack server, I have dual CPUs.Yes, no matter which repository you use (enterprise or no-subscription), the upgrade should work. And with a valid subscription you are likely using the enterprise repository anyway.
Most likely two. If you have Proxmox VE already installed you can see how many sockets are in use. Go to {node}->Summary and check the line with the CPU info. At the end it will tell you how many sockets are in use.
pvetest repository: [1] with either the pve-no-subscription repository: [2], if you do not have an active subscription or the pve-enterprise repository: [3], if you have one.apt update and: apt full-upgrade (or: apt dist-upgrade).replace tests repos by no-subscription or enterprise repo if you have a license , then apt update, apt dist-upgrade.
Well with subscription level basic and higher, where higher means naturally not only more features but also more attention, you get access to the experienced enterprise support team via the private enterprise ticket system, where you can share much more details about your setups without risking privacy exposure, and they will then try their best to help you as per the support agreement. So yes, it can definitively help to diagnose issues, but we cannot give you a blank check that it can be 100% fixed.
If you can get around, you could try installing via the Proxmox VE ISO to test if just that would work, that could give you some hint if it's really the kernel issue or the like, or if it's bootloader/encryption misconfiguration (in combination with what Proxmox VE does).
Please check that secure boot is disabled, this is known to cause booting issues https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_12_Bookworm#PVE_Kernel_fails_to_boot
Of course I followed it as I could not invent my own procedure. Went down to systemctl reboot and then got stuck.
Yes, I have seen this note, but graded it as improbable as I could upgrade previously. Now I think I should actually check, in case the other kernels that boot well are merely insensitive to this. The facility is a bit bulky and I tend not to reboot without a need.
Integration is currently being worked upon: https://lists.proxmox.com/pipermail/pve-devel/2023-June/057271.html
virtiofsd manually and use qm set <ID> -args <arguments passed directly to QEMU> to add the necessary arguments to the VM. See the documentation for which arguments these are: https://virtio-fs.gitlab.io/howto-qemu.html
We don't sell licenses, as Proxmox VE is licensed under the AGPLv3, you probably mean Support Subscriptions, and yes, those are only bound to a specific server, not the version of Proxmox VE (albeit the enterprise support covers only versions that aren't EOL yet).