Recent content by jsterr

According to the docs: "If the NUMA option is used, it is recommended to set the number of sockets tothe number of nodes of the host system." Have you tried that and checked how it changes your situation/problem? https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_numa I cant help here but...

Fix is up and worked well on my side: https://forum.proxmox.com/threads/ceph-cves-–-keyring-rotation-strongly-advised-probably-required-in-the-future.185863/#post-867260

Hello Thomas! @t.lamprecht After applying the updates in the script its green again, had to use a couple of commands though: root@training3:~# /usr/share/pve-manager/migrations/pve-cephx-rotate-service-keys root@training3:~# /usr/share/pve-manager/migrations/pve-cephx-rotate-service-keys...

how did it help you exactly? ;-) I personally would like to make some testing about: * testing with 32 PGs vs 512 PGs (min/max) and how it affects performance * testing with erasure coded pools (fastec/non-fast-ec) * testing with krbd/non-krbd

Yeah the container has failback disabled, this seems to be the reason why the container can be moved to a different host, even though the other host has a lower priority.

Hi @dakralex is this a known bug? If not I would create a new one. (not related to dynamic crs but we had talked about other ha improvements here in the last posts) Bug: VMs cant be migrated to nodes with lower priority if priority is set in a HA Node Affinity Rule (positive) without...

20.2.4-pve2 released - seems like I need to manually remove the self-applied fix, as the dashboard still shows the errors.

for reference. I also used the workaround by editing the file.

Isnt that what "Hibernate" does ;-) ?

Hallo Daniel! Done https://bugzilla.proxmox.com/show_bug.cgi?id=7893 https://bugzilla.proxmox.com/show_bug.cgi?id=6593 (this ones already existing but also useful) https://bugzilla.proxmox.com/show_bug.cgi?id=6960 (already existed, commented on this one)...

Hello Kefu Chai (does he have a account here @aaron ?) Nice addition of having a bulk-restart feature in ceph when using 9.2.5 :-) It worked really well on mons, mgr, osds and mds. I also used it in a test-setup for trying a ceph 19 to 20 upgrade -> which could help reducing the guide...

Hi Daniel! Some cases that do not work or might be cool adding them: Example 1: A resource affinity rule with “Keep Separate” for VM1 and VM2, combined with an HA node affinity rule (without “Strict”) on node1 and node2 (checked), but not checked for node3. VM2 cannot start if node2 fails...

Full meshed with sdn fabric (openfabric) is the way to go. See the 9.0 Release Video for a quick introduction.

Hello Community, im currently in the progress of trying out nvme over tcp in Proxmox VE and wanted to ask, if somebody has ressources for: * Basic Setup of NVMe-Over-TCP in Proxmox VE? * Information about using basic nvme-cli vs nvme-stas -> benefits? * Measuring performance of nvme-over-tcp...

The customer also asked the proxmox enterprise support and proxmox also thinks that stalled i/o caused the issue. The solution could be using a fleecing storage. Thanks for your (also correct :) ) replies.