New answers tagged vmware-vcenter
In case the software inside your VMs relies on a CPU feature that the chosen EVC mode hides it will crash. A lot of software doesn't take some CPU features for granted and falls back to doing things themselves ("in software") instead of offloading tasks to specialized CPU instructions. So even if your software can run without certain CPU features you might ...
The sDRS schedules are regular vCenter scheduled tasks. There are few blog posts available on how to list these with PowerCLI, e.g. here: https://virtualbyte.wordpress.com/2014/09/05/retrieve-vcenter-scheduled-task-with-powercli/ http://rvdnieuwendijk.com/2013/01/19/get-vmware-vcenter-scheduled-tasks-with-powercli/ I personally like this one liner from the ...
This looks like a former VMFS-3 volume. The block size impacts the maximum capacity of the datastore under the legacy VMFS-3 format. But beyond that and with vSphere 5.5, you have to use the Web client to do anything with larger VMs and VMDKs. Use the vSphere Web Client to create VMDKs larger than 4 TB, or to extend an existing VMDK beyond 4 TB.
Resolved. When looking at the datastore through the vSphere Web Interface (my fault, I still prefer the old client) it correctly shows the 62TB max size limit. Potentially a hardcoded value in the old GUI given it's now deprecated.
No, you cannot have multiple vCenter servers managing the same hosts at the same time. In KB1024051 the supported HA options for vCenter are outlined. New in version 6.0 is the option to use Microsoft Clustering for the Windows version of vCenter which probably provides the best availability, but also introduces the highest possible complexity.
the solution to fix this is to sync all parties (ESXi hosts, vcenter, VRM Appliance) with ntp servers. Once this done - the error is gone.
As far as I know you can get Layer 2 networking information via SNMP from ESXi: Understanding Layer 2 networking as reported by VMware ESXi SNMP You have to query the host (management address). I don't know if you get all the information you need for your billing, though. Just give it a try. Distributed Switches also support NetFlow. Together with a NetFlow ...
The problem encountered here was caused by python or the vcsa-deploy utility attempting to use the proxy defined in the shell environment: https_proxy=http://proxy.example.com:3128/ I ran vcsa-deploy with strace and saw that it was attempting to use that proxy. I used the unset https_proxy command to temporarily disable that proxy, repeated the ...
Top 50 recent answers are included