RE: Error: "Unable to add host"

[Pavan Bandarupally]

What did the lsmod | grep kvm output after enabling virtualization ? Did it 
show kvm_intel this time ? If it hasn't can you try installing kvm-qemu package 
and give it a try ? 

-Original Message-
From: Cayetano Rodríguez [mailto:tfg.cloudcomput...@gmail.com] 
Sent: Thursday, April 21, 2016 11:56 PM
To: users@cloudstack.apache.org
Subject: Re: Error: "Unable to add host"

It wasn't enabled but I enabled the virtualization in the BIOS and I still 
can't add a host

El lunes, 18 de abril de 2016, Pavan Bandarupally < 
pavan.bandarupa...@accelerite.com> escribió:

> Is Virtualization enabled in the BIOS for the machine ?
>
> -Original Message-
> From: Cayetano Rodríguez [mailto:tfg.cloudcomput...@gmail.com
> ]
> Sent: Friday, April 15, 2016 8:05 PM
> To: users@cloudstack.apache.org 
> Subject: Re: Error: "Unable to add host"
>
> Yes, I'm trying to setup everything on a single machine. I followed 
> that guide and now I've checked all steps in the KVM section. When I execute  
> "
> lsmod | grep kvm "
>  I get the following output:
> [root@srvr1 ~]# lsmod | grep kvm
> kvm   341551  0
>
> In the guide it appears in the output another line (kvm_intel), am I 
> doing something wrong so that line doesn't appear?
>
> Thank you
>
> 2016-04-15 4:06 GMT+02:00 Pavan Bandarupally < 
> pavan.bandarupa...@accelerite.com >:
>
> > If you have resources, it is recommended to have management server 
> > and host on separate machines. But just to troubleshoot your 
> > environment you can check the below link and see if things work.
> >
> > From my understanding you are trying to setup everything ( 
> > management server and hotst) on a single machine. The error you face 
> > is generally seen if the hypervisor host doesn't have KVM agent 
> > installed properly (I might be wrong here). Can you please go 
> > through the below link and make sure that you have followed all the 
> > required steps (for KVM installation ) and confirm if KVM is 
> > properly installed (say by checking
> lsmod | grep kvm ) ?
> >
> >
> > http://docs.cloudstack.apache.org/projects/cloudstack-installation/e
> > n/
> > 4.6/qig.html
> >
> > Regards,
> > Pavan
> >
> >
> > -Original Message-
> > From: Cayetano Rodríguez [mailto:tfg.cloudcomput...@gmail.com
> ]
> > Sent: Friday, April 15, 2016 6:08 AM
> > To: users@cloudstack.apache.org 
> > Subject: Re: Error: "Unable to add host"
> >
> > The managenent ip address is the same as the host ip address, and 
> > the same as the machine that I'm using...
> > I've done this because I've followed the Quick Installation Guide 
> > that is focused on doing everything in the same machine, and this 
> > guide specifies to use the same ip addresses in managenent server 
> > and the
> first host.
> >
> > I am interested in getting started on CloudStack doing this "trial"
> > installation, so I don't need lots of resources (and actually don't 
> > have them at this moment). For this reason I think doing everything 
> > in the same machine is the best option for me.
> >
> > If you could help me doing this that would be great, or if it's not 
> > possible and you think it's better and easier separating the 
> > management server and host, I could look for another machine to use.
> >
> > Thank you very much.
> >
> > El jueves, 14 de abril de 2016, Simon Weller  > escribió:
> >
> > > Can you ping the ip address you supplied from the management server?
> > > Are you able to ssh into it using the credentials (from the 
> > > management
> > > server) you're using in the Cloudstack GUI?
> > >
> > > ICloudstack is really designed to be deployed on separate servers, 
> > > so mixing management and hosts can complicate things a fair bit.
> > >
> > > - Si
> > >
> > >
> > > 
> > > From: Cayetano Rodríguez  > >  >
> > > Sent: Thursday, April 14, 2016 12:18 PM
> > > To: users@cloudstack.apache.org  
> > > Subject: Error: "Unable to add host"
> > >
> > > Hi everyone!
> > >
> > > I've followed the "Quick Installation Guide for Centos 6" guide, 
> > > to install CloudStack in one machine with Centos 6.5. I've 
> > > followed all steps and finished installing, but I get an error 
> > > while configuring it. The

RE: problem with vm volume resize

[Pavan Bandarupally]

I think Root disk resize is supported only on KVM as per the FS 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Root+Resize+Support


-Original Message-
From: ilya [mailto:ilya.mailing.li...@gmail.com]
Sent: Wednesday, April 20, 2016 11:23 AM
To: users@cloudstack.apache.org
Subject: Re: problem with vm volume resize

device 0 implies root disk..

On 4/19/16 9:26 PM, Simon Weller wrote:
> Chris,
>
> Device 0, if I'm not mistaken, normally refers to the root volume. Have you 
> tried this via the api directly, or via cloudmonkey to eliminate the ui?
>
> - Si
>
> Simon Weller/ENA
> (615) 312-6068
>
> -Original Message-
> From: Chris Chupela [cchup...@dsscorp.com]
> Received: Tuesday, 19 Apr 2016, 10:57PM
> To: users@cloudstack.apache.org [users@cloudstack.apache.org]
> Subject: problem with vm volume resize
>
> I have a cloudstack 4.2 installation with vmware 5.0 as the underlying 
> hypervisor. I've resized volumes in the past using the web UI, but have run 
> into an issue where my resize attempt on an existing win2k8 data volume 
> failed. It is a resize from 50Gb to 100Gb, and I have enough storage to do 
> the resize.
>
> When I attempt the resize, the UI returns 'unable to resize volume', and I 
> find the following error in the management server log:
>
> 2016-04-19 22:52:45,468 ERROR [vmware.resource.VmwareResource] 
> (DirectAgent-88:wyo1-p1-c1-hv5.dsscorp.com, job-641, cmd: 
> ResizeVolumeCommand) Unable to resize volume
> java.lang.RuntimeException: Invalid operation for device '0'.
> at 
> com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:413)
> at 
> com.cloud.hypervisor.vmware.mo.VirtualMachineMO.configureVm(VirtualMachineMO.java:862)
> at 
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:691)
> at 
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:572)
> at 
> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
> at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
> at java.util.concurrent.FutureTask.run(Unknown Source)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown
>  Source)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown
>  Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown 
> Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
>
> The vm in question has been in the cloud enviornment/production for 2+ years. 
> It has a root volume, and 3 data volumes. I'm trying to resize the first data 
> volume.
>
> I've seen some mention of issues like this with resizing volumes that were 
> created from snapshots, but that doesn't apply here.
>
> Any thoughts on why my resize attempt is failing?
>
> Chris Chupela
> Systems Engineer
> DSS
> 610.927.2031 Office
> 610.334.2392 Cell
>
> Website | Data Center 
> | Twitter | 
> Facebook
>
>



DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Accelerite, a Persistent Systems business. It is intended only for 
the use of the individual or entity to which it is addressed. If you are not 
the intended recipient, you are not authorized to read, retain, copy, print, 
distribute or use this message. If you have received this communication in 
error, please notify the sender and delete all copies of this message. 
Accelerite, a Persistent Systems business does not accept any liability for 
virus infected mails.

RE: Error: "Unable to add host"

[Pavan Bandarupally]

Is Virtualization enabled in the BIOS for the machine ?

-Original Message-
From: Cayetano Rodríguez [mailto:tfg.cloudcomput...@gmail.com] 
Sent: Friday, April 15, 2016 8:05 PM
To: users@cloudstack.apache.org
Subject: Re: Error: "Unable to add host"

Yes, I'm trying to setup everything on a single machine. I followed that guide 
and now I've checked all steps in the KVM section. When I execute  "
lsmod | grep kvm "
 I get the following output:
[root@srvr1 ~]# lsmod | grep kvm
kvm   341551  0

In the guide it appears in the output another line (kvm_intel), am I doing 
something wrong so that line doesn't appear?

Thank you

2016-04-15 4:06 GMT+02:00 Pavan Bandarupally <
pavan.bandarupa...@accelerite.com>:

> If you have resources, it is recommended to have management server and 
> host on separate machines. But just to troubleshoot your environment 
> you can check the below link and see if things work.
>
> From my understanding you are trying to setup everything ( management 
> server and hotst) on a single machine. The error you face is generally 
> seen if the hypervisor host doesn't have KVM agent installed properly 
> (I might be wrong here). Can you please go through the below link and 
> make sure that you have followed all the required steps (for KVM 
> installation ) and confirm if KVM is properly installed (say by checking 
> lsmod | grep kvm ) ?
>
>
> http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/
> 4.6/qig.html
>
> Regards,
> Pavan
>
>
> -Original Message-
> From: Cayetano Rodríguez [mailto:tfg.cloudcomput...@gmail.com]
> Sent: Friday, April 15, 2016 6:08 AM
> To: users@cloudstack.apache.org
> Subject: Re: Error: "Unable to add host"
>
> The managenent ip address is the same as the host ip address, and the 
> same as the machine that I'm using...
> I've done this because I've followed the Quick Installation Guide that 
> is focused on doing everything in the same machine, and this guide 
> specifies to use the same ip addresses in managenent server and the first 
> host.
>
> I am interested in getting started on CloudStack doing this "trial"
> installation, so I don't need lots of resources (and actually don't 
> have them at this moment). For this reason I think doing everything in 
> the same machine is the best option for me.
>
> If you could help me doing this that would be great, or if it's not 
> possible and you think it's better and easier separating the 
> management server and host, I could look for another machine to use.
>
> Thank you very much.
>
> El jueves, 14 de abril de 2016, Simon Weller  escribió:
>
> > Can you ping the ip address you supplied from the management server?
> > Are you able to ssh into it using the credentials (from the 
> > management
> > server) you're using in the Cloudstack GUI?
> >
> > ICloudstack is really designed to be deployed on separate servers, 
> > so mixing management and hosts can complicate things a fair bit.
> >
> > - Si
> >
> >
> > 
> > From: Cayetano Rodríguez  > >
> > Sent: Thursday, April 14, 2016 12:18 PM
> > To: users@cloudstack.apache.org 
> > Subject: Error: "Unable to add host"
> >
> > Hi everyone!
> >
> > I've followed the "Quick Installation Guide for Centos 6" guide, to 
> > install CloudStack in one machine with Centos 6.5. I've followed all 
> > steps and finished installing, but I get an error while configuring 
> > it. The error appears when CloudStack is trying to add a host. The 
> > error says: "Unable to add the host".
> >
> > I've checked /var/log/cloudstack/management/management-server.log 
> > and this is the complete error:
> >
> >
> >
> > 2016-04-14 19:10:36,257 DEBUG [c.c.a.ApiServlet]
> > (catalina-exec-1:ctx-3c617426) (logid:25f4748e) ===START===
> > 192.168.1.2 -- GET
> >
> > command=listNetworkOfferings&state=Enabled&guestiptype=Shared&respon
> > se
> > =json&_=1460653836254
> > 2016-04-14 19:10:36,315 DEBUG [c.c.a.ApiServlet]
> > (catalina-exec-1:ctx-3c617426 ctx-5090361b) (logid:25f4748e) 
> > ===END===
> > 192.168.1.2 -- GET
> >
> > command=listNetworkOfferings&state=Enabled&guestiptype=Shared&respon
> > se
> > =json&_=1460653836254
> > 2016-04-14 19:10:36,323 DEBUG [c.c.a.ApiServlet]
> > (catalina-exec-14:ctx-8f5ed97e) (logid:30b82c99) ===START===
> > 192.168.1.2
> > -- POST  command=addHost&response=js

RE: Error: "Unable to add host"

[Pavan Bandarupally]

If you have resources, it is recommended to have management server and host on 
separate machines. But just to troubleshoot your environment you can check the 
below link and see if things work.

From my understanding you are trying to setup everything ( management server 
and hotst) on a single machine. The error you face is generally seen if the 
hypervisor host doesn't have KVM agent installed properly (I might be wrong 
here). Can you please go through the below link and make sure that you have 
followed all the required steps (for KVM installation ) and confirm if KVM is 
properly installed (say by checking lsmod | grep kvm ) ? 

http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/4.6/qig.html

Regards,
Pavan


