@olivierlambert said:
Start the VM with xe vm-start uuid=<VM UUID> and see the error message there.
I believe I found the problem:
[17:19 xcp-server1 ~]# xe vm-start uuid=4ba7c16c-f850-6001-830b-bf0f51e52a40
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-server1 : Cannot start here [VM requires access to SR: da59d7a1-b08f-dd81-1258-65a380bd77d8 (Iso)]
There were no servers available to complete the specified operation.
I made changes to my Iso storage folder path:
[image: 1782615502954-screenshot_20260627_160512.png]
from:
[image: 1782615535998-screenshot_20260626_220502.png]
to:
[image: 1782615681155-screenshot_20260627_210002.png]
and when I tried to start my NTP VM, because I wanted to reinstall the OS is when I get the error message:
[image: 1782616205507-screenshot_20260627_210723.png]
Can you put the correct error message from the cli here instead of this generic one, because it causes far to much trouble shooting time? I knew directly where to go after seeing the cli message.
Also, I can start the NTP VM without the .iso as normal. However, I did find out why I lost control of the OSs as stated above. Since the latest updates, the keyboard does not work properly. I will come back with more details later.
For now, my question is, is there a way to modify/edit the path to my Iso Storage without removing and redefining it, like you can with Cockpit, if not is/can this be a future feature added?:
[image: 1782617180903-screenshot_20260627_212426.png]
