n the
>>> /var/log/cloudstack/agent/agent.log)?
>>>
>>> One more question did you update and the management with the 4.15.1.0
>>> version?
>>>
>>> Kind regards,
>>> Slavka
>>>
>>>> On Tue, Jun 1, 2021 at 4:33 P
> >>
> >>
> >> I played around with cloudstack 4.15 and UEFI boot until someone here
> >> pointed me to a PR which fixes the problem with the missing q35 chipset.
> >>
> >> Thats the reason why I just installed the 4.15.1 SNAPSHOT.
> >>
&g
eason why I just installed the 4.15.1 SNAPSHOT.
Now I get the following problem:
Unable to start VM on Host... due to Unsupported Configuration: IDE
controllers
are unsupported for this QEMU binary or machine type
I am using cloudstack on CentOS 7.9 with
# rpm -qa | egrep "(qemu|lib
the problem with the missing q35 chipset.
>
> Thats the reason why I just installed the 4.15.1 SNAPSHOT.
>
> Now I get the following problem:
>
> Unable to start VM on Host... due to Unsupported Configuration: IDE
> controllers
> are unsupported for this QEMU binary or mach
Hi guys,
I played around with cloudstack 4.15 and UEFI boot until someone here
pointed me to a PR which fixes the problem with the missing q35 chipset.
Thats the reason why I just installed the 4.15.1 SNAPSHOT.
Now I get the following problem:
Unable to start VM on Host... due to
vidan
Enviado: domingo, 9 de mayo de 2021 16:17
Para: users@cloudstack.apache.org
Asunto: Unable to start VM due to insufficient capacity
Hello,
I just stopped two VMs residing on one of primary storages and they just
failed to start. VMs residing on a different primary storage are starting
well. Th
Hello,
I just stopped two VMs residing on one of primary storages and they just
failed to start. VMs residing on a different primary storage are starting
well. The NFS storage is mounted on the host (1 host available) and has
access to it. The volume is ready and the file exists on the storage.
Ho
Unable to start VM on Host[-1-Routing] due to internal error: guest failed
to start: cannot find init path '/sbin/init' relative to container root: No
such file or directory
You can google a bit - seems related to LXC stuff
On Mon, 17 Jun 2019 at 16:23, Alejandro Ruiz Bermejo &l
Hi,
Well this is awkward a few days ago i managed, with help from here, to
create an LXC cluster and launch an LXC instance. Then suddenly now i can't
start any VM inside the cluster and i think is due to a network error. I
checked the instance logs and the creation of it was successful but it
cras
deus House, Floral Street, London WC2E 9DPUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: peter.murysh...@zv.fraunhofer.de
> Sent: 29 April 2019 14:00
> To: users@cloudstack.apache.org
> Subject: AW: Troubleshooting the Exception "Unable to start VM i
deus House, Floral Street, London WC2E 9DPUK
@shapeblue
-Original Message-
From: peter.murysh...@zv.fraunhofer.de
Sent: 29 April 2019 14:00
To: users@cloudstack.apache.org
Subject: AW: Troubleshooting the Exception "Unable to start VM instance"
Hi, Rakesh,
thanks!
After
kind regards
Peter
Von: Rakesh Venkatesh [www.rakeshv@gmail.com]
Gesendet: Montag, 29. April 2019 13:17
An: users@cloudstack.apache.org
Betreff: Re: Troubleshooting the Exception "Unable to start VM instance"
Hello Peter
If you dig into logs a li
the logs there is the following trace - how to troubleshoot it and
> understand which circumstances lead to it?
>
>
> com.cloud.utils.exception.CloudRuntimeException: Unable to start VM
> instance
> at
> com.cloud.vm.VirtualMachineManagerImpl.orchestr
Hi, all,
sometimes the system can't start a VM instance (a 530 error).
In the logs there is the following trace - how to troubleshoot it and
understand which circumstances lead to it?
com.cloud.utils.exception.CloudRuntimeException: Unable to start VM instance
ssage ---
From: Jeremy Peterson
To: "users@cloudstack.apache.org"
Sent: Thu, 13 Jul 2017 21:26:21 +
Subject: Unable to Start VM SR failure
> Ok so I am back at the users again.
>
> I had 1 VM lock up today and was forced to issue a restart as the OS
> was
Ok so I am back at the users again.
I had 1 VM lock up today and was forced to issue a restart as the OS was non
responsive.
After powering off the VM bounced around between hosts and ultimately stopped
and failed with an insufficient resources error.
I looked around in XenServer and found the
uot;details":"com.cloud.agent.api.StartCommand
fail on exceptionObject reference not set to an instance of an
object.","contextMap":{},"wait":0}}]
.
.
.
2015-09-17 04:45:07,844 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-295:ctx-f5578a04) (logid:d11afe7a) executeRequest
received response [{"com.cloud.agent.api.StartAnswer":{"vm":{"
id":1241,"name":"v-1241-VM","type":"ConsoleProxy","cpus":1,"minSpeed":500,"maxSpeed":500,"minRam":1073741824,"maxRam":1073741824,"arch":"x86_64","os":"Debian
GNU/Linux 7(64-bit)","bootArgs":"
template\u003ddomP type\u003dconsoleproxy host\u003d172.16.116.219
port\u003d8250 name\u003dv-1241-VM zone\u003d9 pod\u003d9
guid\u003dProxy.1241 proxy_vm\u003d1241 disable_rp_filter\u003dtrue
vmpassword\u003dtCUAMd6x eth2ip\u003daa.bb.cc.138
eth2mask\u003d255.255.255.0 gateway\u003daa.bb.cc.10
eth0ip\u003d169.254.2.35 eth0mask\u003d255.255.0.0
eth1ip\u003dxx.yy.zz.163 eth1mask\u003d255.255.255.0
mgmtcidr\u003d172.16.116.0/23 localgw\u003dxx.yy.zz.10
internaldns1\u003dxx.yy.zz.180 internaldns2\u003dmm.nn.oo.171
dns1\u003dxx.yy.zz.180
dns2\u003dmm.nn.oo.171","enableHA":false,"limitCpuUse":false,"enableDynamicallyScaleVm":false,,"params":{},"uuid":"b6119681-e6da-4617-a2dd-504e5f82fe4a","disks":[{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"0c3d902f-8840-41d7-8c87-df860ea6ffcd","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"587027e4-e766-30fa-8972-d8ed9515170b","id":13,"poolType":"SMB","host":"xx.yy.zz.223","path":"/primary","port":445,"url":"SMB://xx.yy.zz.223/primary/?ROLE\u003dPrimary\u0026STOREUUID\u003d587027e4-e766-30fa-8972-d8ed9515170b"}},"name":"ROOT-1241","size":0,"path":"0c3d902f-8840-41d7-8c87-df860ea6ffcd","volumeId":1075,"vmName":"v-124VM","accountId":1,"format":"VHD","provisioningType":"THIN","id":1075,"deviceId":0,"hypervisorType":"Hyperv"}},"diskSeq":
0,"path":"0c3d902f-8840-41d7-8c87-df860ea6ffcd","type":"ROOT","_details":{"managed":"false","storagePort":"445","storageHost":"xx.yy.zz.223","volumeSize":"0"}}],"nics":[{"deviceId":2,"networkRateMbps":-1,"defaultNic":true,"pxeDisable":true,"nicUuid":"42a9765e-b84f-4199-9446-145df4bc68de","uuid":"a4a46926-8caf-4bee-b1a0-70529c3ecac6","ip":"aa.bb.cc.138","netmask":"255.255.255.0","gateway":"aa.bb.cc.10","mac":"06:4d:90:00:00:0d","dns1":"xx.yy.zz.180","dns2":"mm.nn.oo.171","broadcastType":"Native","type":"Guest","broadcastUri":"vlan://untagged","isSecurityGroupEnabled":false,"name":"Virtual
Switch"},{"deviceId":0,"networkRateMbps":-1,"defaultNic":false,"pxeDisable":true,"nicUuid":"1cba88d1-5867-4073-a2fd-c8139a8a5a1a","uuid":"e548abca-23da-4568-96e4-3a6aa709566b","ip":"169.254.2.35","netmask":"255.255.0.0","gateway":"169.254.0.1","mac":"0e:00:a9:fe:02:23","broadcastType":"LinkLocal","type":"Control","isSecurityGroupEnabled":false},{"deviceId":1,"networkRateMbps":-1,"defaultNic":false,"pxeDisable":true,"nicUuid":"bb80257d-1578-4643-95b7-63a72f80703a","uuid":"d149dd9f-ac98-411d-9fb0-e587852a9df1","ip":"xx.yy.zz.163","netmask":"255.255.255.0","gateway":"xx.yy.zz.10","mac":"06:0c:48:00:00:3e","broadcastType":"Native","type":"Management","isSecurityGroupEnabled":false,"name":"Virtual
Switch"}]},"result":false,"details":"com.cloud.agent.api.StartCommand
fail on exceptionObject reference not set to an instance of an
object.","contextMap":{},"wait":0}}]
.
.
.
2015-09-17 04:45:07,888 INFO [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-57:ctx-fb0c16f6 job-126/job-7169 ctx-d0465230)
(logid:d11afe7a) Unable to start VM on Host[-94-Routing] due to
com.cloud.agent.api.StartCommand fail on exceptionObject reference not
set to an instance of an object.
--- ---
created and destroyed continuously (Console Proxy nd
>> Secondary Storage VM) (confirmed by the cloudstack manager logs)
>> - System VMs appear as stopped in the CloudStack web interface, and
>> periodically vanish.
>>
>> Looking through the logs the VM build p
tack manager logs)
> - System VMs appear as stopped in the CloudStack web interface, and
> periodically vanish.
>
> Looking through the logs the VM build process fails with this message:
>
> ---
> .
> .
>
> 2015-09-17 04:45:07,888 INFO [c.c.v.VirtualMachineManagerImpl]
> (Work-Job-Exe
ously (Console Proxy nd
> Secondary Storage VM) (confirmed by the cloudstack manager logs)
> - System VMs appear as stopped in the CloudStack web interface, and
> periodically vanish.
>
> Looking through the logs the VM build process fails with this message:
>
> ---
> .
tx-fb0c16f6 job-126/job-7169 ctx-d0465230)
(logid:d11afe7a) Unable to start VM on Host[-94-Routing] due to
com.cloud.agent.api.StartCommand fail on exceptionObject reference not
set to an instance of an object.
.
.
.
---
Details of my setup:
1. Hyper-V Version: Hypervisor version 6.2
2. CloudS
stack manager logs)
>> - System VMs appear as stopped in the CloudStack web interface, and
>> periodically vanish.
>>
>> Looking through the logs the VM build process fails with this message:
>>
>> ---
>> .
>> .
>>
>> 2015-09-17 04:45:07,888
[c.c.v.VirtualMachineManagerImpl]
> (Work-Job-Executor-57:ctx-fb0c16f6 job-126/job-7169 ctx-d0465230)
> (logid:d11afe7a) Unable to start VM on Host[-94-Routing] due to
> com.cloud.agent.api.StartCommand fail on exceptionObject reference not
> set to an instance of an object.
>
INFO [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-57:ctx-fb0c16f6 job-126/job-7169 ctx-d0465230)
(logid:d11afe7a) Unable to start VM on Host[-94-Routing] due to
com.cloud.agent.api.StartCommand fail on exceptionObject reference not
set to an instance of an object.
.
.
.
---
Details of my setu
Thank you, Somesh
Will try to upgrade.
Best regards
Yuri
> From: somesh.na...@citrix.com
> To: users@cloudstack.apache.org
> Subject: RE: Unable to start VM due to the HOST_NOT_ENOUGH_FREE_MEMORY error
> on XenServer
> Date: Mon, 26 Ja
that version to fix this
issue.
Regards,
Somesh
-Original Message-
From: Yuri Kogun [mailto:yko...@outlook.com]
Sent: Monday, January 26, 2015 11:10 AM
To: users@cloudstack.apache.org
Subject: RE: Unable to start VM due to the HOST_NOT_ENOUGH_FREE_MEMORY error on
XenServer
Hi Somesh
not inside cloudstack in the management log.
Best regards
Yuri
> From: somesh.na...@citrix.com
> To: users@cloudstack.apache.org
> Subject: RE: Unable to start VM due to the HOST_NOT_ENOUGH_FREE_MEMORY error
> on XenServer
> Date: Mon,
10:26 AM
To: users@cloudstack.apache.org
Subject: Unable to start VM due to the HOST_NOT_ENOUGH_FREE_MEMORY error on
XenServer
Hi,
I wonder if somebody experienced a similar issue. We have a very busy dev
cloudstack installation with 10 hosts, 3 clusters and more than 300 user VM's
runn
Hi,
I wonder if somebody experienced a similar issue. We have a very busy dev
cloudstack installation with 10 hosts, 3 clusters and more than 300 user VM's
running across the clusters. The cpu over-provisioning is set to 3. From time
to time we are getting the following an error when starting
December 30, 2014 21:26
> To: users@cloudstack.apache.org
> Cc: d...@cloudstack.apache.org
> Subject: Re: Unable to start VM due to concurrent operation
>
> systemvm64template-2014-01-14-master-kvm.qcow2.bz2 This is the template i
> used.
>
>
> On 31 December 2014 at 07:49, Moh
ary 02, 2015 7:03 AM
>> To: users@cloudstack.apache.org
>> Cc: d...@cloudstack.apache.org
>> Subject: Re: Unable to start VM due to concurrent operation
>>
>> Hi all,
>>
>> I did redeploy cloudstack and i used the
>>
>> >> 1. /usr/share/cloudstack-c
Infaz [mailto:infaz...@cse.mrt.ac.lk]
> Sent: Friday, January 02, 2015 7:03 AM
> To: users@cloudstack.apache.org
> Cc: d...@cloudstack.apache.org
> Subject: Re: Unable to start VM due to concurrent operation
>
> Hi all,
>
> I did redeploy cloudstack and i used the
>
> >&
e.org
Subject: Re: Unable to start VM due to concurrent operation
Hi all,
I did redeploy cloudstack and i used the
>> 1. /usr/share/cloudstack-common/
scripts/storage/secondary/cloud-install-sys-tmplt \
>> 2. -m /srv/images/secondary \
>> 3. -u
http://download.
ned in 4.3.
> >>
> >> Thank you.
> >>
> >> On 1 January 2015 at 01:39, Somesh Naidu
> wrote:
> >>
> >>> You mean the system VMs for Zone 1 are running? Are they showing as
> >>> connected in the DB?
> >>>
> >&
;> On 1 January 2015 at 01:39, Somesh Naidu wrote:
>>
>>> You mean the system VMs for Zone 1 are running? Are they showing as
>>> connected in the DB?
>>>
>>> If they are, can you stop these VMs and see if they start okay.
>>>
: Mohamed Infaz [infaz...@cse.mrt.ac.lk]
>> Sent: Tuesday, December 30, 2014 21:26
>> To: users@cloudstack.apache.org
>> Cc: d...@cloudstack.apache.org
>> Subject: Re: Unable to start VM due to concurrent operation
>>
>> systemvm64template-2014-01-14-master-kvm.qcow2.bz2 Thi
and see if they start okay.
>
> From: Mohamed Infaz [infaz...@cse.mrt.ac.lk]
> Sent: Tuesday, December 30, 2014 21:26
> To: users@cloudstack.apache.org
> Cc: d...@cloudstack.apache.org
> Subject: Re: Unable to start VM due to concurrent operation
>
> systemvm64t
@cloudstack.apache.org
Cc: d...@cloudstack.apache.org
Subject: Re: Unable to start VM due to concurrent operation
systemvm64template-2014-01-14-master-kvm.qcow2.bz2 This is the template i used.
On 31 December 2014 at 07:49, Mohamed Infaz wrote:
> Hi Somesh,
>
> Thank you for the reply. Well b
ing system VM template. Please verify that you
>> have correctly provisioned the secondary storage with the correct system VM
>> template (as per the docs).
>>
>> -Somesh
>>
>> -Original Message-----
>> From: Mohamed Infaz [mailto:infaz...@cse.mrt.a
z [mailto:infaz...@cse.mrt.ac.lk]
> Sent: Tuesday, December 30, 2014 11:03 AM
> To: users@cloudstack.apache.org
> Cc: d...@cloudstack.apache.org
> Subject: Unable to start VM due to concurrent operation
>
> Hi All,
>
> I have successfully deployed cloudstack 4.3 with two hosts and the
k.apache.org
Cc: d...@cloudstack.apache.org
Subject: Unable to start VM due to concurrent operation
Hi All,
I have successfully deployed cloudstack 4.3 with two hosts and the setup
runs the management server on another physical host. I had issues with
downloading an ISO but finally i was able to
"Unable
to start VM due to concurrent operation" i did some searching on the topic
and it said version 4.3 system template solved the issue. These are some of
the MS logs that i collected what could be the issue?
2014-12-31 05:25:07,972 DEBUG [c.c.s.s.SecondaryStorageManagerImpl]
(secsto
Hi,
I have same error after computing node restaring ...
Did you find solution? fix ?
On Sat, Nov 16, 2013 at 3:17 PM, m2m isb wrote:
> Hello All
>
>
>
> We have a problem about Starting VMs.
>
> We have a ClousdStack 4.1.1 running with KVM,
> Unable to start VMs with Following error.
>
>
> Cl
Hello All
We have a problem about Starting VMs.
We have a ClousdStack 4.1.1 running with KVM,
Unable to start VMs with Following error.
CloudStack management Server Log.
/var/log/cloudstack/management/management-server.log
2013-11-16 14:30:56,859 DEBUG [cloud.deploy.FirstFitPlanner]
(Job
44 matches
Mail list logo