-Original Message-
From: Cayetano Rodríguez [mailto:tfg.cloudcomput...@gmail.com] 
Sent: Friday, April 15, 2016 6:08 AM
To: users@cloudstack.apache.org
Subject: Re: Error: "Unable to add host"

The managenent ip address is the same as the host ip address, and the same as 
the machine that I'm using...
I've done this because I've followed the Quick Installation Guide that is 
focused on doing everything in the same machine, and this guide specifies to 
use the same ip addresses in managenent server and the first host.

I am interested in getting started on CloudStack doing this "trial"
installation, so I don't need lots of resources (and actually don't have them 
at this moment). For this reason I think doing everything in the same machine 
is the best option for me.

If you could help me doing this that would be great, or if it's not possible 
and you think it's better and easier separating the management server and host, 
I could look for another machine to use.

Thank you very much.

El jueves, 14 de abril de 2016, Simon Weller  escribió:

> Can you ping the ip address you supplied from the management server? 
> Are you able to ssh into it using the credentials (from the management 
> server) you're using in the Cloudstack GUI?
>
> ICloudstack is really designed to be deployed on separate servers, so 
> mixing management and hosts can complicate things a fair bit.
>
> - Si
>
>
> 
> From: Cayetano Rodríguez >
> Sent: Thursday, April 14, 2016 12:18 PM
> To: users@cloudstack.apache.org 
> Subject: Error: "Unable to add host"
>
> Hi everyone!
>
> I've followed the "Quick Installation Guide for Centos 6" guide, to 
> install CloudStack in one machine with Centos 6.5. I've followed all 
> steps and finished installing, but I get an error while configuring 
> it. The error appears when CloudStack is trying to add a host. The 
> error says: "Unable to add the host".
>
> I've checked /var/log/cloudstack/management/management-server.log and 
> this is the complete error:
>
>
>
> 2016-04-14 19:10:36,257 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-1:ctx-3c617426) (logid:25f4748e) ===START===  
> 192.168.1.2 -- GET
>
> command=listNetworkOfferings&state=Enabled&guestiptype=Shared&response
> =json&_=1460653836254
> 2016-04-14 19:10:36,315 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-1:ctx-3c617426 ctx-5090361b) (logid:25f4748e) ===END===
> 192.168.1.2 -- GET
>
> command=listNetworkOfferings&state=Enabled&guestiptype=Shared&response
> =json&_=1460653836254
> 2016-04-14 19:10:36,323 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-14:ctx-8f5ed97e) (logid:30b82c99) ===START===  
> 192.168.1.2
> -- POST  command=addHost&response=json
> 2016-04-14 19:10:36,335 WARN  [c.c.a.d.ParamGenericValidationWorker]
> (catalina-exec-14:ctx-8f5ed97e ctx-8c36d11e) (logid:30b82c99) Received 
> unknown parameters for command addHost. Unknown parameters : 
> clustertype
> 2016-04-14 19:10:36,339 INFO  [c.c.r.ResourceManagerImpl] 
> (catalina-exec-14:ctx-8f5ed97e ctx-8c36d11e) (logid:30b82c99) Trying 
> to add a new host at http://192.168.1.2 in data center 1
> 2016-04-14 19:10:36,343 WARN  [c.c.h.k.d.LibvirtServerDiscoverer]
> (catalina-exec-14:ctx-8f5ed97e ctx-8c36d11e) (logid:30b82c99)  can't 
> setup agent, due to java.io.IOException: There was a problem while 
> connecting to
> 192.168.1.2:22 - There was a problem while connecting to 
> 192.168.1.2:22
> 2016-04-14 19:10:36,343 WARN  [c.c.r.ResourceManagerImpl] 
> (catalina-exec-14:ctx-8f5ed97e ctx-8c36d11e) (logid:30b82c99) Unable 
> to find the server resources at http://192.168.1.2
> 2016-04-14 19:10:36,343 INFO  [c.c.u.e.CSExceptionErrorCode] 
> (catalina-exec-14:ctx-8f5ed97e ctx-8c36d11e) (logid:30b82c99) Could 
> not find exception: com.cloud.exception.DiscoveryException in error 
> code list for exceptions
> 2016-04-14 19:10:36,343 WARN  [o.a.c.a.c.a.h.AddHostCmd] 
> (catalina-exec-14:ctx-8f5ed97e ctx-8c36d11e) (logid:30b82c99) Exception:
> com.cloud.exception.DiscoveryException: Unable to add the host
> at
>
> com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:802)
> at
>
> com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:597)
> at sun.reflect

