dakralex's latest activity
-
dakralex replied to the thread Cannot migrate VM, because HA resource vm is not allowed.Sorry for the late reply, missed this thread in the new posts section. This was already stated some of the other answers, but this is the expected behavior: HA resources are by default configured with "failback" enabled. Failback in that sense... -
dakralex replied to the thread After PVE upgrade to 9.2.5 I cannot more migrate VM.Hi! If I understand your description correctly, this is expected behavior. As HA resources are "failback" by default and the HA resource is in a non-strict node affinity rule, the HA Manager does not allow the migration. This is because the HA...
-
dakralex reacted to j.theisen's post in the thread Powering down a Proxmox 9.2 cluster: how-to needed with
Like.
Hi @engineer5 thank you for posting on the forum! So with the new HA disarm feature you can also chose to ignore the state of the VMs instead of freezing everything. This will still let you properly power down all the VMs. After the... -
dakralex replied to the thread Questions about the dynamic CRS.Hi, sorry for the late reply! At least for two rooms this is already possible with non-strict node affinity rules as these will fallback to the other available cluster nodes if none of the specified nodes are available anymore. However, an HA...
-
dakralex reacted to aaron's post in the thread HA fencing with softdog vs IPMI watchdog — which one is actually used when both are configured? with Like.
I recommend to stick with the soft watchdog. It works well and you avoid any issues due to questionable quality of OOBM hardware and software ;)
-
dakralex replied to the thread pve-ha-crm breaking our cluster... again.The SIGSEGV is a very different cause to end a process here, so that seems quite unrelated to the previous SIGABRT signals. Could you specify the hardware these cluster nodes are running on? Does a longer-running memtest or a stresstest with...
-
dakralex replied to the thread pve-ha-crm breaking our cluster... again.Unfortunately, we don't have any way to reproduce this on our end yet. One way to be able to have some more information about this would be to look at the process' coredump as a SIGABRT will cause this. See if there is any coredump related to...
-
dakralex replied to the thread disarm-ha and arm-ha commands.The safest procedure to disarm the HA stack before these disarm-ha/arm-ha commands were introduced is to stop the pve-ha-lrm service on each node individually, and after these are all confirmed to be 'restart mode' and all HA resources in...
-
dakralex replied to the thread pve-ha-crm breaking our cluster... again.I don't think that pvestatd is related to this issue, because neither pve-ha-crm nor pve-ha-lrm directly depend on pvestatd. I haven't found any clues why pve-ha-lrm in particular is killed with SIGABRT... How was the HP modules blacklisted? Was...
-
dakralex replied to the thread LCX not starting after upgrading PVe from 9.1.x to 9.2.2 - Mount fails.Have you started the affected container during the time of this log? You can use journalctl --since '2026-06-12 09:38:00' --until '...' to capture the output between some time span (I filled in the --since with the rough start time of the LXC...
-
We are excited to announce the release of Proxmox Mail Gateway 9.1! This release is based on Debian 13.5 "Trixie" and ships the Linux kernel 7.0 as the new stable default. It includes the latest versions of ZFS 2.4, PostgreSQL 17, SpamAssassin...
-
dakralex replied to the thread pve-ha-crm breaking our cluster... again.Does the pve-ha-lrm service acquire its lock on pve1 and pve3 correctly?
-
dakralex replied to the thread pve-ha-crm breaking our cluster... again.Thanks, could you also provide the kernel syslog for the boot before the node rebooted itself?
-
dakralex replied to the thread pve-ha-crm breaking our cluster... again.Hi! Does this happen on a specific cluster node or all cluster nodes? What kind of watchdog is used on the node(s) where this happens? Are there any kernel parameters set? Does any other software on the cluster nodes compete for the...
-
dakralex reacted to t.lamprecht's post in the thread Proxmox Virtual Environment 9.2 available! with Like.
Even then, AMD <-> Intel live migrations can break due to too many subtle differences and vendor-specific optimizations to guarantee that this could work independent of the used vCPU type; some types (like host) will make breakage much more...
-
Look at Datacenter --> HA --> Affinity Rules --> HA Node Affinity Rules. Read about the "Strict" flag shown there. Probably you can create two rules, one with the AMD nodes and one with the Intel nodes. Select the VMs to be "in" the...
-
dakralex replied to the thread Questions about the dynamic CRS.No worries, and the manual can always be improved though I didn't put in the technical explanation from above as it felt too specific. If it's useful there as well, I can certainly find a way to put it there without being too distracting from the...
-
dakralex replied to the thread Questions about the dynamic CRS.Hi! In more detail, each node's current cpu and memory usage is normalized with its own capacity (i.e. cpu_load = current_cpu / max_cpu and memory_load = current_memory / max_memory), where the node's current load is then a equal-weighted...
-
dakralex replied to the thread Conntrack not working when VM has HA turned on.Hi! Yes, this is a known issue and is currently tracked with this Bugzilla entry [0]. [0] https://bugzilla.proxmox.com/show_bug.cgi?id=7053
-
dakralex replied to the thread pve‑ha‑lrm segfault on a single HA node.Thanks for the infos! It's a bit unfortunate that the log doesn't have any entries before the error to know on what tasks the LRM was currently working on. Can I assume that the node is the ballpark of ~33+ nodes according to the names? How...