Newly created Windows VM stuck in Prolog

I’m trying to create a Windows VM using this guide: OpenNebula - How to Build a Windows Image - YouTube, but once I startup the VM in is stuck in Prolog:
Tue Jun 1 12:05:44 2021 [Z0][VM][I]: New state is ACTIVE
Tue Jun 1 12:05:44 2021 [Z0][VM][I]: New LCM state is PROLOG

I have been waiting for 45 miutes and nothing has changes. Does anyone know what causes this and how to fix?

Thanks in advance

Same problem with Ubuntu VM’s

Most probably there is an issue with the resource allocation like CPUs, MEM, datastopre constrains, etc and OpenNebula could not find a matching host where to start the VM. You should check /var/log/one/sched.log for hints about the reason. Also, check the VM Placement tab - in recent OpenNebula versions the error line from sched.log is registered there too.

Placement tab says: Cannot dispatch VM to any Host. Possible reasons: Not enough capacity in Host or System DS, dispatch limit reached, or limit of free leases reached.

Any idea what it means?

Hello @atodorov_storpool and @bribo, note that once the VM switch to PROLOG state, it means that the VM has already been scheduled and the files (i.e VM disks, contexts, …) are being copied to the destination host. So probably there’s a problem while this copy is performed.

It would be useful to know which kind of storage are you using @bribo.

NOTE: if you’re using ssh datastores, a common mistake is that the frontend node is not able to properly reach the hypervisor via ssh. You can check this by running ssh <one-hostname> command as oneadmin user in your frontend node, and it should works without any human intervention (usually the problem is related with the host key verification question that is prompted the first time you connect to a host).