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 PM Udo Müller wrote:
>>>
&
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:
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|libvirtd
xes 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 machine t
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
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. The NFS
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.
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 <
arberme
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
ral 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"
&
, 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 furth
ards
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 little b
ogs 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
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
---
From: Jeremy Peterson <jpeter...@acentek.net>
To: "users@cloudstack.apache.org" <users@cloudstack.apache.org>
Sent: Thu, 13 Jul 2017 21:26:21 +0000
Subject: Unable to Start VM SR failure
> Ok so I am back at the users again.
>
> I had 1 VM lock u
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
ough the logs the VM build process fails with this message:
>
> ---
> .
> .
>
> 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
udStack 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-Executor-57:ctx-fb0c16f6 job-126/job-7169 ctx-d0465230)
(logid:d11afe7a) Unable to start VM
management console:
>>
>> -The Cloudstack controller is successfully is launching and
>> destroying the system vms:
>> - System VMs are created and destroyed continuously (Console Proxy nd
>> Secondary Storage VM) (confirmed by the cloudstack manager logs)
>&
VMs are 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 process fails with this message:
&g
ry 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:
>>
>> ---
>> .
>> .
>&
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
[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 setup:
1
-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
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 Jan 2015 18:49:54 +
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, 26 Jan 2015 15:56:01 +
Yes, seen
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
running across
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
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,
Thank you
, 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, Mohamed Infaz infaz...@cse.mrt.ac.lk
@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-common/
scripts/storage/secondary/cloud-install-sys-tmplt \
2. -m /srv/images/secondary \
3. -u
http
[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
1. /usr/share/cloudstack-common/
scripts/storage
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.cloud.com/templates/4.3/systemvm64template
: 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 infaz...@cse.mrt.ac.lk
wrote:
Hi Somesh,
Thank you for the reply. Well both of my system vm's are running
.
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
systemvm64template-2014-01-14-master-kvm.qcow2.bz2 This is the template i
used
...@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 infaz...@cse.mrt.ac.lk
wrote:
Hi Somesh,
Thank you for the reply. Well both of my system
.
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
systemvm64template-2014-01-14-master-kvm.qcow2.bz2
@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 infaz...@cse.mrt.ac.lk wrote:
Hi Somesh,
Thank you for the reply
: 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 download an ISO
@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 setup
runs the management server on another physical host. I had issues with
downloading an ISO but finally i was able
the docs).
-Somesh
-Original Message-
From: Mohamed Infaz [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
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 isb...@gmail.com 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.
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]
43 matches
Mail list logo
