XCP host rebooted: VM's wont start anymore :-(
-
For some reason my xcp host server rebooted and now I cannot access some VM's anymore.
When trying to restart a vm from cli with 'xe vm-start uuid=<vm uuid> it returns this:
"There are no suitable hosts to start this VM on.
The following table provides per-host reasons for why the VM could not be started:xcp : Cannot start here [VM requires access to SR: d58928fe-4a00-3fb0-36c3-8437e3417296 (Local storage)]
xcp-ng-01: Cannot start here [Host down]
"
How can I get it working again or even manually extract the VHD file for a certain VM to another host for conversion/migration ? -
It's hard to assist without knowing more. It's one host only? (not in a pool with others?). Only local storage?
-
@prensel Oh and even reinstalling XOA doesnt work anymore also. bash -c "$(curl -sS https://xoa.io/deploy)" returns without errors but also without creating the XOA
-
@olivierlambert I had two hosts running once but one (xcp-ng-01) was switched off long before this happened. The only host running now is the xcp and didnt gave any (known) issues before,,
-
@prensel said in XCP host rebooted: VM's wont start anymore
:@prensel Oh and even reinstalling XOA doesnt work anymore also. bash -c "$(curl -sS https://xoa.io/deploy)" returns without errors but also without creating the XOA
[15:53 xcp ~]# bash -c "$(curl -sS https://xoa.io/deploy)"
Welcome to the XOA auto-deploy script!
Network settings:
IP address? [dhcp]Your XOA will be started using DHCP
Importing XOA VM...
[15:59 xcp ~]# -
In your host, can you do a
xe host-listplease? -
[16:00 xcp ~]# xe host-list uuid ( RO) : f4d5a20d-e7f3-4e62-8804-e2caa6922a43 name-label ( RW): xcp name-description ( RW): uuid ( RO) : 40974c9e-11c7-4925-a1ea-26496297084e name-label ( RW): xcp-ng-01 name-description ( RW): [16:01 xcp ~]# -
- Please use Markdown syntax over your console copy/paste, I edited your post.
- You need to have the other host online if you want to boot the VM in question.
-
@olivierlambert Ah ok, sorry about the markup.
I cant restart the other host back online because it doesnt exist anymore. -
So why not removing it from the pool then? It's not meant at all to run with a "ghost" machine in a pool.
-
@olivierlambert I just did remove the host but when trying to restart the VM it stiil complains about the SR missing. How can I change this setting for this VM ?
-
Is this SR available?
-
@olivierlambert [16:41 xcp ~]
# xe host-list uuid ( RO) : f4d5a20d-e7f3-4e62-8804-e2caa6922a43 name-label ( RW): xcp name-description ( RW): [16:41 xcp ~]# -
[16:44 xcp ~]# xe vm-start uuid=143f7b5b-b252-346c-5cc0-3027a7dba627 There are no suitable hosts to start this VM on. The following table provides per-host reasons for why the VM could not be started: xcp : Cannot start here [VM requires access to SR: e1fb6d59-93c5-72bf-a018-184dd3ea3643 (Local storage)] There were no servers available to complete the specified operation. [16:44 xcp ~]# xe sr-list uuid ( RO) : e1fb6d59-93c5-72bf-a018-184dd3ea3643 name-label ( RW): Local storage name-description ( RW): host ( RO): xcp type ( RO): ext content-type ( RO): user uuid ( RO) : d58928fe-4a00-3fb0-36c3-8437e3417296 name-label ( RW): Local storage name-description ( RW): host ( RO): <not in database> type ( RO): ext content-type ( RO): user -
[16:47 xcp ~]# xe diagnostic-vm-status uuid=143f7b5b-b252-346c-5cc0-3027a7dba627 uuid ( RO) : 143f7b5b-b252-346c-5cc0-3027a7dba627 name-label ( RW): testserver power-state ( RO): halted possible-hosts ( RO): Checking to see whether disks are attachable uuid ( RO) : dd90f85b-755b-9227-aba7-8583e4b8544f vdi-uuid ( RO): <not in database> empty ( RO): true device ( RO): xvdd userdevice ( RW): 3 mode ( RW): RO type ( RW): CD attachable ( RO): true storage-lock ( RO): false uuid ( RO) : 23a51757-9fec-ab0b-a2d4-2790c8a4a63a vdi-uuid ( RO): 06f7760e-157f-4a18-83fe-ba48db06a5ef empty ( RO): false device ( RO): xvda userdevice ( RW): 0 mode ( RW): RW type ( RW): Disk attachable ( RO): true storage-lock ( RO): false Checking to see whether VM can boot on each host xcp : Cannot start here [VM requires access to SR: e1fb6d59-93c5-72bf-a018-184dd3ea3643 (Local storage)] VM is not agile because: VM requires access to non-shared SR: e1fb6d59-93c5-72bf-a018-184dd3ea3643 (Local storage). SR must both be marked as shared and a properly configured PBD must be plugged-in on every host -
So you want to start a VM that has a disk on a host which you removed.
-
@olivierlambert
I can see the vhd file on the local disk of this host and it has always been there afaik. The other host wasnt used for this VM. And the VM was running fine without the other host being present for several months. So I assume the disk on this host ? -
Well, you can display the VM disk list with a
xe vm-disk-list uuid=<VM UUID>.Then you can find info on those disks with, for each, a
xe vdi-param-list uuid=<VDI UUID>.Then, you'll see on which SR are each disks, and you'll understand why the VM can't boot.
-
I'm trying to understand how it is possible that this vm has been running for a few months without the other host being present ? Where would have the vhd file been stored ?
I have a copy of the vhd file here, can I create a new vm with that ? -
[17:22 xcp ~]# xe vdi-param-list uuid=06f7760e-157f-4a18-83fe-ba48db06a5ef uuid ( RO) : 06f7760e-157f-4a18-83fe-ba48db06a5ef name-label ( RW): mailserver name-description ( RW): Created by XO is-a-snapshot ( RO): false snapshot-of ( RO): <not in database> snapshots ( RO): snapshot-time ( RO): 19700101T00:00:00Z allowed-operations (SRO): generate_config; update; forget; destroy; snapshot; copy; clone current-operations (SRO): sr-uuid ( RO): e1fb6d59-93c5-72bf-a018-184dd3ea3643 sr-name-label ( RO): Local storageIt says the sr-uuid is
e1fb6d59-93c5-72bf-a018-184dd3ea3643, this my local storage SR of the current host ??
