Sure. I edited fence_virt.conf file and set interface=virbr0. Conf file that worked for me is as below
Thanksbackends { libvirt { uri = "qemu:///system"; } } listeners { multicast {
interface=virbr0;
port = "1229"; family = "ipv4"; address = "225.0.0.12"; key_file = "/etc/cluster/fence_xvm.key"; } } fence_virtd { module_path = "/usr/lib64/fence-virt"; backend = "libvirt"; listener = "multicast"; }
On Fri, Jul 19, 2013 at 7:23 AM, emmanuel segura <emi2fast@xxxxxxxxx> wrote:
ThanksHellocan you tell us how you resolved the problem, maybe it can be util for others people
2013/7/19 Vishesh kumar <linuxtovishesh@xxxxxxxxx>
--Thanks.It worked now. I debugged by option -d99 -F and found issue with multicast.
ThanksOn Thu, Jul 18, 2013 at 9:49 AM, Digimer <lists@xxxxxxxxxx> wrote:
On 18/07/13 12:40, Vishesh kumar wrote:
<mailto:lists@xxxxxxxxxx>> 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
So the deamon is not running, it would seem. Try running 'fence_virtd -d99 -F' (show debug and do not fork into the background).
--
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?
--
http://linuxmantra.com
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
--
esta es mi vida e me la vivo hasta que dios quiera
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
--
http://linuxmantra.com
-- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster