In the proxmox shop FAQ, its mentioned that you will receive a renewal notices 30 days before your subscription ends:
https://shop.proxmox.com/index.php?rp=/knowledgebase/8/Renewal.html
I would suggest to contact Proxmox shop team regarding your...
There's an enhancement request for including PDM in POM, see:
https://bugzilla.proxmox.com/show_bug.cgi?id=7762
Latest update is patch for it available, waiting for review...
The guest-fsfreeze-status command is used to determine if a fsfreeze is still ongoing inside the guest VM. The timeout here show that the guest does not respond to the status requests send by the PVE host, which waits 10 minutes at most for this...
Just my 2 cents, I might be wrong:
My understanding this means pve (i think specifically pvestatd/qmeventd) tries to access the QMP socket of the VM but it couldn't and timeout, this can occurs for many reasons, for example such as another...
There's one bug report on PBS related to nfs and kernel 7:
https://bugzilla.proxmox.com/show_bug.cgi?id=7558
Might worth attempting to force NFS version 4.0 and see if that's help? also if its possible for you to try temporary to use the latest...
Hi !
First of all, thanks to everyone contributing to this forum, I have a home server running Proxmox VE 9.2.11 and this forum has been helpful more than once ! Now, I've had to create an account because I cannot find an exact match for my...
If its cluster nodes, then might be problematic as shown above. Although you can work on separate migrating network/replication then it should be fine as well I think.
As mentioned in the thread above:
"For two IPs in two subnets, you will need a second NIC."
However, if your node is standalone (not part of a cluster), you can easily add two IPs from different subnets on the same bridge using a command like...
No reboot is not required for these packages but for running VMs must be fully Stopped and Started to load the new QEMU version.
In general, I would only reboot host for kernel updates as you mentioned.
There's an enhancement request:
https://bugzilla.proxmox.com/show_bug.cgi?id=6967
Its also discussed in the thread:
https://forum.proxmox.com/threads/pdm-migration-network.174345/post-810600
Yes, your understanding is correct.
If for whatever reason the new subscription didnt get replaced correctly, you can attempt with --force option:
pvesubscription update --force
I am also not sure if LVM-Thin can be safely shared between different nodes?
Currently if the backend storage support thin-provisioning and discard, then (I think) you are more less having the same features as if its "LVMthin over iscsi".
I mean...
https://forum.proxmox.com/threads/pbs-acme-order-kann-nicht-abgeschlossen-werden.176240/post-863521
Does it resolve when automatic updater run now? from above thread 2 reports mentioned it worked without change
I think the upgrade is necessary in any case since PVE7/Debian 11 is EOL.
I found one thread related to Intel E810 NICs, where it was observed it can be related to causing memory leaks...
I'm not aware of an official PVE specific source but if you care, here's some of my opinions about it. This heavilly depends on the storage type.
My experience is with ZFS and LVM-Thin, which are also what I recommend, in that order
I haven't...
Interesting topic, I am not aware of performance impact with keeping snapshot for too long or more snapshots means less performance.
Indeed "snapshots are no backups" is to be taken seriously therefore ensure to always have your scheduled backup...
Is your NICs Broadcom bnxt_en NICs?
I edited my first comment if thats can be tested (Ensure you have access via IPMI/iDRAC and take backup of /etc/network/interfaces so you can easily revert things)