Re: lxc on cloudstack

2014-08-01 Thread Rajani Karuturi
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

lxc on cloudstack

2014-07-31 Thread Osamu Ikehara
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

Fail to attach volume to LXC in CloudStack 4.2

2014-01-28 Thread Du Jun
Hi all,
Recently, I am stuck in attaching volumes to Linux Container using
CloudStack 4.2. But I got the error:Failed to attach volume: data-111 to
VM: lxc-111; org.libvirt.LibvirtException: unsupported configuration: Can't
setup disk for non-block device.

It seems that cause is libvirt, does libvirt has the API to attach volume
to LXC?

I really have no idea about that. Can anyone help me out? Thanks.

--
Best regards,
DuJun