RE: No such file or directory ( ACS 4.8

[Pavan Bandarupally]

Hi Cristian,

Is the SystemVM template seeded properly ? Is the routing-8 template present in 
the secondary store (templates/tmpl/1/8 )? If Yes then please check permissions 
as mentioned below.

Can you just check the permissions for the templates folder in secondary store. 
It should 777 for VmWare hypervisor. If they are different then please try to 
give 777 permissions to templates folder recursively and give it a try.

Regards,
Pavan

-Original Message-
From: Cristian Ciobanu [mailto:cristian.c@istream.today]
Sent: Monday, April 11, 2016 1:06 AM
To: users@cloudstack.apache.org
Subject: No such file or directory ( ACS 4.8

Hello All,



   I just installed a new ACS 4.8 with Vmware, but i'm not sure why i get 
"No such file or directory"  non of the system templates were created.



  Any idea  ?





2016-04-10 15:21:38,409 DEBUG [c.c.a.t.Request] 
(Work-Job-Executor-129:ctx-1b73f17d job-7/job-475 ctx-7e3fc4f3)
(logid:e1225ee9) Seq 1-887772076545409129: Sending  { Cmd , MgmtId:
345048635511, via: 1(ns327063.ip-xxx-xxx-xxx.eu), Ver: v1, Flags: 100111, 
[{"org.apache.cloudstack.storage.command.CopyCommand":{"srcTO":{"org.apache.
cloudstack.storage.to.TemplateObjectTO":{"path":"template/tmpl/1/8/","origUr
l":"http://cloudstack.apt-get.eu/systemvm/4.6/systemvm64template-4.6.0-vmwar
e.ova","uuid":"2f6c6960-e60c-11e5-91fb-005056805877","id":8,"format":"OVA","
accountId":1,"checksum":"4b415224fe00b258f66cad9fce9f73fc","hvm":false,"disp
layText":"SystemVM Template
(vSphere)","imageDataStore":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://1
72.11.11.2/secondary","_role":"Image"}},"name":"routing-8","hypervisorType":
"VMware"}},"destTO":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"o
rigUrl":"http://cloudstack.apt-get.eu/systemvm/4.6/systemvm64template-4.6.0-
vmware.ova","uuid":"2f6c6960-e60c-11e5-91fb-005056805877","id":8,"format":"O
VA","accountId":1,"checksum":"4b415224fe00b258f66cad9fce9f73fc","hvm":false,
"displayText":"SystemVM Template
(vSphere)","imageDataStore":{"org.apache.cloudstack.storage.to.PrimaryDataSt
oreTO":{"uuid":"a0e3b41b-4c99-4972-8985-618d94a92d1f","id":1,"poolType":"VMF
S","host":"VMFS datastore:
datastore-29","path":"datastore-29","port":0,"url":"VMFS://VMFS datastore:
datastore-29/datastore-29/?ROLE=Primary&STOREUUID=a0e3b41b-4c99-4972-8985-61
8d94a92d1f"}},"name":"routing-8","hypervisorType":"VMware"}},"executeInSeque
nce":true,"options":{},"options2":{},"wait":10800}}] }

2016-04-10 15:21:38,409 DEBUG [c.c.a.t.Request] 
(Work-Job-Executor-129:ctx-1b73f17d job-7/job-475 ctx-7e3fc4f3)
(logid:e1225ee9) Seq 1-887772076545409129: Executing:  { Cmd , MgmtId:
345048635511, via: 1(ns327063.ip-xxx-xxx-xxx.eu), Ver: v1, Flags: 100111, 
[{"org.apache.cloudstack.storage.command.CopyCommand":{"srcTO":{"org.apache.
cloudstack.storage.to.TemplateObjectTO":{"path":"template/tmpl/1/8/","origUr
l":"http://cloudstack.apt-get.eu/systemvm/4.6/systemvm64template-4.6.0-vmwar
e.ova","uuid":"2f6c6960-e60c-11e5-91fb-005056805877","id":8,"format":"OVA","
accountId":1,"checksum":"4b415224fe00b258f66cad9fce9f73fc","hvm":false,"disp
layText":"SystemVM Template
(vSphere)","imageDataStore":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://1
72.11.11.2/secondary","_role":"Image"}},"name":"routing-8","hypervisorType":
"VMware"}},"destTO":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"o
rigUrl":"http://cloudstack.apt-get.eu/systemvm/4.6/systemvm64template-4.6.0-
vmware.ova","uuid":"2f6c6960-e60c-11e5-91fb-005056805877","id":8,"format":"O
VA","accountId":1,"checksum":"4b415224fe00b258f66cad9fce9f73fc","hvm":false,
"displayText":"SystemVM Template
(vSphere)","imageDataStore":{"org.apache.cloudstack.storage.to.PrimaryDataSt
oreTO":{"uuid":"a0e3b41b-4c99-4972-8985-618d94a92d1f","id":1,"poolType":"VMF
S","host":"VMFS datastore:
datastore-29","path":"datastore-29","port":0,"url":"VMFS://VMFS datastore:
datastore-29/datastore-29/?ROLE=Primary&STOREUUID=a0e3b41b-4c99-4972-8985-61
8d94a92d1f"}},"name":"routing-8","hypervisorType":"VMware"}},"executeInSeque
nce":true,"options":{},"options2":{},"wait":10800}}] }

2016-04-10 15:21:38,409 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-168:ctx-af26db25) (logid:e9d7408e) Seq 1-887772076545409129:
Executing request

2016-04-10 15:21:38,429 INFO  [c.c.s.r.VmwareStorageProcessor]
(DirectAgent-168:ctx-af26db25 ns327063.ip-xxx-xxx-xxx.eu, job-7/job-475,
cmd: CopyCommand) (logid:e1225ee9) Template routing-8 is not setup yet. Set up 
template from secondary storage with uuid name:
dfe4d12702053b96bfa64e5a392c640c

2016-04-10 15:21:38,443 INFO  [c.c.s.r.VmwareStorageProcessor]
(DirectAgent-168:ctx-af26db25 ns327063.ip-xxx-xxx-xxx.eu, job-7/job-475,
cmd: CopyCommand) (logid:e1225ee9) Executing 
copyTemplateFromSecondaryToPrimary. secondaryStorage:
nfs://172.11.11.2/secondary, templatePathAtSecondaryStorage:
template/tmpl/1/8/, templateName: routing-8

2016-04-10 15:21:38,443 INFO  [c.c.s.r.VmwareStorageProcessor]
(DirectAgent-168:ctx-af26db25 ns327063.ip-xxx-

RE: Error resize volumen

[Pavan Bandarupally]

If it is data disk then it should be supported in VmWare (only increase of disk 
size is supported on VmWare). But there is a little caveat involved in VmWare 
data disk resize. It will not be dynamically reflected inside the guest OS if 
it is windows. I am not sure if your CS UI is showing the increased size after 
resize ? 

Say you have increased the size from 20 GB to 30 GB and the disk size, in UI 
data disk size has changed to 30 GB but not in the guest OS, then you have to 
go to disk management in windows and create the partition. You will see the 
extra 10 GB as unallocated disk, which you should be able to format and then 
see the disk partition inside the OS.

If you haven't seen the increased size in UI itself then that must be an issue 
in disk resize. Since you are using 4.3.0 this feature should work in that 
release.

Here is the FS for data disk resize: 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Resize+Data+Volumes 

Regards,
Pavan

-Original Message-
From: Yesid Mora [mailto:ym...@o4it.com] 
Sent: Wednesday, April 06, 2016 10:37 PM
To: users@cloudstack.apache.org
Subject: RE: Error resize volumen

Hello Pavan, the volume to resize is data 

Thanks,

-Original Message-
From: Pavan Bandarupally [mailto:pavan.bandarupa...@accelerite.com] 
Sent: Tuesday, April 05, 2016 11:08 PM
To: users@cloudstack.apache.org
Subject: RE: Error resize volumen

Hi Yesid,

Is this a root disk or data disk that you are trying to resize ? If it is Root 
disk resize, I guess it is not supported on VmWare.

https://cwiki.apache.org/confluence/display/CLOUDSTACK/Root+Resize+Support

Regards,
Pavan

From: Yesid Mora [mailto:ym...@o4it.com]
Sent: Wednesday, April 06, 2016 1:38 AM
To: users@cloudstack.apache.org
Subject: RE: Error resize volumen


Hello thanks for your comments, confirm that the storage controller is SCSI and 
LSI Logic SAS, the VM not have snapshot and check in vmware and the ability to 
resize is available to change, the version in Cloudstack is 4.3.0 the error is:



2016-04-05 10:52:41,826 DEBUG [c.c.u.AccountManagerImpl] 
(catalina-exec-2:ctx-a7997fc0 ctx-9eb2a31d) Access to 
Acct[07224ecd-35fd-41d2-92e8-1121918df2bf-usercsn] granted to 
Acct[07224ecd-35fd-41d2-92e8-1121918df2bf-usercsn] by DomainChecker

2016-04-05 10:52:41,840 DEBUG [c.c.a.ApiServlet] (catalina-exec-2:ctx-a7997fc0 
ctx-9eb2a31d) ===END===  10.109.3.37 -- GET  
jobId=028aae74-c300-419f-97e6-5d89319d7b12&tenantParam=f045cb13-5183-4830-bb0a-730b2979feb2&response=json&command=queryAsyncJobResult&_=1459871459748&sessionkey=gsICkPB2ddq5%2FJTL%2BGncBcj3cag%3D&jSessionId=37502B148DB676C1B50A9D7346166E24

2016-04-05 10:52:42,205 ERROR [c.c.h.v.r.VmwareResource] 
(DirectAgent-391:ctx-71b1f981 miatmcplathost01.corp.local) Unable to resize 
volume

java.lang.RuntimeException: A specified parameter was not correct.



at 
com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:336)

at 
com.cloud.hypervisor.vmware.mo.VirtualMachineMO.configureVm(VirtualMachineMO.java:922)

at 
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:680)

at 
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:594)

at 
com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:215)

at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:50)

at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)

at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)

at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)

