[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[Linux-cluster] VM Service not rebooting.



I have basically followed these instructions on building a xen cluster...
http://www.redhatmagazine.com/2007/08/23/automated-failover-and-recovery-of-
virtualized-guests-in-advanced-platform/#comment-121366

When I issue a "xm destroy <ID>" the vm automatically reboots backup, but
when I reboot or shut down a machine the VM's that were on the shutdown node
never come back up on the existing node.

Any idea why this doesn't work?

Thanks!

My cluster.conf...

<?xml version="1.0"?>

<cluster alias="Xen" config_version="67" name="Xen">

        <fence_daemon clean_start="0" post_fail_delay="0"
post_join_delay="300"/>

        <clusternodes>

                <clusternode name="xen1.smartechcorp.net" nodeid="1"
votes="1">

                        <fence>

                                <method name="1">

                                        <device name="manual"
nodename="xen1.smartechcorp.net"/>

                                </method>

                        </fence>

                </clusternode>

                <clusternode name="xen2.smartechcorp.net" nodeid="2"
votes="1">

                        <fence>

                                <method name="1">

                                        <device name="manual"
nodename="xen2.smartechcorp.net"/>

                                </method>

                        </fence>

                </clusternode>

        </clusternodes>

        <cman expected_votes="1" two_node="1"/>

        <fencedevices>

                <fencedevice agent="fence_manual" name="manual"/>

        </fencedevices>

        <rm>

                <failoverdomains>

                        <failoverdomain name="bias-xen1" nofailback="0"
ordered="0" restricted="0">

                                <failoverdomainnode
name="xen1.smartechcorp.net" priority="1"/>

                        </failoverdomain>

                        <failoverdomain name="bias-xen2" nofailback="0"
ordered="0" restricted="0">

                                <failoverdomainnode
name="xen2.smartechcorp.net" priority="1"/>

                        </failoverdomain>

                        <failoverdomain name="gfs-xen1" nofailback="0"
ordered="0" restricted="1">

                                <failoverdomainnode
name="xen1.smartechcorp.net" priority="1"/>

                        </failoverdomain>

                        <failoverdomain name="gfs-xen2" nofailback="0"
ordered="0" restricted="1">

                                <failoverdomainnode
name="xen2.smartechcorp.net" priority="1"/>

                        </failoverdomain>

                </failoverdomains>

                <resources/>

                <service autostart="1" domain="gfs-xen2" exclusive="0"
name="GFS Mount Xen2" recovery="restart"/>

                <service autostart="1" domain="gfs-xen1" exclusive="0"
name="GFS Mount Xen1" recovery="restart"/>

                <vm autostart="1" domain="bias-xen1" exclusive="0"
migrate="live" name="Windows1" path="/xen/boot" recovery="relocate"/>

                <vm autostart="1" domain="bias-xen2" exclusive="0"
migrate="live" name="Linux1" path="/xen/boot" recovery="relocate"/>

        </rm>

        <quorumd device="/dev/sdb5" interval="1" min_score="1" tko="10"
votes="1">

                <heuristic interval="2" program="ping -c3 -t2 10.10.10.1"
score="1"/>

        </quorumd>

</cluster>

---

Chris Edwards





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]