You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Stephan Seitz <s....@secretresearchfacility.com> on 2015/01/27 17:30:38 UTC
cloudmonkey / deploy virtualmachine from ISO
Hi there,
I'm trying to create instances via cloudmonkey with an ISO as
templateid. This is intentional, the VMs are supposed to boot from ISO.
Using cloudstack 4.4.2 and cloudmonkey 5.3.0 I got the following error:
(local) 🐵 > deploy virtualmachine
templateid=648ea3c5-8015-4bff-be2d-f2f4e4e7ae43
serviceofferingid=ef3b04fa-52a2-4eee-bcd2-fa7de438caae
networkids=2ab17815-dae1-4664-a991-bb4a5ad3346a
zoneid=a6afefa1-c770-42d5-b5fb-ab328d814bbd
diskofferingid=e28d6137-4a89-4e04-9a17-73100c318db0
.Error
Async job a860fa38-c817-4dfa-8fb6-fd96b02d9d07 failed
Error 533, Unable to create a deployment for VM[User|i-2-1262-VM]
accountid = 98fabd82-43ce-11e4-940f-0030487e3bf9
cmd = org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin
created = 2015-01-27T17:17:05+0100
jobid = a860fa38-c817-4dfa-8fb6-fd96b02d9d07
jobprocstatus = 0
jobresult:
errorcode = 533
errortext = Unable to create a deployment for VM[User|i-2-1262-VM]
jobresultcode = 530
jobresulttype = object
jobstatus = 2
userid = 98fac86e-43ce-11e4-940f-0030487e3bf9
The logfile states, that the HyperVisorType does not match my running
cluster. Interestingly, It works, If I deploy the very same machine via
GUI. The ISO Template has "OS Type Other (64-bit)".
Does that sound, if I'm holding it wrong? Or is it likely that I hit
some bug?
Thanks,
- Stephan
Below a snippet of /etc/cloudstack/management/management.log
015-01-27 17:27:17,882 DEBUG [c.c.d.FirstFitPlanner]
(API-Job-Executor-120:ctx-784091de job-26028 ctx-d5e58e10) Listing
clusters in order of aggregate capacity, that have (atleast one host
with) enough CPU and RAM capacity under this Zone: 1
2015-01-27 17:27:17,885 DEBUG [c.c.d.FirstFitPlanner]
(API-Job-Executor-120:ctx-784091de job-26028 ctx-d5e58e10) Removing from
the clusterId list these clusters from avoid set: []
2015-01-27 17:27:17,890 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
(API-Job-Executor-120:ctx-784091de job-26028 ctx-d5e58e10) Cluster: 2
has HyperVisorType that does not match the VM, skipping this cluster
2015-01-27 17:27:17,890 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
(API-Job-Executor-120:ctx-784091de job-26028 ctx-d5e58e10) Could not
find suitable Deployment Destination for this VM under any clusters,
returning.
2015-01-27 17:27:17,890 DEBUG [c.c.d.FirstFitPlanner]
(API-Job-Executor-120:ctx-784091de job-26028 ctx-d5e58e10) Searching all
possible resources under this Zone: 1
2015-01-27 17:27:17,891 DEBUG [c.c.d.FirstFitPlanner]
(API-Job-Executor-120:ctx-784091de job-26028 ctx-d5e58e10) Listing
clusters in order of aggregate capacity, that have (atleast one host
with) enough CPU and RAM capacity under this Zone: 1
2015-01-27 17:27:17,892 DEBUG [c.c.d.FirstFitPlanner]
(API-Job-Executor-120:ctx-784091de job-26028 ctx-d5e58e10) Removing from
the clusterId list these clusters from avoid set: [2]
2015-01-27 17:27:17,893 DEBUG [c.c.d.FirstFitPlanner]
(API-Job-Executor-120:ctx-784091de job-26028 ctx-d5e58e10) No clusters
found after removing disabled clusters and clusters in avoid list,
returning.
2015-01-27 17:27:17,894 DEBUG [c.c.v.UserVmManagerImpl]
(API-Job-Executor-120:ctx-784091de job-26028 ctx-d5e58e10) Destroying vm
VM[User|i-2-1264-VM] as it failed to create on Host with Id:null
2015-01-27 17:27:17,902 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-120:ctx-784091de job-26028 ctx-d5e58e10) 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
2015-01-27 17:27:17,907 WARN [o.a.c.alerts]
(API-Job-Executor-120:ctx-784091de job-26028 ctx-d5e58e10) alertType::
8 // dataCenterId:: 1 // podId:: null // clusterId:: null // message::
Failed to deploy Vm with Id: 1264, on Host with Id: null
2015-01-27 17:27:17,920 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin]
(API-Job-Executor-120:ctx-784091de job-26028 ctx-d5e58e10)
com.cloud.exception.InsufficientServerCapacityException: Unable to
create a deployment for VM[User|i-2-1264-VM]Scope=interface
com.cloud.dc.DataCenter; id=1
2015-01-27 17:27:17,921 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin]
(API-Job-Executor-120:ctx-784091de job-26028 ctx-d5e58e10) Unable to
create a deployment for VM[User|i-2-1264-VM]
com.cloud.exception.InsufficientServerCapacityException: Unable to
create a deployment for VM[User|i-2-1264-VM]Scope=interface
com.cloud.dc.DataCenter; id=1
at
org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:214)
at
org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:200)
Re: cloudmonkey / deploy virtualmachine from ISO
Posted by Stephan Seitz <s....@secretresearchfacility.com>.
Hi,
Am Dienstag, den 27.01.2015, 23:40 +0100 schrieb Rene Moser:
> Hi
>
> On 01/27/2015 05:30 PM, Stephan Seitz wrote:
> > Hi there,
> >
> > The logfile states, that the HyperVisorType does not match my running
> > cluster. Interestingly, It works, If I deploy the very same machine via
> > GUI. The ISO Template has "OS Type Other (64-bit)".
>
> I assume you have not touched the global setting about hypervisors, so
> there are still all hypervisors configured and if you don't provide the
> param hypervisor=<KVM|VMware|...> it will take the first specified in
> the global settings IMHO.
No. So far, I didn't touch the global settings. The defaults show a lot
of Hypervisors plus BareMetal and LXC. The "preferred" was set to
XenServer (which I'm using in that Zone as single technology).
I added the hypervisor=XenServer to my cloudmonkey commandline and it
worked :).
Interestingly I was never in the need for adding the hypervisor
statement. Using ISO as templateid obviously needs this.
Thank's for your suggestion!
cheers,
- Stephan
Re: cloudmonkey / deploy virtualmachine from ISO
Posted by Rene Moser <ma...@renemoser.net>.
Hi
On 01/27/2015 05:30 PM, Stephan Seitz wrote:
> Hi there,
>
> I'm trying to create instances via cloudmonkey with an ISO as
> templateid. This is intentional, the VMs are supposed to boot from ISO.
>
> Using cloudstack 4.4.2 and cloudmonkey 5.3.0 I got the following error:
>
> (local) 🐵 > deploy virtualmachine
> templateid=648ea3c5-8015-4bff-be2d-f2f4e4e7ae43
> serviceofferingid=ef3b04fa-52a2-4eee-bcd2-fa7de438caae
> networkids=2ab17815-dae1-4664-a991-bb4a5ad3346a
> zoneid=a6afefa1-c770-42d5-b5fb-ab328d814bbd
> diskofferingid=e28d6137-4a89-4e04-9a17-73100c318db0
> .Error
> Async job a860fa38-c817-4dfa-8fb6-fd96b02d9d07 failed
> Error 533, Unable to create a deployment for VM[User|i-2-1262-VM]
> accountid = 98fabd82-43ce-11e4-940f-0030487e3bf9
> cmd = org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin
> created = 2015-01-27T17:17:05+0100
> jobid = a860fa38-c817-4dfa-8fb6-fd96b02d9d07
> jobprocstatus = 0
> jobresult:
> errorcode = 533
> errortext = Unable to create a deployment for VM[User|i-2-1262-VM]
> jobresultcode = 530
> jobresulttype = object
> jobstatus = 2
> userid = 98fac86e-43ce-11e4-940f-0030487e3bf9
>
>
> The logfile states, that the HyperVisorType does not match my running
> cluster. Interestingly, It works, If I deploy the very same machine via
> GUI. The ISO Template has "OS Type Other (64-bit)".
I assume you have not touched the global setting about hypervisors, so
there are still all hypervisors configured and if you don't provide the
param hypervisor=<KVM|VMware|...> it will take the first specified in
the global settings IMHO.
If you only have 1 hypervisor, you should adjust this setting so you do
not have to provide the param "hypervisor" every time deploy a new VM.
Regards
René