at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:47)

at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)

at java.util.concurrent.FutureTask.run(FutureTask.java:262)

at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)

at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)

at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

at java.lang.Thread.run(Thread.java:745)

2016-04-05 10:52:42,206 DEBUG [c.c.a.m.DirectAgentAttache] 
(DirectAgent-391:ctx-71b1f981) Seq 3279-1872975942: Response Received:

2016-04-05 10:52:42,206 DEBUG [c.c.a.m.ClusteredAgentManagerImpl] 
(DirectAgent-391:ctx-71b1f981) Seq 3279-1872975942: MgmtId 345048626012: Resp: 
Routing to peer

2016-04-05 10:52:42,620 ERROR [c.c.a.ApiAsyncJobDispatcher] 
(API-Job-Execut

RE: Error resize volumen

[Pavan Bandarupally]

Hi Yesid,

Is this a root disk or data disk that you are trying to resize ? If it is Root 
disk resize, I guess it is not supported on VmWare.

https://cwiki.apache.org/confluence/display/CLOUDSTACK/Root+Resize+Support

Regards,
Pavan

From: Yesid Mora [mailto:ym...@o4it.com]
Sent: Wednesday, April 06, 2016 1:38 AM
To: users@cloudstack.apache.org
Subject: RE: Error resize volumen


Hello thanks for your comments, confirm that the storage controller is SCSI and 
LSI Logic SAS, the VM not have snapshot and check in vmware and the ability to 
resize is available to change, the version in Cloudstack is 4.3.0 the error is:



2016-04-05 10:52:41,826 DEBUG [c.c.u.AccountManagerImpl] 
(catalina-exec-2:ctx-a7997fc0 ctx-9eb2a31d) Access to 
Acct[07224ecd-35fd-41d2-92e8-1121918df2bf-usercsn] granted to 
Acct[07224ecd-35fd-41d2-92e8-1121918df2bf-usercsn] by DomainChecker

2016-04-05 10:52:41,840 DEBUG [c.c.a.ApiServlet] (catalina-exec-2:ctx-a7997fc0 
ctx-9eb2a31d) ===END===  10.109.3.37 -- GET  
jobId=028aae74-c300-419f-97e6-5d89319d7b12&tenantParam=f045cb13-5183-4830-bb0a-730b2979feb2&response=json&command=queryAsyncJobResult&_=1459871459748&sessionkey=gsICkPB2ddq5%2FJTL%2BGncBcj3cag%3D&jSessionId=37502B148DB676C1B50A9D7346166E24

2016-04-05 10:52:42,205 ERROR [c.c.h.v.r.VmwareResource] 
(DirectAgent-391:ctx-71b1f981 miatmcplathost01.corp.local) Unable to resize 
volume

java.lang.RuntimeException: A specified parameter was not correct.



at 
com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:336)

at 
com.cloud.hypervisor.vmware.mo.VirtualMachineMO.configureVm(VirtualMachineMO.java:922)

at 
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:680)

at 
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:594)

at 
com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:215)

at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:50)

at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)

at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)

at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)

at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:47)

at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)

at java.util.concurrent.FutureTask.run(FutureTask.java:262)

at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)

at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)

at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

at java.lang.Thread.run(Thread.java:745)

2016-04-05 10:52:42,206 DEBUG [c.c.a.m.DirectAgentAttache] 
(DirectAgent-391:ctx-71b1f981) Seq 3279-1872975942: Response Received:

2016-04-05 10:52:42,206 DEBUG [c.c.a.m.ClusteredAgentManagerImpl] 
(DirectAgent-391:ctx-71b1f981) Seq 3279-1872975942: MgmtId 345048626012: Resp: 
Routing to peer

2016-04-05 10:52:42,620 ERROR [c.c.a.ApiAsyncJobDispatcher] 
(API-Job-Executor-107:ctx-9a0297db job-14058) Unexpected exception while 
executing org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd

java.lang.RuntimeException: Unexpected exception

at 
com.cloud.storage.VolumeApiServiceImpl.resizeVolume(VolumeApiServiceImpl.java:950)

at 
com.cloud.storage.VolumeApiServiceImpl.resizeVolume(VolumeApiServiceImpl.java:178)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

   at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)

at 
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)

at 
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)

at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)

at 
com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50)

