Thanks.
It worked now. I debugged by option -d99 -F and found issue with multicast.
Thanks
On Thu, Jul 18, 2013 at 9:49 AM, Digimer li...@alteeve.ca wrote:
On 18/07/13 12:40, Vishesh kumar wrote:
On Thu, Jul 18, 2013 at 8:51 PM, Digimer li...@alteeve.ca
mailto:li...@alteeve.ca wrote:
Hello
can you tell us how you resolved the problem, maybe it can be util for
others people
Thanks
2013/7/19 Vishesh kumar linuxtovish...@gmail.com
Thanks.
It worked now. I debugged by option -d99 -F and found issue with multicast.
Thanks
On Thu, Jul 18, 2013 at 9:49 AM, Digimer
Sure. I edited fence_virt.conf file and set interface=virbr0. Conf file
that worked for me is as below
backends {
libvirt {
uri = qemu:///system;
}
}
listeners {
multicast {
interface=virbr0;
port = 1229;
family = ipv4;
address = 225.0.0.12;
Hi All,
I am trying to implement fence_xvm using backend libvirt. Everything is
setup fine and fence_virt.conf have following configuration
++
backends {
libvirt {
uri = qemu:///system;
}
}
listeners {
multicast {
port = 1229;
Thanks for reply,
I have to check value of /sys/class/net/virbr0/bridge/multicast_querier for
centos6.4. Do this value only belong to bridged interface?
Thanks
On Thu, Jul 18, 2013 at 7:27 PM, Digimer li...@alteeve.ca wrote:
On 18/07/13 07:54, Vishesh kumar wrote:
Hi All,
I am trying to
If your bridge is 'virbr0', then yes. If you use traditional bridging,
probably not. Do you see the VMs from the how when you run 'fence_xvm -o
list'?
On 18/07/13 10:17, Vishesh kumar wrote:
Thanks for reply,
I have to check value of /sys/class/net/virbr0/bridge/multicast_querier
for
On Thu, Jul 18, 2013 at 8:51 PM, Digimer li...@alteeve.ca wrote:
. Do you see the VMs from the how when you run 'fence_xvm -o list'?
Thanks for reply.
'fence_xvm -o list' command resulting in timeout.
Thanks
--
http://linuxmantra.com
--
Linux-cluster mailing list
Linux-cluster@redhat.com
