The problematic patch was identified and will be reverted for now, until we have a version which doesn't introduce this regression.
Upstream report: https://lore.kernel.org/qemu-devel/414848c6-3829-4120-b760-6db8d43c1ab5@proxmox.com/
You are not the first one to stumble upon this problem, e.g: https://bugzilla.proxmox.com/show_bug.cgi?id=6174 , https://bugzilla.proxmox.com/show_bug.cgi?id=7200
No, I have no solution... :-(
I want to push the backups on my PBS to a S3-storage (Wasabi). I created a datastore on my PBS which works as a cache. The sync-job fills the cache but no data is being send to the S3-storage. I did follow the instructions on the Wasabi site but...
After a change of the root pw of all clusternodes, metrics are no longer shown or shown erraticly on nodes summary page.
All nodes are on 9.1.19 and have been rebootet afer password change. login is possible via ssh and webpage.
I am somewhat...
note that Debian is currently preparing the changes for their first shim update signed with both old and new microsoft keys, and that includes checking which keys are currently enrolled and refusing the update if there is no overlap. that means...
Hey!
To your first point: the new feature uses the -cpu help output as a base and populates the per-node support field with the flags that the host CPUs actually advertise [0]. Those are retrieved by spawning a temporary VM with the CPU type...
As I understand it, you need to purchase three 1-socket subscriptions as each host uses a different key. You cannot share a 2-socket subscription over two hosts. Contact the Proxmox shop with purchase questions to be sure.
7.0 is optin and you can still boot on previous kernel in grub. And only availaible in non subscription repo. So, instead complaining, please report your nic model. Is it a pbs vm on proxmox ve ? Or on vmware ?
7.0 is a test kernel,not an enterprise kernel atm, so if you are okay with breakages you use this kernel. If not, you usually pay for enterprise subscription.
Why would you be angry on a company giving you a test repo?
See: https://forum.proxmox.com/threads/proxmox-tries-to-import-zfs-pool-belonging-to-truenas-vm.128758/
TL;DR: If you don't use ZFS on the Proxmox host you can systemctl disable --now zfs-import-scan.service.
Bzgl. Roadmap siehe auch meinen Post zu einer ähnlichen Frage im Englischen Forum:
https://forum.proxmox.com/threads/kernel-6-14-end-of-support.183689/#post-853599
Kurzum: Wir planen das wieder genauer zu evaluieren, da hat sich ja doch einiges...
You should still upgrade to PVE8 and PVE9 afterwards since PVE7 won't get any security patches anymore. And somewhere in PVE8 or 9 the network-pinning-tool was introduced to mitigate the issues with changing nic names
Hello All,
I need some help on how to do it right.
I have two node PVE cluster where Proxmox root is installed on separate ssd with ex4 lvm and have diferent zpools for other disks:
zpool-nvme
zpool-nvme\local-nvme - this i datacenter storage...
Hi Patrick,
Because new and old machines are same numbers you will have resources to temporarily run all guests only using new machines, so my safe and boring approach would be:
build new 3 node cluster connected to switches
setup up and test...