at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)

at 
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)

at 
org.springframework.aop.framework.ReflectiveMethodI

RE: snapshot cleanup on hypervisor primary storage

[Pavan Bandarupally]

Hi Swen,

Cloud Stack just hands over the snapshot operation to XenServer via XenServer 
commands. As mentioned earlier if the volume (VDI/VBD) is deleted all the 
associated snapshots will be cleaned up by Xenserver.

My assumption here is that the volume that you have deleted from cloud stack is 
not deleted in the XenServer and hence the snapshots are not getting deleted ? 
Can you please check on XenServer if the VDI chain (for the deleted volume) is 
still present in the SR ?

I am not exactly aware of any changes in functionality from 4.5.1 but you can 
try one thing to isolate if the issue is with CS version or XenServer. Can you 
please create a standalone VM on Xenserver and take a snapshot of the VDI ? 
Delete the VDI and check if the snapshots are getting deleted ?

Regards,
Pavan
-Original Message-
From: S. Brüseke - proIO GmbH [mailto:s.brues...@proio.com]
Sent: Tuesday, April 05, 2016 4:54 PM
To: Pavan Bandarupally; users@cloudstack.apache.org
Subject: AW: snapshot cleanup on hypervisor primary storage

Hi Pavan,

XenServer is not deleting the snapshots even after do a rescan:

Apr  5 13:20:59 cp-test-xs-2 SMGC: [24074] No work, exiting Apr  5 13:20:59 
cp-test-xs-2 SMGC: [24074] In cleanup

I am really not sure why he should do it in first place. Can you please tell me 
more about it? Please have in mind that we are using CS 4.5.1 and not the 
newest version.

Mit freundlichen Grüßen / With kind regards,

Swen


-Ursprüngliche Nachricht-
Von: Pavan Bandarupally [mailto:pavan.bandarupa...@accelerite.com]
Gesendet: Dienstag, 5. April 2016 13:14
An: users@cloudstack.apache.org; S. Brüseke - proIO GmbH
Betreff: RE: snapshot cleanup on hypervisor primary storage

Hi Swen,

Yes , if you have deleted the volume, the snapshots of that volume should be 
cleaned from primary storage by Xenserver.

Can you please run sr scan and check if they are getting cleaned up (running sr 
scan will manually trigger the GC on Xenserver which should clean up these if 
GC is not run for some reason) ?

Regards,
Pavan
-Original Message-
From: S. Brüseke - proIO GmbH [mailto:s.brues...@proio.com]
Sent: Tuesday, April 05, 2016 4:05 PM
To: users@cloudstack.apache.org
Subject: AW: snapshot cleanup on hypervisor primary storage

Hi Pavan,

snapshots are working fine. Are you sure that snapshots on primary storage 
should be deleted?

I did some testing and observed the following:

First volume-snapshot of an instance
1. you create a volume-snapshot in CS UI 2. XenServer is taking a snapshot of 
the vm 3. XenServer is mounting secondary storage 4. XenServer is copying 
snapshot to secondary storage 5. XenServer is unmounting secondary storage

Second (or more) volume-snapshot of an instance 1. you create a volume-snapshot 
in CS UI 2. XenServer is taking a snapshot of the vm and uses the first 
snapshot as parent (you are unable to see this in XenCenter because the parent 
snapshot will be hidden) 3. XenServer is mounting secondary storage 4. 
XenServer is copying only delta of snapshot to secondary storage into the same 
directory as the first snapshot 5. XenServer is unmounting secondary storage


If you delete the a snapshot via XenCenter all following volume-snapshots are 
going to fail because of missing parent!

If you migrate vm to another XenServer host and create a volume-snapshot it 
will work. Reason for that is that CS is starting from the beginning here and 
handles this as a first snapshot. CS also uses a new folder on secondary 
storage for this volume-snapshot.

The last snapshot on XenServer will always be there, because CS needs it as 
parent for the next one and XenServer is creating a vhd chain.

The questions here are:
1. When I delete an instance is the snapshot on XenServer still needed?
I think now, it can be deleted even the volume-snapshot is still on secondary 
storage.

2. When I delete all volume-snapshots in CS UI of the snapshot-chain will CS 
delete the snapshots on XenServer?
As far as I can see, no.

3. Who is cleaning up the snapshots on XenServer's primary storage when you do 
a storage migration (normal and live) to another primary storage?
Right now, nobody is doing this and if you are using storage migration a lot 
(if you are using local storage you will do it a lot) than you end up with GBs 
of unwanted data on your primary storages.

Mit freundlichen Grüßen / With kind regards,

Swen


-Ursprüngliche Nachricht-
Von: Pavan Bandarupally [mailto:pavan.bandarupa...@accelerite.com]
Gesendet: Dienstag, 5. April 2016 11:17
An: users@cloudstack.apache.org; S. Brüseke - proIO GmbH
Betreff: RE: snapshot cleanup on hypervisor primary storage

Hi Swen,

I don't think this is expected. The snapshots should get cleaned from Primary 
Storage by XenServer. Can you please check if the snapshots are usable or 
corrupted ?

Regarding deletion of snapshots on expunging the VM is not expected, because we 
do keep the snapshots (in secondary store) for furthe

RE: snapshot cleanup on hypervisor primary storage

[Pavan Bandarupally]

Hi Swen,

Yes , if you have deleted the volume, the snapshots of that volume should be 
cleaned from primary storage by Xenserver.

Can you please run sr scan and check if they are getting cleaned up (running sr 
scan will manually trigger the GC on Xenserver which should clean up these if 
GC is not run for some reason) ?

Regards,
Pavan
-Original Message-
From: S. Brüseke - proIO GmbH [mailto:s.brues...@proio.com]
Sent: Tuesday, April 05, 2016 4:05 PM
To: users@cloudstack.apache.org
Subject: AW: snapshot cleanup on hypervisor primary storage

Hi Pavan,

snapshots are working fine. Are you sure that snapshots on primary storage 
should be deleted?

I did some testing and observed the following:

First volume-snapshot of an instance
1. you create a volume-snapshot in CS UI 2. XenServer is taking a snapshot of 
the vm 3. XenServer is mounting secondary storage 4. XenServer is copying 
snapshot to secondary storage 5. XenServer is unmounting secondary storage

