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

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

  • To: xen-api@xxxxxxxxxxxxxxxxxxx
  • From: Chonduy Nguyen <chonduy9@xxxxxxxxx>
  • Date: Thu, 4 Mar 2010 17:18:15 -0800 (PST)
  • Cc: Dave Scott <Dave.Scott@xxxxxxxxxxxxx>
  • Delivery-date: Thu, 04 Mar 2010 17:18:16 -0800
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type; b=loEq/vxX+Gt7fyVtWovWU5ESYHEpVm+SSN/hUX0IVI7vQtCOKMzI+9u1ELflux5k+EQ2d7z7iFR/jpr4sHfE0gnNB0ee54954dLZ6T6y8g50tD7xu/XeOlA2g9Mk5ZVg2cD8t0BxyBn72OcIPaTxmwfys5WXJ52HcA8JiNO7P/A=;
  • List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>


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



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.