,
Devdeep
On Mon, Nov 16, 2015 at 10:25 AM, Amir Abbasi wrote:
> Hello,
>
> Disk Total on old Primary Storage is 2.8T and new one is 2T (over
> provisioning factor is 2). Currently Disk Allocated is only 5G on second
> storage but old one hast 2.5T Disk Allocated.
>
>
would require new apis for disabling/enabling storage pool.
Thoughts, comments?
Regards,
Devdeep
> -Original Message-
> From: Mike Tutkowski [mailto:[email protected]]
> Sent: Monday, February 23, 2015 3:48 AM
> To: [email protected]
> Cc: [email protected]
If a storage pool is put in disabled state then it will not be picked up as a
possible destination when a volume is being migrated or when a virtual machine
is being migrated along with its volumes.
Regards,
Devdeep
> -Original Message-
> From: Mike Tutkowski [mailto:mike.
for hyper-v you'll have to
create a separate zone in which hyper-v is the only hypervisor. For a hyper-v
zone; you'll have to register a secondary storage of type SMB.
Regards,
Devdeep
> -Original Message-
> From: Tejas Gadaria [mailto:[email protected]]
> Sent
Hi Tejas,
It should work but I would recommend that you seed the vmware systemvm template
too on the secondary storage.
Regards,
Devdeep
> -Original Message-
> From: Tejas Gadaria [mailto:[email protected]]
> Sent: Tuesday, April 22, 2014 3:05 PM
> To: users@cloudstac
Which hypervisor are you working with? Have you seeded the secondary storage
with the systemvm template for the hypervisor?
Regards,
Devdeep
> -Original Message-
> From: Amin Pashapour [mailto:[email protected]]
> Sent: Tuesday, May 13, 2014 1:05 AM
> To: users@cloudstac
cloudstack logs when
you try and list the hosts for migration from the UI?
Regards,
Devdeep
> -Original Message-
> From: Amin Samir [mailto:[email protected]]
> Sent: Friday, May 23, 2014 8:12 AM
> To: [email protected]
> Subject: VM's using custom offerings
Hi Amin,
Right now I am not sure as to why the issue is there. If I get a chance, I'll
give it a try and let you know if I find something.
Regards,
Devdeep
> -Original Message-
> From: Amin Samir [mailto:[email protected]]
> Sent: Tuesday, May 27, 2014 2:36
Hi Amin,
I can reproduce the problem; the stack trace is similar to what Prashant
pointed to. Do confirm you are seeing a similar stack trace in your logs and
file a bug for the same. I'll submit a fix for the problem.
Regards,
Devdeep
> -Original Message-
> From: Amin Sami
Just to confirm, are you using XenServer 6.2 or XenServer 6.2 SP1?
Regards,
Devdeep
> -Original Message-
> From: Vijay Ramadoss [mailto:[email protected]]
> Sent: Wednesday, June 18, 2014 10:01 AM
> To: [email protected]
> Subject: Re: Cloudstack/Xenser
From the FS [1], under Interoperability and compatibility, it is supported for
6.2 SP1 and later.
[1]
https://cwiki.apache.org/confluence/display/CLOUDSTACK/GPU+and+vGPU+support+for+CloudStack+Guest+VMs
Regards,
Devdeep
> -Original Message-
> From: Vijay Ramadoss [mailto:
Sanjay can correct me if I am wrong, but looks like a different resource gets
loaded for XenServer 6.2 and XenServer 6.2 SP1. So if you are using 6.2 ,
cloudstack will not query the host for GPU details.
Regards,
Devdeep
> -Original Message-
> From: Vijay Ramadoss [mailto:
Hi Amir,
Can you share some more logs of the management server? It looks like management
server isn't able to connect to the host; but we'll have to look at rest of the
logs to root cause the issue. What hypervisor are you working with?
Regards,
Devdeep
> -Original Messag
This looks like a bug in 4.2.1. Can you elaborate more on the operation tried?
Were you trying to migrate a volume (data disk) that was detached from a
instance/vm to another storage pool?
Regards,
Devdeep
-Original Message-
From: Pierre-Luc Dion [mailto:[email protected]]
Sent
14 matches
Mail list logo
