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...
There is some documentation available for Corosync network setup: https://pve.proxmox.com/wiki/Cluster_Manager#pvecm_cluster_network
Using bonds is not advised, shared links with other traffic types are not advised too.
It’s a disk image backup so AFAIK no. Microsoft has a script and stored procedure to trigger a back up of all databases, even in Express; I can dig it up next week if you want.