Hi,
it looks like your VirtualRouter is failing to deploy and the virtual machine
you are trying to deploy is depending on the successful deployment of the
virtual router:
For the virtualrouter:
"No clusters found having a host with enough capacity, returning"
2023-09-04 14:53:18,705 DEBUG [o.
Hi,
It looks like there was not enough memory.
-Wei
On Mon, 4 Sept 2023 at 11:08, Technology Mail
wrote:
> Hello,
>
> Unable to deploy vm instance,
>
> My server is alam 8.
>
> 1. MGMT+NFS
> 2. KVM
>
> +
>
> Unable to start a VM [55d71859-ae54-4e12-8de3-8f84fe9627bf] due to
> [
2014 10:54 AM
> To: users@cloudstack.apache.org; d...@cloudstack.apache.org
> Subject: Re: Unable to deploy vm
>
> Hi,
>
> Please ignore previous mail,
> I think I misunderstood & deleted stale sysetmvm.iso. Still I am facing
> same error .
>
> So Under "Templates"
: Tejas Gadaria [mailto:refond.g...@gmail.com]
Sent: Friday, February 28, 2014 10:54 AM
To: users@cloudstack.apache.org; d...@cloudstack.apache.org
Subject: Re: Unable to deploy vm
Hi,
Please ignore previous mail,
I think I misunderstood & deleted stale sysetmvm.iso. Still I am facing same
e
while uploading template to primary storage URL and
>> cleanup stale template. Working on unit testing now.
>>
>> We have work around for this issue. Delete the stale template that was
>> created in datacenter due to failed PrimaryStorageDownloadCommand.
>> Subsequently a template would be setup again freshly.
>>
>> ==
late would be setup again freshly.
>
>
>
>
> Thanks,
> Sailaja.M
>
> -Original Message-
> From: Tejas Gadaria [mailto:refond.g...@gmail.com]
> S
Thanks,
Sailaja.M
-Original Message-
From: Tejas Gadaria [mailto:refond.g...@gmail.com]
Sent: 27 February 2014 10:35
To: users@cloudstack.apache.org
Subject: Re: Unable to deploy vm
Hi,
thanks for replay,
Is there any workaround for this
Please follow the instructions given at : [1] to upgrade from 4.0.x to 4.1.0:
[1]:
http://svn.apache.org/repos/asf/cloudstack/docsite/html/docs/en-US/Apache_CloudStack/4.1.0/html/Release_Notes/upgrade-instructions.html#upgrade-from-4.0-to-4.1
Thanks,
Sanjeev
-Original Message-
From: Teja
Hi,
thanks for replay,
Is there any workaround for this ?
OR
how can I update 4.0.2 to 4.1.0 ?
Regards,
Tejas
On Wed, Feb 26, 2014 at 2:55 PM, Sailaja Mada wrote:
> Hi,
>
> Error log seems to be same as the bug @
> https://issues.apache.org/jira/browse/CLOUDSTACK-1403 - This got fixed in
> 4.1
Hi,
Error log seems to be same as the bug @
https://issues.apache.org/jira/browse/CLOUDSTACK-1403 - This got fixed in 4.1.0
.
Thanks,
Sailaja.M
-Original Message-
From: Tejas Gadaria [mailto:refond.g...@gmail.com]
Sent: 26 February 2014 13:21
To: users@cloudstack.apache.org
Subject:
On 01.11.2013 08:33, Geoff Higginbottom wrote:
Just so you know, zone wide primary storage is not currently
supported by XenServer, that's why you had to add a dedicated primary
storage for your XenServer Cluster.
Oh, ok, thanks for that! I was getting confused with this zone-wide
primary stor
Just so you know, zone wide primary storage is not currently supported by
XenServer, that's why you had to add a dedicated primary storage for your
XenServer Cluster.
Regards
Geoff Higginbottom
CTO / Cloud Architect
D: +44 20 3603 0542 | S: +44 20 3603 0540
| M: +447968161581
geoff.higginbo
On 01.11.2013 00:22, Eric Tykwinski wrote:
It looks like you didn't assign the primary storage to Xen.
013-10-31 23:57:36,080 DEBUG
[storage.allocator.ClusterScopeStoragePoolAllocator]
(Job-Executor-3:job-28 = [ b52e0a27-9f1c-4e15-aef6-0e758333b2e3 ]) No
storage pools available for shared volume
It looks like you didn't assign the primary storage to Xen.
013-10-31 23:57:36,080 DEBUG
[storage.allocator.ClusterScopeStoragePoolAllocator] (Job-Executor-3:job-28 = [
b52e0a27-9f1c-4e15-aef6-0e758333b2e3 ]) No storage pools available for shared
volume allocation, returning
Sincerely,
Eric T
14 matches
Mail list logo