Second (or more) volume-snapshot of an instance 1. you create a volume-snapshot 
in CS UI 2. XenServer is taking a snapshot of the vm and uses the first 
snapshot as parent (you are unable to see this in XenCenter because the parent 
snapshot will be hidden) 3. XenServer is mounting secondary storage 4. 
XenServer is copying only delta of snapshot to secondary storage into the same 
directory as the first snapshot 5. XenServer is unmounting secondary storage


If you delete the a snapshot via XenCenter all following volume-snapshots are 
going to fail because of missing parent!

If you migrate vm to another XenServer host and create a volume-snapshot it 
will work. Reason for that is that CS is starting from the beginning here and 
handles this as a first snapshot. CS also uses a new folder on secondary 
storage for this volume-snapshot.

The last snapshot on XenServer will always be there, because CS needs it as 
parent for the next one and XenServer is creating a vhd chain.

The questions here are:
1. When I delete an instance is the snapshot on XenServer still needed?
I think now, it can be deleted even the volume-snapshot is still on secondary 
storage.

2. When I delete all volume-snapshots in CS UI of the snapshot-chain will CS 
delete the snapshots on XenServer?
As far as I can see, no.

3. Who is cleaning up the snapshots on XenServer's primary storage when you do 
a storage migration (normal and live) to another primary storage?
Right now, nobody is doing this and if you are using storage migration a lot 
(if you are using local storage you will do it a lot) than you end up with GBs 
of unwanted data on your primary storages.

Mit freundlichen Grüßen / With kind regards,

Swen


-Ursprüngliche Nachricht-
Von: Pavan Bandarupally [mailto:pavan.bandarupa...@accelerite.com]
Gesendet: Dienstag, 5. April 2016 11:17
An: users@cloudstack.apache.org; S. Brüseke - proIO GmbH
Betreff: RE: snapshot cleanup on hypervisor primary storage

Hi Swen,

I don't think this is expected. The snapshots should get cleaned from Primary 
Storage by XenServer. Can you please check if the snapshots are usable or 
corrupted ?

Regarding deletion of snapshots on expunging the VM is not expected, because we 
do keep the snapshots (in secondary store) for further usage as templates / 
volumes can be created from the snapshots irrespective of whether the VM from 
whose disk the snapshot was created exists or not.

Regards,
Pavan

-Original Message-
From: S. Brüseke - proIO GmbH [mailto:s.brues...@proio.com]
Sent: Tuesday, April 05, 2016 1:21 PM
To: users@cloudstack.apache.org
Subject: snapshot cleanup on hypervisor primary storage

Hey guys,

we are using CS 4.5 with XenServer 6.5 SP1 and observed a behavior with 
volume-snapshots that will fill up your primary storage over time:

Workflow:
1. create an instance
2. create a volume-snapshot of the ROOT-disk of that instance 3. delete 
instance and expunge it 4. check primary storage of XenServer. The latest 
snapshot of each volume-snapshot will stay on primary storage and is not being 
deleted even after waiting for storage.cleanup.interval

Can somebody reproduce this?

As far as I understand the workflow of volume-snapshots CS will XenServer ask 
to do a snapshot of the vm and then copy this snapshot to secondary storage. 
But why CS is not deleting the snapshot on primary storage after a success copy 
to secondary storage? Is this a "broken" workflow or is there a reason for that?

Is this the same behavior in newer releases of CS?

Mit freundlichen Grüßen / With kind regards,

Swen




- proIO GmbH -
Geschäftsführer: Swen Brüseke
Sitz der Gesellschaft: Frankfurt am Main

USt-IdNr. DE 267 075 918
Registergericht: Frankfurt am Main - HRB 86239

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese 

RE: snapshot cleanup on hypervisor primary storage

[Pavan Bandarupally]

Hi Swen,

I don't think this is expected. The snapshots should get cleaned from Primary 
Storage by XenServer. Can you please check if the snapshots are usable or 
corrupted ?

Regarding deletion of snapshots on expunging the VM is not expected, because we 
do keep the snapshots (in secondary store) for further usage as templates / 
volumes can be created from the snapshots irrespective of whether the VM from 
whose disk the snapshot was created exists or not.

Regards,
Pavan

-Original Message-
From: S. Brüseke - proIO GmbH [mailto:s.brues...@proio.com]
Sent: Tuesday, April 05, 2016 1:21 PM
To: users@cloudstack.apache.org
Subject: snapshot cleanup on hypervisor primary storage

Hey guys,

we are using CS 4.5 with XenServer 6.5 SP1 and observed a behavior with 
volume-snapshots that will fill up your primary storage over time:

Workflow:
1. create an instance
2. create a volume-snapshot of the ROOT-disk of that instance 3. delete 
instance and expunge it 4. check primary storage of XenServer. The latest 
snapshot of each volume-snapshot will stay on primary storage and is not being 
deleted even after waiting for storage.cleanup.interval

Can somebody reproduce this?

As far as I understand the workflow of volume-snapshots CS will XenServer ask 
to do a snapshot of the vm and then copy this snapshot to secondary storage. 
But why CS is not deleting the snapshot on primary storage after a success copy 
to secondary storage? Is this a "broken" workflow or is there a reason for that?

Is this the same behavior in newer releases of CS?

Mit freundlichen Grüßen / With kind regards,

Swen




- proIO GmbH -
Geschäftsführer: Swen Brüseke
Sitz der Gesellschaft: Frankfurt am Main

USt-IdNr. DE 267 075 918
Registergericht: Frankfurt am Main - HRB 86239

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet.

This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail in error) 
please notify the sender immediately and destroy this e-mail.
Any unauthorized copying, disclosure or distribution of the material in this 
e-mail is strictly forbidden.





DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Accelerite, a Persistent Systems business. It is intended only for 
the use of the individual or entity to which it is addressed. If you are not 
the intended recipient, you are not authorized to read, retain, copy, print, 
distribute or use this message. If you have received this communication in 
error, please notify the sender and delete all copies of this message. 
Accelerite, a Persistent Systems business does not accept any liability for 
virus infected mails.

RE: Hyper-V Agent log files.

[Pavan Bandarupally]

Hi Rodrigo,

I do not think there is any separate agent log other than the event viewer logs 
available for the service.

Regards,
Pavan

