Search results

Both will work for the no-subscription and debian repos without any subscription keys.

that sounds like a sensible thing to do and isn't hard to change. Therefore I send a patch for this: https://lore.proxmox.com/pve-devel/20250507124434.1730046-1-a.lauterer@proxmox.com/T/#u

You will have to look with the ZFS tools when the last successful replication happened by checking what the last snapshot is. Since this is the local-zfs, the pool and sub dataset in which the virtual disks reside is rpool/data. To list all snapshots in the location, run zfs list -t snapshot -r...

IIRC ist das Limit per Default 250 PGs/OSD, für mehr muss man den Wert in der Config (ceph.conf oder MON config DB) entsprechend ändern.

Since the VM replication feature based on ZFS is done within one cluster, and Ceph is a shared storage within one cluster, the direct equivalent is not necessary. In the context of the Datacenter Manager, we do plan to have site-replication and (manual) fail over between different Proxmox VE...

Nur mal so als Idee, ich weiß nicht ob das auch auf Server 2025 zutrifft, aber gibt es unter Windows nicht neue security Features, irgendwas "memory integrity protection"? Das könnte, falls aktiv, auch ganz schön Performance fressen.

Okay, if that is way off then the certificate verification will also not work :) Good to hear that it is solved.

@RocketSam Please contact us in our support portal https://my.proxmox.com so we can troubleshoot the issue for the TLS verification error. Since the current Cert is valid from March 7 to June 5, it will most likely be a proxy or something like it in between the Host and shop.proxmox.com that is...

@patefoniq to add to the answer of @dcsapak, the roadmap has the following: So yes, something that we would like to implement in the future.

Check which networks are used by Corosync (Proxmox VE Cluster communication) (/etc/pve/corosync.conf). Ideally you have more than one with one of them being there only for Corosync alone (physical, 1 Gbit is enough). If you only have one Corosync network and it is having issues, then it is...

not really fully fledged out, but you could install sudo and configure for the dedicated user that it only allowed to run the commands needed to receive the data to the datasets it needs.

Bei den meisten Browsern kommt man mit CTRL+Shift+i in den Inspector, und dann ists nur einen Tab weiter zur "Console". Dort beschwert sich Javascript dann deutlich wenn was nicht passt. Das gibt uns evtl. eine Idee was schief läuft. Aber ansonsten bitte mal den Host auf den neuesten Stand...

Vielleicht auch mal in Javascript Console der Devtools im Browser schauen, ob es Probleme gibt.

With those huge CPUs (physically) it can also sometimes be necessary to do a reseat, as in, taking it out and putting it in again because sometimes not all pins have a good contact.

Thanks, that must have slipped through. In the next version of the docs it will be aligned to avoid confusion https://git.proxmox.com/?p=pve-docs.git;a=commitdiff;h=57cdb882248f08c2099751a5eb2d64669e26a9a2

Since Proxmox VE follows a rolling release model, there is no way to install a specific version. That term is also hard to define, because even if the GUI says you are on 8.2.4, some other packages could be on several possible versions. Either update the other nodes as well, or, for the future...

If you have enough large SSDs and have other use-cases for the small SSDs, then I would use them with the other use-cases. Keep in mind, that the number of OSDs / host is important in smaller clusters. Especially when the number of nodes is equal to the number of replicas (size). In most...

If you have OSDs with very different sizes in the cluster, it gets a bit more complicated. Performance wise, the larger OSDs will see more load as they store more data. What happens if you have many small and a few large OSDs? What happens if a large OSD fails? Can the remaining OSDs/hosts...

^^^^^^^ Das hier ist der primäre Filter, um die Consumersachen wegzuhaben! Der Rest ist dann meistens in Ordnung bis super, je nachdem wie viel man ausgeben will.

So things are likely to be okay. But there could be other factors outside of the packages that interfere here. Can you disable or remove it temporarily? Overall, this is not something I have seen recently to be a general problem. And this is a modified host, which makes troubleshooting a bit...