The issue turned out to be that the backup software was attempting to backup
the volume at the same time I was trying to resize it. After making sure the
backup wasn't running, I was able to resize the drive without issue.
Chris Chupela
Systems Engineer
DSS
610.927.2031 Office
610.334
9 22:52:45,111 INFO [vmware.mo.VirtualMachineMO]
(DirectAgent-88:wyo1-p1-c1-hv5.dsscorp.com, job-641, cmd: ResizeVolumeCommand)
Test against disk backing : [WYO-P1-C1-PS1-ESX]
i-27-387-VM/d4ef260d8182427a8b36fada13875278-01.vmdk
2016-04-19 22:52:45,111 INFO [vmware.mo.VirtualMachineMO]
, 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.
The cpu frequency is set to 2.30Ghz in the GUI, both for the 16GB/4 cpu as well
as the 32Gb/4 cpu service offerings.
Chris Chupela
Systems Engineer
DSS
-Original Message-
From: Erik Weber [mailto:terbol...@gmail.com]
Sent: Saturday, June 13, 2015 3:42 AM
To: users
ffering back to 4cpu/16gb ram, vm
will start successfully. This seems odd, since I have not changed number of
cpu's but yet cloudstack is complaining that is the issue - CpuFreqGood: false.
Additionally, my memory usage and cpu usage (for the zone), sit at 59% and 29%
respectively.
C
