Hi Dave,

Since the current XCP didnot provide Fault Tolerant and HA yet, we tried to 
write a simple monitoring where we ping the node and check 
if this node is unreachable - for whatever reason - could be network connection 
down or could be physical hardware etc...

we will disconnect this problem  node  out of XCP network by filter traffic 
from this node to storage network and other nodes -using iptables filtering and 
we want to quickly move Vms to start at other mahines - Therefore,we need to 
use reset-power-state

However, since we keep monitoring this node - the node could be back up again. 
That time we want to find a way to check if VMs running - but XCP
showed that VMs not there - but actually VMs still there.

Can you please suggest a way to find out if VMs running on machine or not ? XCP 
will fail to show this - I am wondering is there anyway we can detect
VMs running on OS?


Please let me know

Thanks

ChonDuy/TNguyen



________________________________
From: Dave Scott <[email protected]>
To: Chonduy Nguyen <[email protected]>; "[email protected]" 
<[email protected]>
Cc: Stephen Spector <[email protected]>
Sent: Fri, March 5, 2010 4:09:47 AM
Subject: RE: XCP / xenAPI shows no vms but vm is still running

  
Hi,
 
You should only use ‘reset-power-state’ on VMs which
have failed e.g. if the host has failed. If the VMs are still running then you
shouldn’t do this – if you start a VM twice then there is a high
chance of disk corruption.
 
Cheers,
Dave
 
From:Chonduy Nguyen
[mailto:[email protected]] 
Sent: 05 March 2010 01:18
To: [email protected]
Cc: Dave Scott; Stephen Spector
Subject: XCP / xenAPI shows no vms but vm is still running
 
Hi

I tried the case when the node - said "P" is unreachable by
interface down - so, we restart Vms of that machine to another machine by
doing reset-power-state first and call vms to start at other machine said
node "A"

However when the problem node"P"  is up again - xenAPI
shows that there is no Vm running on it-   Which is wrong, Vms should be
running.
I tested this by stop the vm on "A"  to start that vm on the
"P" - "P" complains that 

[r...@quindecim ~]# xe vm-start vm=ken-debian-vm-2 on=quindecim
The server failed to handle your request, due to an internal error.  The
given message may give details useful for debugging the problem.
message: Failure("The VDI
57a82bd4-a889-42ff-94d3-479a2618f2ec is already attached in RW mode; it can't
be attached in RO mode!")

After I reboot the node, vm can start.  So, is there any way I can detect
that VMs are currently running on the "P" problem machine?

after the Vms relocated to other machine, info from XenAPI showed that that
machine has no VMs ( which is incorrect!)

Thanks

ChonDuy/Tnguyen


      
_______________________________________________
xen-api mailing list
[email protected]
http://lists.xensource.com/mailman/listinfo/xen-api

Reply via email to