Cannot Start VM - Exit Code 255

[CCUK]

Hi

I'm getting an error trying to start a new VM. There are only two VMs on the Proxmox server and one of them is running fine. However, when I go to start the new one, I'm getting the following error:

Error: command 'ha-manager set vm:101 --state started' failed: exit code 255

It's a dedicated server running Proxmox VE 5.1 with ZFS.

2x480 GB SSD in a ZFS Mirror for the ZIL and L2ARC
2X2 TB HDD in a ZFS Mirror
64 GB Ram
Xeon 4 Core (8T)

The VM that won't start is configured with 1 GB Ram and 1 vcore so there's plenty of resource avaialbe.

I'm fairly new to Proxmox. Suggestions on where to look first?

Thanks

 

[CCUK]

In case it helps someone in the future, I managed to get around this issue by clicking on Datastore, HA. On the right hand panel under Resources, my VM was listed. I clicked it and then Remove. After that I was able to start the VM.

Not sure why it ended up in that state though..

 

[aris]

Thanks for the solution
I guess that happened because I do not have enough RAM

 

[midy.dk]

In case it helps someone in the future, I managed to get around this issue by clicking on Datastore, HA. On the right hand panel under Resources, my VM was listed. I clicked it and then Remove. After that I was able to start the VM.

Not sure why it ended up in that state though..

I know that this is old, but I registered just to say THANK YOU! for this!

 

[sda]

In case it helps someone in the future, I managed to get around this issue by clicking on Datastore, HA. On the right hand panel under Resources, my VM was listed. I clicked it and then Remove. After that I was able to start the VM.

Not sure why it ended up in that state though..

THANK YOU!

 

[seithan]

thanx aswell!

 

[Polisenno]

thanks! I remove VM and after I re-add it. All works fine.

 

[dunckhan]

In case it helps someone in the future, I managed to get around this issue by clicking on Datastore, HA. On the right hand panel under Resources, my VM was listed. I clicked it and then Remove. After that I was able to start the VM.

Not sure why it ended up in that state though..

You are the MVP!

 

[arow]

In case it helps someone in the future, I managed to get around this issue by clicking on Datastore, HA. On the right hand panel under Resources, my VM was listed. I clicked it and then Remove. After that I was able to start the VM.

Not sure why it ended up in that state though..

thkz.

 

[JoaquinR]

In case it helps someone in the future, I managed to get around this issue by clicking on Datastore, HA. On the right hand panel under Resources, my VM was listed. I clicked it and then Remove. After that I was able to start the VM.

Not sure why it ended up in that state though..

Thank you so much!!

 

[PVTD]

Logged in just for the thanks!

 

[TigerGr]

Datastore, HA. On the right hand panel under Resources, my VM was listed. I clicked it and then Remove.

Hi. Not need Remove there. Just Edit VM and there state to Disable first. After - Started. It cleanup the state error.
Thank you about the way by TS.

 

[wiredclark]

In case it helps someone in the future, I managed to get around this issue by clicking on Datastore, HA. On the right hand panel under Resources, my VM was listed. I clicked it and then Remove. After that I was able to start the VM.

Not sure why it ended up in that state though..

Thank you! Problem solved

 

[deivylara]

Thank you! Problem solved

 

[sixmasrl]

Thanks !

 

[knam273]

THanks

 

[DrViliam]

I had the same error on one of my VMs, which could not start. The issue was that I removed the NFS share from Proxmox that held the ISO images, and one of the ISO images was attached to the VM.

 

[merlin87]

In case it helps someone in the future, I managed to get around this issue by clicking on Datastore, HA. On the right hand panel under Resources, my VM was listed. I clicked it and then Remove. After that I was able to start the VM.

Not sure why it ended up in that state though..

In the current version (8.2.8) and depending on your situation you can also change the requested state in the HA Resources group for that VM to disabled to clear the HA error. Then change the requested state back to started etc...