Custom qcow2 won't boot stuck in queued

[jpeterson]

I created a Ubuntu VM with BIRD and uploaded it as a qcow2 to CML, but for some reason when i add that node to my Lab it gets stuck in a QUEUED state.  

I've verified that CPU and Memory match what I had given the VM when I built it in ESXi.

My current load does not show I'm out of Green.

CPU / Load Avg
0.31% (8 CPUs)
1 min 5 min 15 min
0.08 0.02 0.01
Memory [GB]
4.44%
Total Used Free
15.50 0.69 14.17
Disk [GB]
23.70%
Total Used Free
78.98 18.72 60.26
VM Stats
Allocated CPUs Allocated Memory Running VMs Total VMs
0 0.00 GB 0 8

Logs of the LAB show it started.

Lab Started 2021-01-28 13:37:47 info
Interface eth1.ubuntu_wBIRD0 DEFINED_ON_CLUSTER 2021-01-28 13:37:47 info
Interface eth0.ubuntu_wBIRD0 DEFINED_ON_CLUSTER 2021-01-28 13:37:47 info
Start Node Requested 2021-01-28 13:37:47 debug
Lab Started 2021-01-28 13:37:47 info
Interface eth1.ubuntu_wBIRD0 DEFINED_ON_CORE 2021-01-28 13:37:12 info
Interface eth0.ubuntu_wBIRD0 DEFINED_ON_CORE 2021-01-28 13:37:12 info
Wipe Node Requested 2021-01-28 13:37:12 debug
Lab Wiped 2021-01-28 13:37:12 info
Node ubuntu_wBIRD0 Defined 2021-01-28 13:37:11
info

Is there a file size limitation? Is there something I can look at in virtualization that would track down why this isn't starting?

I uploaded a vyos qcow2 and that launched just fine.

I can add other nodes and they start just fine.

[jpeterson]

I dug a little more into the console and am getting this error is presented when i click to start my ubuntu server with BIRD

i'm in /var/local/virl2/images/d3afef/8cb05d1-b7e2-47cb-a4be-81c7a47c6e8a/ but there is no nodedisk_0 file
I see disk clone failed errors above.  But why?

I'm going to reupload the qcow2 file and watch the logs to see if it imports it properly and report back.

[jpeterson · Accepted solution]

Ok so i followed https://www.youtube.com/watch?v=ur2G0dpMCBs as a guideline and it booted now.

But for some reason, I am finding randomly other vm's are going into a queued state.

Is there something to look at to find out why these won't boot?