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<http://www.dsscorp.com/> | Data Center<http://www.dssdatacenter.com/> | Twitter<http://www.twitter.com/DSSDataCenter> | Facebook<https://www.facebook.com/distributedsystemsservicesinc#!/DistributedSystemsServices>