Search results

I probably can enable it in the Juniper switch, but haven't touched the switch config from when I had it working with standard linux bonding and bridging since I could enable the querier there. I've never messed with the multicast settings in the Juniper side, if anyone has any suggestions on...

I'm having issues where multicast doesn't appear to work when I use openvswitch to configure my bonds and bridges. Initially at boot, everything comes up and the system has quorum, then in the logs you start seeing totem retransmissions on all systems and everything gets out of whack...

There's also this wiki which set up a mac mini proxmox cluster. Quite a few things you have to do to get the mac mini properly bootable: http://www.jaxlug.net/wiki/2014/07/16

You'll find a couple of other forum posts here about the same thing. 3.5 doesn't work, 3.4 does. However, I gave up on gluster as my VMs would report disk i/o errors on reboot of nodes randomly. I think it was due to disabling client-side quorum, but leaving server side quorum enabled. With...

I've actually switched to testing ceph instead of glusterfs, I hit some other issues with glusterfs even after rolling back to 3.4, such as i/o errors reported to a VM when one of the gluster nodes was rebooted even though quorum still existed .. resulting in the VM remounting the root fs as...

It turns out this wasn't actually disk corruption, the kernel panic is due to / not being writable. So the volume went into a read-only state on glusterfs. It turns out, when using replica 2, but with 3 nodes, the loss of just one node when enabling client-side quorum will result in the VM...

Someone appears to be reporting the same here .... not seeing a resolution in the thread: http://supercolony.gluster.org/pipermail/gluster-users/2014-April/039985.html

I think I may be seeing this same issue. I have 3 proxmox nodes, all running glusterfs 3.4.2, with replica2 and quorum-type auto and server-quorum-type server (actually all the options use with 'group virt'). I use 2 bricks on each server to comply with the replica requirements, but ensure 2...

Turns out I had a few issues. First was ... don't install GlusterFS 3.5 from the gluster.org repos, seems there is some sort of incompatibility with Proxmox. Next is, I was still having multicast issues, I fixed the server bridge issue by disabling multicast snooping (by adding this to my...

I've been pulling my hair out with the same issue, I'm also running GlusterFS 3.5. I just starting playing with ProxMox this week, so GlusterFS 3.5 was the natural choice. Was a workaround ever introduced for this?

I think this post is the same issue as mine. http://forum.proxmox.com/threads/18486-qm-start-fails-with-timeout-error-but-vm-is-actually-started

Not seeing anything in there that would help. That said, it appeared I was having multicast issues, which is why rgmanager wasn't running. I fixed those. However, that didn't fix live migration. One other mentionable item, I noticed whenever I start a VM, it gives me an error like: TASK...

We are just starting to evaluate proxmox ve and testing the various features provided. The setup uses 3 Intel-based nodes with GlusterFS. Since we do not have an enterprise subscription (yet) we installed Debian 7.5 + GlusterFS 3.5, then performed the conversion to the Proxmox kernel using the...