registering the template with requireshvm=false or executing the below query worked for me update vm_template set hvm=0 where id=‘TEMPLATE_ID’;
I don’t know what the flag does or why it doesn’t work with lxc. ~Rajani On 01-Aug-2014, at 11:09 am, Osamu Ikehara <ikeh...@joes.co.jp> wrote: > Hello, > > I am stacking about cloudstack + lxc. > > what I did is > > Ubuntu 14.04 trusty, cloudstack 4.4 installed from > http://cloudstack.apt-get.eu/ubuntu/dists/trusty/ > > create management node -> fine > add kvm cluster -> fine > add kvm agent -> fine > create second storage vm, console vm -> fine > add lxc cluster -> fine > add lxc agent -> seems to be fine > > add lxc instance adding iso -> ..... > > log is below. > > is anyone able to create lxc instance on cloudstack? > what is the mean 'they are not HVM enabled' ? > please tell me how to create lxc. > > Thank you. > > 2014-08-01 13:08:43,304 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] > (API-Job-Executor-52:ctx-0f32ce3a job-56) Executing AsyncJobVO {id:56, > userId: 2, accountId: 2, instanceType: VirtualMachine, instanceId: 3, cmd: > org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin, cmdInfo: > {"serviceofferingid":"ca9ec6a0-10e3-4101-9b4e-32da49929397","sessionkey":"ZXZElEJY2wGlUjbYc8mYMTjEKDU\u003d","cmdEventType":"VM.CREATE","ctxUserId":"2","zoneid":"e32f5ae1-5a01-4f44-b4ae-cc09419efd11","httpmethod":"GET","templateid":"60a6ae31-3690-4122-8cbe-ad106f18679f","response":"json","id":"3","ctxDetails":"{\"com.cloud.template.VirtualMachineTemplate\":\"60a6ae31-3690-4122-8cbe-ad106f18679f\",\"com.cloud.vm.VirtualMachine\":\"f362e2be-e7a7-40a6-9388-556e95583d0b\",\"com.cloud.offering.DiskOffering\":\"842daf1f-bfd5-425b-a6f3-3f6fa06fd90a\",\"com.cloud.dc.DataCenter\":\"e32f5ae1-5a01-4f44-b4ae-cc09419efd11\",\"com.cloud.offering.ServiceOffering\":\"ca9ec6a0-10e3-4101-9b4e-32da49929397\"}","hypervisor":"L > XC","iptonetworklist[0].networkid":"c220e198-baf3-419d-b561-dddb2b79540a","_":"1406866122712","uuid":"f362e2be-e7a7-40a6-9388-556e95583d0b","ctxAccountId":"2","diskofferingid":"842daf1f-bfd5-425b-a6f3-3f6fa06fd90a","ctxStartEventId":"147"}, > cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: > null, initMsid: 109955820418, completeMsid: null, lastUpdated: null, > lastPolled: null, created: null} > 2014-08-01 13:08:43,405 DEBUG [c.c.n.NetworkModelImpl] > (API-Job-Executor-52:ctx-0f32ce3a job-56 ctx-f436dcd7) Service SecurityGroup > is not supported in the network id=208 > 2014-08-01 13:08:43,408 DEBUG [c.c.n.NetworkModelImpl] > (API-Job-Executor-52:ctx-0f32ce3a job-56 ctx-f436dcd7) Service SecurityGroup > is not supported in the network id=208 > 2014-08-01 13:08:43,427 DEBUG [c.c.d.DeploymentPlanningManagerImpl] > (API-Job-Executor-52:ctx-0f32ce3a job-56 ctx-f436dcd7) Deploy avoids pods: > [], clusters: [], hosts: [] > 2014-08-01 13:08:43,428 DEBUG [c.c.d.DeploymentPlanningManagerImpl] > (API-Job-Executor-52:ctx-0f32ce3a job-56 ctx-f436dcd7) DeploymentPlanner > allocation algorithm: com.cloud.deploy.FirstFitPlanner@5e99834a > 2014-08-01 13:08:43,428 DEBUG [c.c.d.DeploymentPlanningManagerImpl] > (API-Job-Executor-52:ctx-0f32ce3a job-56 ctx-f436dcd7) Trying to allocate a > host and storage pools from dc:2, pod:null,cluster:null, requested cpu: 500, > requested ram: 536870912 > 2014-08-01 13:08:43,428 DEBUG [c.c.d.DeploymentPlanningManagerImpl] > (API-Job-Executor-52:ctx-0f32ce3a job-56 ctx-f436dcd7) Is ROOT volume READY > (pool already allocated)?: No > 2014-08-01 13:08:43,429 DEBUG [c.c.d.FirstFitPlanner] > (API-Job-Executor-52:ctx-0f32ce3a job-56 ctx-f436dcd7) Searching all possible > resources under this Zone: 2 > 2014-08-01 13:08:43,430 DEBUG [c.c.d.FirstFitPlanner] > (API-Job-Executor-52:ctx-0f32ce3a job-56 ctx-f436dcd7) Listing clusters in > order of aggregate capacity, that have (atleast one host with) enough CPU and > RAM capacity under this Zone: 2 > 2014-08-01 13:08:43,433 DEBUG [c.c.d.FirstFitPlanner] > (API-Job-Executor-52:ctx-0f32ce3a job-56 ctx-f436dcd7) Removing from the > clusterId list these clusters from avoid set: [] > 2014-08-01 13:08:43,439 DEBUG [c.c.d.DeploymentPlanningManagerImpl] > (API-Job-Executor-52:ctx-0f32ce3a job-56 ctx-f436dcd7) Checking resources in > Cluster: 3 under Pod: 2 > 2014-08-01 13:08:43,439 DEBUG [c.c.a.m.a.i.FirstFitAllocator] > (API-Job-Executor-52:ctx-0f32ce3a job-56 ctx-f436dcd7 > FirstFitRoutingAllocator) Looking for hosts in dc: 2 pod:2 cluster:3 > 2014-08-01 13:08:43,441 DEBUG [c.c.a.m.a.i.FirstFitAllocator] > (API-Job-Executor-52:ctx-0f32ce3a job-56 ctx-f436dcd7 > FirstFitRoutingAllocator) FirstFitAllocator has 1 hosts to check for > allocation: [Host[-5-Routing]] > 2014-08-01 13:08:43,443 DEBUG [c.c.a.m.a.i.FirstFitAllocator] > (API-Job-Executor-52:ctx-0f32ce3a job-56 ctx-f436dcd7 > FirstFitRoutingAllocator) Not considering hosts: [Host[-5-Routing]] to > deploy template: Tmpl[201-ISO-201-2-e9eacfcd-1360-3e1d-8b5b-497997678249 as > they are not HVM enabled > 2014-08-01 13:08:43,444 DEBUG [c.c.a.m.a.i.FirstFitAllocator] > (API-Job-Executor-52:ctx-0f32ce3a job-56 ctx-f436dcd7 > FirstFitRoutingAllocator) Found 0 hosts for allocation after prioritization: > [] > 2014-08-01 13:08:43,444 DEBUG [c.c.a.m.a.i.FirstFitAllocator] > (API-Job-Executor-52:ctx-0f32ce3a job-56 ctx-f436dcd7 > FirstFitRoutingAllocator) Looking for speed=500Mhz, Ram=512 > 2014-08-01 13:08:43,444 DEBUG [c.c.a.m.a.i.FirstFitAllocator] > (API-Job-Executor-52:ctx-0f32ce3a job-56 ctx-f436dcd7 > FirstFitRoutingAllocator) Host Allocator returning 0 suitable hosts > 2014-08-01 13:08:43,444 DEBUG [c.c.d.DeploymentPlanningManagerImpl] > (API-Job-Executor-52:ctx-0f32ce3a job-56 ctx-f436dcd7) No suitable hosts found > 2014-08-01 13:08:43,444 DEBUG [c.c.d.DeploymentPlanningManagerImpl] > (API-Job-Executor-52:ctx-0f32ce3a job-56 ctx-f436dcd7) No suitable hosts > found under this Cluster: 3 > 2014-08-01 13:08:43,446 DEBUG [c.c.d.DeploymentPlanningManagerImpl] > (API-Job-Executor-52:ctx-0f32ce3a job-56 ctx-f436dcd7) Cluster: 2 has > HyperVisorType that does not match the VM, skipping this cluster > 2014-08-01 13:08:43,446 DEBUG [c.c.d.DeploymentPlanningManagerImpl] > (API-Job-Executor-52:ctx-0f32ce3a job-56 ctx-f436dcd7) Could not find > suitable Deployment Destination for this VM under any clusters, returning. > 2014-08-01 13:08:43,447 DEBUG [c.c.d.FirstFitPlanner] > (API-Job-Executor-52:ctx-0f32ce3a job-56 ctx-f436dcd7) Searching all possible > resources under this Zone: 2 > 2014-08-01 13:08:43,448 DEBUG [c.c.d.FirstFitPlanner] > (API-Job-Executor-52:ctx-0f32ce3a job-56 ctx-f436dcd7) Listing clusters in > order of aggregate capacity, that have (atleast one host with) enough CPU and > RAM capacity under this Zone: 2 > 2014-08-01 13:08:43,450 DEBUG [c.c.d.FirstFitPlanner] > (API-Job-Executor-52:ctx-0f32ce3a job-56 ctx-f436dcd7) Removing from the > clusterId list these clusters from avoid set: [2, 3] > 2014-08-01 13:08:43,450 DEBUG [c.c.d.FirstFitPlanner] > (API-Job-Executor-52:ctx-0f32ce3a job-56 ctx-f436dcd7) No clusters found > after removing disabled clusters and clusters in avoid list, returning. > 2014-08-01 13:08:43,452 DEBUG [c.c.v.UserVmManagerImpl] > (API-Job-Executor-52:ctx-0f32ce3a job-56 ctx-f436dcd7) Destroying vm > VM[User|i-2-3-VM] as it failed to create on Host with Id:null > 2014-08-01 13:08:43,518 DEBUG [c.c.c.CapacityManagerImpl] > (API-Job-Executor-52:ctx-0f32ce3a job-56 ctx-f436dcd7) VM state transitted > from :Stopped to Error with event: OperationFailedToErrorvm's original host > id: null new host id: null host id before state transition: null > 2014-08-01 13:08:43,693 WARN [o.a.c.alerts] > (API-Job-Executor-52:ctx-0f32ce3a job-56 ctx-f436dcd7) alertType:: 8 // > dataCenterId:: 2 // podId:: null // clusterId:: null // message:: Failed to > deploy Vm with Id: 3, on Host with Id: null > 2014-08-01 13:08:43,976 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin] > (API-Job-Executor-52:ctx-0f32ce3a job-56 ctx-f436dcd7) > com.cloud.exception.InsufficientServerCapacityException: Unable to create a > deployment for VM[User|i-2-3-VM]Scope=interface com.cloud.dc.DataCenter; id=2 > 2014-08-01 13:08:43,977 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin] > (API-Job-Executor-52:ctx-0f32ce3a job-56 ctx-f436dcd7) Unable to create a > deployment for VM[User|i-2-3-VM] > 2014-08-01 13:08:43,979 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] > (API-Job-Executor-52:ctx-0f32ce3a job-56) Complete async job-56, jobStatus: > FAILED, resultCode: 530, result: > org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":533,"errortext":"Unable > to create a deployment for VM[User|i-2-3-VM]"} > 2014-08-01 13:08:44,033 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] > (API-Job-Executor-52:ctx-0f32ce3a job-56) Done executing > org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin for job-56 > 2014-08-01 13:08:44,058 INFO [o.a.c.f.j.i.AsyncJobMonitor] > (API-Job-Executor-52:ctx-0f32ce3a job-56) Remove job-56 from job monitoring > > > > > > > -- > Osamu Ikehara <ikeh...@joes.co.jp>
