from last corosync release
https://github.com/corosync/corosync/releases
"A new option (totem.ip_dscp) is available to configure DSCP for traffic
prioritization. Thanks to David Hanisch for this great improvement."
could be interesting for...
Sounds good, thanks for reporting back!
I'd generally recommend a dedicated primary network for corosync, to prevent other traffic from driving up corosync latencies, see [1]. corosync can handle multiple redundant networks itself [2], so...
Understandable. In my view, deploying a product that is effectively unsupported (by anyone) is a bad solution, regardless of budgetary requirements. outages, loss of service, or loss of data are more expensive than upfront spending. Given your...
I don't see any Linux kernel driver that is not part of Linux itself, just hardware vendor / product integration. Most are hardware vendor integration drivers similar to the ones that exist for PVE. If more vendors would support PVE directly, PVE...
I know @bbgeek17 is too humble, but I'm pretty sure you can get the functionality you are after using blockbridge. The state of PVE's support of block level SANs via API has been "not in scope" for a long time, and doesnt look like it will be...
Hi @sys92, welcome to the forum.
If by “native” you mean vendor-specific FC integrations, then no - there are currently no plans in that direction.
If you’re referring to native FC support within Proxmox VE itself, any developments in this area...
Hello rXp,
Could you please clarify if this is a Container in your storage, or within a VM? Is it an [lxc]?
At your convenience, could you please also run the command [pvesm status] and share its output?
Is the Balloon Device checkbox active in the VMs Memory configuration (Advanced section)?
Is the Balloon Service installed and running in the Windows VM?
The Balloon Device is needed to communicate with the VM regarding its memory usage (and...
Hi bru87!
I do not have any comment on the resolution you found, but just wanted to say that I appreciated reading this well laid out post. Thank you for sharing!
Any usb devices hooked up? :oops: Check your hardware, maybe udev has issues removing a device.
Well, looks like a classical issue of NOT HAVING SEPARATED YOUR COROSNYC LINKS. Link saturation (amongst others) may result in loss of quorum and...
Hi @weehooey-bh,
thanks for asking, because this made me look at the documentation again, which I didn't earlier. And it clearly states, that a standard Linux bridge is used in the background of SDN everywhere...
A status update on this:
Two corosync parameters that are especially relevant for larger clusters are the "token timeout" and the "consensus timeout". When a node goes offline, corosync (or rather the totem protocol it implements) will need to...
Just for the record the VM config sizing and changes are related to the PXMCFS https://pve.proxmox.com/wiki/Proxmox_Cluster_File_System_(pmxcfs)
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
Hi @Nathan Stratton and all,
You need clear guidance here: do not do that unless you have a very compelling reason to.
a) Your hardware is discontinued and past the end of service, which significantly increases the likelihood of component...
@aomer786 There have been various posts here about max cluster size, like the one linked above. The concern with corosync is latency not bandwidth. So if enough milliseconds go by the node is considered to not be responding. A NIC can't send...
Right now, the fact that we're working on providing guidance for necessary corosync tweaks for bigger clusters. When that is available, we can update the linked post (to avoid scattering information across multiple posts).
Hi, from a quick look, the "Retransmit" messages may be a symptom of network stability issues (e.g. lost packets, increased latency etc) that are more likely to occur if corosync shares a physical network with other traffic types -- I'd expect...