Hi all, I hit an issue a little while ago where live-migrating a VM (on the same management network normally used for corosync and a few other monitoring tasks) ate up all the bandwidth, causing corosync to declare a failure and triggering a fence.
I've dealt with this, in part, by adding redundant ring support on a different network. However, I'd like to also limit the migration bandwidth so that I don't need to fail over the ring in the first place. Is it reasonable/feasible to add 'virsh migrate-setspeed' support to the vm.sh RA? Something like; 'setspeed="75MiB"'? -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? _______________________________________________ Users mailing list: [email protected] http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
