Re: [pve-devel] 3.4: Changes in the way quorum is formed?

2015-02-21 Thread Michael Rasmussen
On Sat, 21 Feb 2015 08:14:12 +0100 (CET) Dietmar Maurer diet...@proxmox.com wrote: 22 patches? We could also wait for Redhat;-) Redhat seems eager to put the patches in production, even so eager that they are willing to cross-cut the normal sunrise period in the linux kernel community. To me

Re: [pve-devel] 3.4: Changes in the way quorum is formed?

2015-02-20 Thread Michael Rasmussen
On Fri, 20 Feb 2015 16:21:24 -0500 Eric Blevins ericlb...@gmail.com wrote: I can confirm this, IPOIB multicast seems to only work intermittently with pve-kernel-2.6.32-37-pve According to this thread RHEL 6.6 kernel has introduced a regression into IPoIB which brakes multicast. The thread

Re: [pve-devel] 3.4: Changes in the way quorum is formed?

2015-02-20 Thread Eric Blevins
On Fri, 20 Feb 2015 00:29:36 +0100 Michael Rasmussen m...@datanom.net wrote: I am giving up for now and have reverted back to pve-kernel-2.6.32-34-pve. Doing the Same I forgot to mention that my conclusion is that the infiniband drivers delivered with pve-kernel-2.6.32-37-pve is broken.

Re: [pve-devel] 3.4: Changes in the way quorum is formed?

2015-02-20 Thread Michael Rasmussen
On Fri, 20 Feb 2015 23:35:09 +0100 Michael Rasmussen m...@datanom.net wrote: According to this thread RHEL 6.6 kernel has introduced a regression into IPoIB which brakes multicast. The thread referrers to 3 patches which should solve the issue.

Re: [pve-devel] 3.4: Changes in the way quorum is formed?

2015-02-20 Thread Dietmar Maurer
According to this thread RHEL 6.6 kernel has introduced a regression into IPoIB which brakes multicast. The thread referrers to 3 patches which should solve the issue. https://www.mail-archive.com/linux-rdma@vger.kernel.org/msg22511.html The complete patchset can be found here:

[pve-devel] 3.4: Changes in the way quorum is formed?

2015-02-19 Thread Michael Rasmussen
Hi all, As a follow up to my post to the forum (http://forum.proxmox.com/threads/21083-Proxmox-VE-3-4-released!?p=107495#post107495) I was wondering if anything has changed in 3.4 in the way quorum is formed? -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael at rasmussen

Re: [pve-devel] 3.4: Changes in the way quorum is formed?

2015-02-19 Thread Michael Rasmussen
On Thu, 19 Feb 2015 21:18:23 +0100 Michael Rasmussen m...@datanom.net wrote: Hi all, As a follow up to my post to the forum (http://forum.proxmox.com/threads/21083-Proxmox-VE-3-4-released!?p=107495#post107495) I was wondering if anything has changed in 3.4 in the way quorum is formed? It

Re: [pve-devel] 3.4: Changes in the way quorum is formed?

2015-02-19 Thread Dietmar Maurer
I am giving up for now and have reverted back to pve-kernel-2.6.32-34-pve. I forgot to mention that my conclusion is that the infiniband drivers delivered with pve-kernel-2.6.32-37-pve is broken. I verified the corosync versions, and there was no update recently. So I guess a driver

Re: [pve-devel] 3.4: Changes in the way quorum is formed?

2015-02-19 Thread Michael Rasmussen
On Fri, 20 Feb 2015 00:29:36 +0100 Michael Rasmussen m...@datanom.net wrote: I am giving up for now and have reverted back to pve-kernel-2.6.32-34-pve. I forgot to mention that my conclusion is that the infiniband drivers delivered with pve-kernel-2.6.32-37-pve is broken. -- Hilsen/Regards

Re: [pve-devel] 3.4: Changes in the way quorum is formed?

2015-02-19 Thread Michael Rasmussen
On Thu, 19 Feb 2015 23:55:27 +0100 Michael Rasmussen m...@datanom.net wrote: Now it gets really strange. If I configure cluster to use unicast then suddenly multicast starts to work!!! I am giving up for now and have reverted back to pve-kernel-2.6.32-34-pve. -- Hilsen/Regards Michael

Re: [pve-devel] 3.4: Changes in the way quorum is formed?

2015-02-19 Thread Michael Rasmussen
On Thu, 19 Feb 2015 23:29:17 +0100 Michael Rasmussen m...@datanom.net wrote: It seems this is the case. Multicast over infiniband is broken on pve-kernel-2.6.32-37-pve!! Just to be curtain I added netmtu=2044 to totem in cluster.conf but this did not change anything and was not needed on