-Original Message-
From: Rodrigo Marques [mailto:rodrigomarques1...@gmail.com] 
Sent: Saturday, March 19, 2016 3:08 AM
To: users@cloudstack.apache.org
Subject: Hyper-V Agent log files.

Hello,
I am trying to install and run the Hyper-V Agent provided here.

I installed and it appears to be running (at least it appears in Windows 
Services). The problem is that I would like to access its log files and I 
cannot find them.
Does anyone know where it is?
I looked in the source code and found a "cloudstack-agent.log". I have tried to 
look for this file in the server using the command *dir -r 
"cloudstack-agent.log" *but it returned nothing.

Can anybody help me?

Thanks.

Best Regards,
Rodrigo.
--
Atenciosamente,

Rodrigo Marques.



DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Accelerite, a Persistent Systems business. It is intended only for 
the use of the individual or entity to which it is addressed. If you are not 
the intended recipient, you are not authorized to read, retain, copy, print, 
distribute or use this message. If you have received this communication in 
error, please notify the sender and delete all copies of this message. 
Accelerite, a Persistent Systems business does not accept any liability for 
virus infected mails.

Raised a blocker bug for failure in Add Region

[Pavan Bandarupally]

https://issues.apache.org/jira/browse/CLOUDSTACK-8696

This is a regression.

Regards,
Pavan

RE: Resize Data disk shrink

[Pavan Bandarupally]

Hi Punit,

Currently Shrink is not supported in Xenserver. Please have a look at the 
issue: https://issues.apache.org/jira/browse/CLOUDSTACK-3392

Regards,
pavan

From: Punit Dambiwal [hypu...@gmail.com]
Sent: Thursday, August 08, 2013 12:55 PM
To: users@cloudstack.apache.org
Subject: Resize Data disk shrink

Hi,

I want to resize the data disk of one VM (Hypervisior is XenServer),but
it's failed with the following error :-

---
[root@csmgmt ~]# cat /var/log/cloudstack/management/management-server.log |
grep resize
2013-08-08 15:17:46,816 DEBUG [cloud.api.ApiServlet] (catalina-exec-9:null)
===START===  116.92.38.79 -- GET
 
command=resizeVolume&id=bd20725e-b06f-406a-b2ee-68c9107eb7c2&shrinkok=true&diskofferingid=04ab93c3-286c-4069-a138-a74b23cbf3b6&response=json&sessionkey=ILMgCgDboPwhcwETjVHMYgJG3%2Fg%3D&_=1375946313923
2013-08-08 15:17:46,916 DEBUG [cloud.api.ApiServlet] (catalina-exec-9:null)
===END===  116.92.38.79 -- GET
 
command=resizeVolume&id=bd20725e-b06f-406a-b2ee-68c9107eb7c2&shrinkok=true&diskofferingid=04ab93c3-286c-4069-a138-a74b23cbf3b6&response=json&sessionkey=ILMgCgDboPwhcwETjVHMYgJG3%2Fg%3D&_=1375946313923
2013-08-08 15:17:47,471 WARN  [xen.resource.CitrixResourceBase]
(DirectAgent-158:null) Unable to resize volume
at com.xensource.xenapi.VDI.resize(VDI.java:1350)
2013-08-08 15:17:47,472 DEBUG [agent.transport.Request]
(DirectAgent-158:null) Seq 1-1377969797: Processing:  { Ans: , MgmtId:
161339431830, via: 1, Ver: v1, Flags: 10,
[{"storage.ResizeVolumeAnswer":{"newSize":0,"result":false,"details":"failed
to resize volume:SR_BACKEND_FAILURE_79VDI Invalid size [opterr=shrinking
not allowed]","wait":0}}] }
2013-08-08 15:17:47,472 DEBUG [cloud.storage.StorageManagerImpl]
(Job-Executor-114:job-114) Resize: returned 'failed to resize
volume:SR_BACKEND_FAILURE_79VDI Invalid size [opterr=shrinking not allowed]'
2013-08-08 15:17:47,573 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-114:job-114) Complete async job-114, jobStatus: 2,
resultCode: 530, result: Error Code: 530 Error text: Failed to resize volume
2013-08-08 15:22:14,162 DEBUG [cloud.api.ApiServlet] (catalina-exec-2:null)
===START===  116.92.38.79 -- GET
 
command=resizeVolume&id=bd20725e-b06f-406a-b2ee-68c9107eb7c2&shrinkok=true&diskofferingid=04ab93c3-286c-4069-a138-a74b23cbf3b6&response=json&sessionkey=ILMgCgDboPwhcwETjVHMYgJG3%2Fg%3D&_=1375946581352
2013-08-08 15:22:14,227 DEBUG [cloud.api.ApiServlet] (catalina-exec-2:null)
===END===  116.92.38.79 -- GET
 
command=resizeVolume&id=bd20725e-b06f-406a-b2ee-68c9107eb7c2&shrinkok=true&diskofferingid=04ab93c3-286c-4069-a138-a74b23cbf3b6&response=json&sessionkey=ILMgCgDboPwhcwETjVHMYgJG3%2Fg%3D&_=1375946581352
2013-08-08 15:22:14,531 WARN  [xen.resource.CitrixResourceBase]
(DirectAgent-136:null) Unable to resize volume
at com.xensource.xenapi.VDI.resize(VDI.java:1350)
2013-08-08 15:22:14,532 DEBUG [agent.transport.Request]
(DirectAgent-136:null) Seq 1-1377969817: Processing:  { Ans: , MgmtId:
161339431830, via: 1, Ver: v1, Flags: 10,
[{"storage.ResizeVolumeAnswer":{"newSize":0,"result":false,"details":"failed
to resize volume:SR_BACKEND_FAILURE_79VDI Invalid size [opterr=shrinking
not allowed]","wait":0}}] }
2013-08-08 15:22:14,532 DEBUG [cloud.storage.StorageManagerImpl]
(Job-Executor-118:job-118) Resize: returned 'failed to resize
volume:SR_BACKEND_FAILURE_79VDI Invalid size [opterr=shrinking not allowed]'
2013-08-08 15:22:14,600 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-118:job-118) Complete async job-118, jobStatus: 2,
resultCode: 530, result: Error Code: 530 Error text: Failed to resize volume
[root@csmgmt ~]#
--