Search results

Guten Abend zusammen, da ich ebenfalls auf diese Thematik aufmerksam gemacht wurde ein paar Anmerkungen. In den bisher beigefügten Übersichten ergibt sich an keiner Stelle der Aufschluss, dass diese Prozesse von PegaProx ein potentielles Problem darstellen würden, noch überhaupt dort mit...

As requested, a `list-only` parameter for added for pipeline runs (avoiding invoking other tools like grep, awk, …). So, you directly get simply the CPU type returned on stdout which can be set for the guest. This is part of release 1.2

Vielen Dank für das tolle Feedback!

Thank you, happy to hear!

Happy new year! Version 1.1.0 released. Version 1.1.0 now also supports standalone PVE nodes. While this is a corner case and host type might mostly fit, this might still be interesting for corner cases like Windows systems where CPU mitigations kick in and slow down the performance.

Ich habe die Tage mal dazu das Tool “ProxCLMC” (Prox CPU Live Migration Checker) geschrieben, da dies immer mal wieder aufkam. Wie @Falk R. schon schrieb, erfolgt dies auf VM Basis. Die Idee ist, dies in eine Pipeline einzubinden, um das aktuelle Level des CPU Typs über alle Nodes im Cluster...

Hey folks, I got asked to cross-post this to the Proxmox forums. You might already know me from the ProxLB project for Proxmox, BoxyBSD or some of the new Ansible modules for Proxmox and I just published a new open-source tool: ProxCLMC (Prox CPU Live Migration Checker). Live migration is one...

Hey @ksl28, instead of: simply use: This probably returns you your expected remotes, including a list of the nodes themselves and their types (pre, pbs). The output looks like: Hope it helps! Afterwards, you can use this data as a foundation to query resources directly via /pve or /pbs...

Not yet, but maybe the ProxLB project might be a look worth in the meantime: https://github.com/gyptazy/ProxLB This also features the support of affinity and anti-affinity rules, ignore options on guest and nodes level and several other features.

Both ways. Also LXC or Docker is possible. It simply uses the Proxmox API - so in the end, it simply requires a network connectivity to any Proxmox node within the cluster. It's up to you and what you prefer. You can find all the details within the docs...

Thank you very much, really appreciate this! Happy to hear that it provides a value to the Proxmox community and its users to boost opensource products on the market. Regarding your request, just change https://github.com/gyptazy/ProxLB/blob/main/proxlb.conf#L8 to "cpu" and restart the service...

So, unfortunately not directly built-in but there’s an opensource project called ProxLB: https://github.com/gyptazy/ProxLB This integrates auto balancing by cpu, memory or local disk for VMs and/or CTs. It also provides support for grouping (affinity/anti-affinity) and more. Hope it helps…

Freut mich zu hören :) Viel Spaß! Aktuell befinden sich (in der Reihenfolge) folgendes Features in der Pipeline: * Storage Balancing * API * Rolling Updates * DPM

Indeed, it is - and also now there is with ProxLB! I had the same issues and wrote an opensource to have this in place: https://github.com/gyptazy/ProxLB

Der Thread ist zwar etwas älter, aber ich wollte eine Art von Loadbalancing von Containern und VMs ebenfalls. Das sollte allerdings ausschließlich über die API laufen, damit das vorhandene Authentication und Authorization System nicht unterwandert wird. Rausgekomnen ist dabei der ProxLB. Bei...

Introduction ProxLB (PLB) is an advanced tool designed to enhance the efficiency and performance of Proxmox clusters by optimizing the distribution of virtual machines (VMs) or Containers (CTs) across the cluster nodes by using the Proxmox API. ProxLB meticulously gathers and analyzes a...

Ok, I finally could make it reproducible and track it down. In my case it’s related to a different MTU size on IPV6 (also dual stack) links to VMs which are using the e1000 network driver and firewalling is active in general (even only on host node). I’m trying to find more details on a...

After only one of my multiple host nodes crashed again and again I could isolate the issue which caused it. Only this this node is running a slightly different and special configuration regarding IPv6 where multiple IPv6 networks are tunnelled by different Tunnelbrokers with different MTU sizes...

This thread seems to be pretty old, but I ran into a similar issue on a host node, where I use IPv6 subnets from tunnel broker which are directly routed. The VMs have IPv6 only setup. When having a firewall enabled on a VM it ran some hours later into: As well as: PVE: 8.1.5 Kernel...