Hi I went over your log file. Here are some memorable mentions: - Checking resources in Cluster: 1 under Pod: 1 <- Tries to find resources for the VM - Looking for speed=500Mhz, Ram=1024 - Host name: xenserver, hostId: 1 is in avoid set, skipping this and trying other available hosts <- For some reason the host is skipped so no vms will be deployed on it. - Host Allocator returning 0 suitable hosts <- you do not have other hosts to deploy the VM - Could not find suitable Deployment Destination for this VM under any clusters, returning. <- no other cluster or hosts exist so the VM cannot be deployed - Listing clusters in order of aggregate capacity, that have (atleast one host with) enough CPU and RAM capacity under this Pod: 1 <<--- searching for resources - Removing from the clusterId list these clusters from avoid set: [1] <<-- removing clusters that are set in avoid mode. I guess your cluster may be in "disabled" state so it is excluded as VMs will not be deployed on disabled entities. - No clusters found after removing disabled clusters and clusters in avoid list, returning. <<- Same comment from the previous line.
- VM state transitted from :Starting to Stopped with event: OperationFailedvm's original host id: null new host id: null host id before state transition: 1 <--- Not sure if this is what it really means but HOST ID: NULL means that there was no chosen host the VM to be started anyway so starting operation got canceled. - Hosts's actual total CPU: 4416 and CPU after applying overprovisioning: 17664 <- Your host resoruces that CD sees. Not sure why CPU count is so high. - Hosts's actual total RAM: 2627446912 and RAM after applying overprovisioning: 2627446784 - This is the amount of RAM the host have (2.5 GB) - Invocation exception, caused by: com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[ConsoleProxy|v-2-VM]Scope=interface com.cloud.dc.DataCenter; id=1 <<-- You can see the error - Insufficient server capacity. Check if your cluster or host is in disabled state. May be this is why the system excludes him as a resource and ultimately decides that there are not enough resources. Best regards, Jordan -----Original Message----- From: fulc927 [mailto:fulc...@gmail.com] Sent: Thursday, October 25, 2018 1:41 AM To: users@cloudstack.apache.org Subject: Unable to create a deployment for VM Hello, First my environment is built following this tutorial https://www.shapeblue.com/virtualbox-test-env/ I am trying to setup properly Cloudstack as a proof-of-concept and eventually adopting it in more sophisticated configuration I am using cloudstack-management-4.11 and Citrix XenServer Host 7.5.0 I successfully create a zone and a primary storage, bad things are coming next, once SystemVMs have to boot. System VMs nevers successfully boot, they are stuck in an endless loop cycle (start-stop-start…) logs attached to this email report: > Deploy avoids pods: null, clusters: null, hosts: null > Unable to create a > deployment for VM My config has enough ressources to run the management server and the xen one in an virtualyzed environment I highly suspect a network misconfiguration, everything should be OK since i replicate the config from shapeblue: PRI STORAGE 10.10.100.11 SECONDARY STORAGE 10.10.101.11 MGMT TRAFFIC SERVER 192.168.56.11 XEN 192.168.56.101 POD SETTINGS 192.168.56.1 (21 - 30) PUBLIC TRAFFIC 172.30.0.(21 - 30 ) Maybe something is wrong on the MGMT network ? but since i can ping IPs properly I suspect something more tricky. If someone could help me giving a look faulty parameters, I can'f figure out why my cluster and pod load as null value and make the next processes messy Thanks Xen hypervisor seems good regarding storage:10.10.100.11:/exports/primary/ on /run/sr-mount/3473326c-6813-97dc-fd85-9f221d59892f type nfs (rw,relatime,vers=3,rsize=131072,wsize=131072,namlen=255,acdirmin=0,acdirmax=0,soft,proto=tcp,timeo=100,retrans=12,sec=sys,mountaddr=10.10.100.11,mountvers=3,mountport=892,mountproto=tcp,local_lock=none,addr=10.10.100.11) 10.10.101.11:/exports/secondary on /var/cloud_mount/fb486192-aa16-30d2-9278-c5704f273389 type nfs4 (rw,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,soft,proto=tcp,port=0,timeo=133,retrans=1,sec=sys,clientaddr=10.10.101.101,local_lock=none,addr=10.10.101.11)
2018-10-24 23:22:12,774 DEBUG [c.c.a.m.a.i.FirstFitAllocator] (Work-Job-Executor-3:ctx-cae4228c job-3/job-23 ctx-9c970034 FirstFitRoutingAllocator) (logid:dd21aa30) Looking for hosts in dc: 1 pod:1 cluster:1 2018-10-24 23:22:12,777 DEBUG [c.c.a.m.a.i.FirstFitAllocator] (Work-Job-Executor-3:ctx-cae4228c job-3/job-23 ctx-9c970034 FirstFitRoutingAllocator) (logid:dd21aa30) FirstFitAllocator has 1 hosts to check for allocation: [Host[-1-Routing]] 2018-10-24 23:22:12,778 DEBUG [c.c.h.x.r.CitrixResourceBase] (DirectAgent-42:ctx-cbbdf08e) (logid:f51ff972) already have a vif on dom0 for link local network 2018-10-24 23:22:12,780 DEBUG [c.c.a.m.a.i.FirstFitAllocator] (Work-Job-Executor-3:ctx-cae4228c job-3/job-23 ctx-9c970034 FirstFitRoutingAllocator) (logid:dd21aa30) Found 1 hosts for allocation after prioritization: [Host[-1-Routing]] 2018-10-24 23:22:12,780 DEBUG [c.c.a.m.a.i.FirstFitAllocator] (Work-Job-Executor-3:ctx-cae4228c job-3/job-23 ctx-9c970034 FirstFitRoutingAllocator) (logid:dd21aa30) Looking for speed=500Mhz, Ram=512 2018-10-24 23:22:12,780 DEBUG [c.c.a.m.a.i.FirstFitAllocator] (Work-Job-Executor-3:ctx-cae4228c job-3/job-23 ctx-9c970034 FirstFitRoutingAllocator) (logid:dd21aa30) Host name: xenserver, hostId: 1 is in avoid set, skipping this and trying other available hosts 2018-10-24 23:22:12,780 DEBUG [c.c.a.m.a.i.FirstFitAllocator] (Work-Job-Executor-3:ctx-cae4228c job-3/job-23 ctx-9c970034 FirstFitRoutingAllocator) (logid:dd21aa30) Host Allocator returning 0 suitable hosts 2018-10-24 23:22:12,780 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-3:ctx-cae4228c job-3/job-23 ctx-9c970034) (logid:dd21aa30) No suitable hosts found 2018-10-24 23:22:12,780 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-3:ctx-cae4228c job-3/job-23 ctx-9c970034) (logid:dd21aa30) No suitable hosts found under this Cluster: 1 2018-10-24 23:22:12,782 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-3:ctx-cae4228c job-3/job-23 ctx-9c970034) (logid:dd21aa30) Could not find suitable Deployment Destination for this VM under any clusters, returning. 2018-10-24 23:22:12,782 DEBUG [c.c.d.FirstFitPlanner] (Work-Job-Executor-3:ctx-cae4228c job-3/job-23 ctx-9c970034) (logid:dd21aa30) Searching resources only under specified Cluster: 1 2018-10-24 23:22:12,783 DEBUG [c.c.d.FirstFitPlanner] (Work-Job-Executor-3:ctx-cae4228c job-3/job-23 ctx-9c970034) (logid:dd21aa30) The specified cluster is in avoid set, returning. 2018-10-24 23:22:12,785 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-3:ctx-cae4228c job-3/job-23 ctx-9c970034) (logid:dd21aa30) DeploymentPlanner allocation algorithm: null 2018-10-24 23:22:12,786 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-3:ctx-cae4228c job-3/job-23 ctx-9c970034) (logid:dd21aa30) Trying to allocate a host and storage pools from dc:1, pod:1,cluster:null, requested cpu: 500, requested ram: 536870912 2018-10-24 23:22:12,786 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-3:ctx-cae4228c job-3/job-23 ctx-9c970034) (logid:dd21aa30) Is ROOT volume READY (pool already allocated)?: No 2018-10-24 23:22:12,789 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-3:ctx-cae4228c job-3/job-23 ctx-9c970034) (logid:dd21aa30) Deploy avoids pods: null, clusters: [1], hosts: [1] 2018-10-24 23:22:12,790 DEBUG [c.c.d.FirstFitPlanner] (Work-Job-Executor-3:ctx-cae4228c job-3/job-23 ctx-9c970034) (logid:dd21aa30) Searching resources only under specified Pod: 1 2018-10-24 23:22:12,790 DEBUG [c.c.d.FirstFitPlanner] (Work-Job-Executor-3:ctx-cae4228c job-3/job-23 ctx-9c970034) (logid:dd21aa30) Listing clusters in order of aggregate capacity, that have (atleast one host with) enough CPU and RAM capacity under this Pod: 1 2018-10-24 23:22:12,793 DEBUG [c.c.d.FirstFitPlanner] (Work-Job-Executor-3:ctx-cae4228c job-3/job-23 ctx-9c970034) (logid:dd21aa30) Removing from the clusterId list these clusters from avoid set: [1] 2018-10-24 23:22:12,795 DEBUG [c.c.d.FirstFitPlanner] (Work-Job-Executor-3:ctx-cae4228c job-3/job-23 ctx-9c970034) (logid:dd21aa30) No clusters found after removing disabled clusters and clusters in avoid list, returning. 2018-10-24 23:22:12,803 DEBUG [c.c.c.CapacityManagerImpl] (Work-Job-Executor-3:ctx-cae4228c job-3/job-23 ctx-9c970034) (logid:dd21aa30) VM state transitted from :Starting to Stopped with event: OperationFailedvm's original host id: null new host id: null host id before state transition: 1 2018-10-24 23:22:12,807 DEBUG [c.c.c.CapacityManagerImpl] (Work-Job-Executor-3:ctx-cae4228c job-3/job-23 ctx-9c970034) (logid:dd21aa30) Hosts's actual total CPU: 4416 and CPU after applying overprovisioning: 17664 2018-10-24 23:22:12,807 DEBUG [c.c.c.CapacityManagerImpl] (Work-Job-Executor-3:ctx-cae4228c job-3/job-23 ctx-9c970034) (logid:dd21aa30) Hosts's actual total RAM: 2627446912 and RAM after applying overprovisioning: 2627446784 2018-10-24 23:22:12,807 DEBUG [c.c.c.CapacityManagerImpl] (Work-Job-Executor-3:ctx-cae4228c job-3/job-23 ctx-9c970034) (logid:dd21aa30) release cpu from host: 1, old used: 1000,reserved: 0, actual total: 4416, total with overprovisioning: 17664; new used: 500,reserved:0; movedfromreserved: false,moveToReserveredfalse 2018-10-24 23:22:12,807 DEBUG [c.c.c.CapacityManagerImpl] (Work-Job-Executor-3:ctx-cae4228c job-3/job-23 ctx-9c970034) (logid:dd21aa30) release mem from host: 1, old used: 1610612736,reserved: 0, total: 2627446784; new used: 1073741824,reserved:0; movedfromreserved: false,moveToReserveredfalse 2018-10-24 23:22:12,811 ERROR [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-3:ctx-cae4228c job-3/job-23 ctx-9c970034) (logid:dd21aa30) Invocation exception, caused by: com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[SecondaryStorageVm|s-1-VM]Scope=interface com.cloud.dc.DataCenter; id=1 2018-10-24 23:22:12,811 INFO [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-3:ctx-cae4228c job-3/job-23 ctx-9c970034) (logid:dd21aa30) Rethrow exception com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[SecondaryStorageVm|s-1-VM]Scope=interface com.cloud.dc.DataCenter; id=1