On 2008-09-29T11:00:04, "Paul.Thurn" <[EMAIL PROTECTED]> wrote:

> But starting the vm from HA gui doesn't work.

Doesn't work "how"?

BTW:

<clone id="configstorecloneset" notify="true" globally_unique="true">
<clone id="imagestorecloneset" notify="true" globally_unique="true">

globally_unique must be set to false here (this might require a full
restart of the cluster). I'm surprised this works at all.

For the Xen RA:

       <primitive id="s10test" class="ocf" type="Xen" provider="heartbeat">
         <meta_attributes id="s10test_meta_attrs">
           <attributes>
             <nvpair id="s10test_metaattr_target_role" name="target_role" 
value="stopped"/>
           </attributes>
         </meta_attributes>
         <instance_attributes id="s10test_instance_attrs">
           <attributes>
             <nvpair id="4279698e-95c9-4d94-8d2f-73345566be0c" name="xmfile" 
value="/etc/xen/vm/sles10test.xml"/>
             <nvpair id="d040f12e-bf93-4d58-9fa7-2333763c1865" 
name="allow_migrate" value="1"/>
           </attributes>
         </instance_attributes>
         <operations>
           <op id="81762d05-cdfb-40e6-bd3b-37c5579a4bbd" name="start" 
description="strat" timeout="60" start_delay="0" disabled="false" 
role="Started" interval="10"/>
           <op id="5b13b767-d362-4df1-be1b-69ae4eb95a25" name="stop" 
description="stoopy" timeout="40" start_delay="30" disabled="false" 
role="Started" interval="10"/>
           <op id="9b657f82-5bf0-452b-b82d-e1eeb6e6ed33" name="status" 
description="ststs" interval="10" timeout="30" start_delay="120" 
disabled="false" role="Started"/>
           <op id="4b65aac6-d2be-4e75-a303-1f1a96f68d84" name="meta-data" 
description="meta" interval="5" timeout="5" start_delay="0" disabled="false" 
role="Started"/>
           <op id="07849bbd-6326-4698-a42e-62fa2f928884" name="monitor" 
description="moni" interval="10" timeout="30" start_delay="120" 
disabled="false" role="Started"/>
         </operations>
       </primitive>


allow_migrate should be a meta_attribute.

And there's no point to define a "status" operation here. That needs to
be removed.

The status section indicates that start failed. Read the logs as to
why. But since you don't have rules ordering and collocating the Xen
start after the filesystem, that would be the reason ...


Regards,
    Lars

-- 
Teamlead Kernel, SuSE Labs, Research and Development
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde

_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to