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é
