This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-API] RE: XCP / xenAPI shows no vms but vm is still running

To: 'Chonduy Nguyen' <chonduy9@xxxxxxxxx>, "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-API] RE: XCP / xenAPI shows no vms but vm is still running
From: Dave Scott <Dave.Scott@xxxxxxxxxxxxx>
Date: Fri, 5 Mar 2010 12:09:47 +0000
Accept-language: en-US
Acceptlanguage: en-US
Delivery-date: Fri, 05 Mar 2010 04:12:46 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <352893.60058.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <352893.60058.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acq8AbzsBsZ2k3cSR4+CVCSv1VWHFAAWo5UA
Thread-topic: XCP / xenAPI shows no vms but vm is still running



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.





From: Chonduy Nguyen [mailto:chonduy9@xxxxxxxxx]
Sent: 05 March 2010 01:18
To: xen-api@xxxxxxxxxxxxxxxxxxx
Cc: Dave Scott; Stephen Spector
Subject: XCP / xenAPI shows no vms but vm is still running



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

[root@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!)




xen-api mailing list