Hello all.

We are having an isue with a windows guest VM.

Just restarted from the guest OS cleanly.

When I checked on vpshere client (we are not managing through VCenter), I saw errors like file locks.

When I consulted the vmware.log of the file I saw errors like below:

@

k' : Failed to lock the file (40003) (0x2013).

2015-09-08T19:46:25.003Z| vmx| I120: AIOMGR: AIOMgr_OpenWithRetry: Descriptor file '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004-delta.vmdk' locked (try 0)

2015-09-08T19:46:25.029Z| Worker#0| I120: DISKLIB-CBT   : Initializing ESX kernel change tracking for fid 185988.

2015-09-08T19:46:25.029Z| Worker#0| I120: DISKLIB-CBT   : Successfuly created cbt node 2d684-cbt.

2015-09-08T19:46:25.029Z| Worker#0| I120: DISKLIB-CBT   : Opening cbt node /vmfs/devices/cbt/2d684-cbt

2015-09-08T19:46:25.029Z| Worker#0| I120: DISKLIB-LIB   : Opened "/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001.vmdk" (flags 0xa, type vmfs).

2015-09-08T19:46:25.029Z| Worker#0| I120: DISK: Disk '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001.vmdk' has UUID '60 00 c2 9e 3d 4b a7 bf-5d 5b 83 21 cf 6a 3a 0f'

2015-09-08T19:46:25.029Z| Worker#0| I120: DISK: OPEN '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001.vmdk' Geo (4568/255/63) BIOS Geo (0/0/0)

2015-09-08T19:46:25.060Z| Worker#1| I120: DISKLIB-VMFS  : "/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000002-delta.vmdk" : open successful (10) size = 30987591680, hd = 284293. Type 8

2015-09-08T19:46:25.060Z| Worker#1| I120: DISKLIB-DSCPTR: Opened [0]: "New Virtual Machine-000002-delta.vmdk" (0xa)

2015-09-08T19:46:25.060Z| Worker#1| I120: DISKLIB-LINK  : Opened '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000002.vmdk' (0xa): vmfsSparse, 73400320 sectors / 35 GB.

2015-09-08T19:46:25.082Z| Worker#1| I120: AIOGNRC: Failed to open '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001-flat.vmdk' : Failed to lock the file (40003) (0x2011).

2015-09-08T19:46:25.082Z| Worker#1| I120: AIOMGR: AIOMgr_OpenWithRetry: Descriptor file '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001-flat.vmdk' locked (try 0)

2015-09-08T19:46:25.339Z| vmx| I120: AIOGNRC: Failed to open '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004-delta.vmdk' : Failed to lock the file (40003) (0x2013).

2015-09-08T19:46:25.339Z| vmx| I120: AIOMGR: AIOMgr_OpenWithRetry: Descriptor file '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004-delta.vmdk' locked (try 1)

2015-09-08T19:46:25.384Z| Worker#1| I120: AIOGNRC: Failed to open '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001-flat.vmdk' : Failed to lock the file (40003) (0x2011).

2015-09-08T19:46:25.384Z| Worker#1| I120: AIOMGR: AIOMgr_OpenWithRetry: Descriptor file '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001-flat.vmdk' locked (try 1)

2015-09-08T19:46:25.642Z| vmx| I120: AIOGNRC: Failed to open '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004-delta.vmdk' : Failed to lock the file (40003) (0x2013).

2015-09-08T19:46:25.642Z| vmx| I120: AIOMGR: AIOMgr_OpenWithRetry: Descriptor file '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004-delta.vmdk' locked (try 2)

2015-09-08T19:46:25.686Z| Worker#1| I120: AIOGNRC: Failed to open '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001-flat.vmdk' : Failed to lock the file (40003) (0x2011).

2015-09-08T19:46:25.686Z| Worker#1| I120: AIOMGR: AIOMgr_OpenWithRetry: Descriptor file '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001-flat.vmdk' locked (try 2)

2015-09-08T19:46:25.944Z| vmx| I120: AIOGNRC: Failed to open '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004-delta.vmdk' : Failed to lock the file (40003) (0x2013).

2015-09-08T19:46:25.944Z| vmx| I120: AIOMGR: AIOMgr_OpenWithRetry: Descriptor file '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004-delta.vmdk' locked (try 3)

2015-09-08T19:46:25.989Z| Worker#1| I120: AIOGNRC: Failed to open '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001-flat.vmdk' : Failed to lock the file (40003) (0x2011).

2015-09-08T19:46:25.989Z| Worker#1| I120: AIOMGR: AIOMgr_OpenWithRetry: Descriptor file '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001-flat.vmdk' locked (try 3)

2015-09-08T19:46:26.246Z| vmx| I120: AIOGNRC: Failed to open '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004-delta.vmdk' : Failed to lock the file (40003) (0x2013).

2015-09-08T19:46:26.246Z| vmx| I120: AIOMGR: AIOMgr_OpenWithRetry: Descriptor file '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004-delta.vmdk' locked (try 4)

2015-09-08T19:46:26.291Z| Worker#1| I120: AIOGNRC: Failed to open '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001-flat.vmdk' : Failed to lock the file (40003) (0x2011).

2015-09-08T19:46:26.291Z| Worker#1| I120: AIOMGR: AIOMgr_OpenWithRetry: Descriptor file '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001-flat.vmdk' locked (try 4)

2015-09-08T19:46:26.549Z| vmx| I120: AIOGNRC: Failed to open '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004-delta.vmdk' : Failed to lock the file (40003) (0x2013).

2015-09-08T19:46:26.549Z| vmx| I120: OBJLIB-FILEBE : FileBEOpen: can't open '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004-delta.vmdk' : Failed to lock the file (262146).

2015-09-08T19:46:26.549Z| vmx| I120: DISKLIB-VMFS  : "/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004-delta.vmdk" : failed to open (Failed to lock the file): ObjLib_Open failed. Type 8

2015-09-08T19:46:26.549Z| vmx| I120: DISKLIB-LINK  : "/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004.vmdk" : failed to open (Failed to lock the file).

2015-09-08T19:46:26.549Z| vmx| I120: DISKLIB-CHAIN : "/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004.vmdk" : failed to open (Failed to lock the file).

2015-09-08T19:46:26.549Z| vmx| I120: DISKLIB-LIB   : Failed to open '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004.vmdk' with flags 0xa Failed to lock the file (16392).

2015-09-08T19:46:26.549Z| vmx| I120: DISK: Cannot open disk "/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004.vmdk": Failed to lock the file (16392).

2015-09-08T19:46:26.549Z| vmx| I120: Msg_Post: Error

2015-09-08T19:46:26.549Z| vmx| I120: [msg.fileio.lock] Failed to lock the file

2015-09-08T19:46:26.549Z| vmx| I120: [msg.disk.noBackEnd] Cannot open the disk '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004.vmdk' or one of the snapshot disks it depends on.

2015-09-08T19:46:26.549Z| vmx| I120: ----------------------------------------

2015-09-08T19:46:26.593Z| Worker#1| I120: AIOGNRC: Failed to open '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001-flat.vmdk' : Failed to lock the file (40003) (0x2011).

2015-09-08T19:46:26.593Z| Worker#1| I120: OBJLIB-FILEBE : FileBEOpen: can't open '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001-flat.vmdk' : Failed to lock the file (262146).

2015-09-08T19:46:26.593Z| Worker#1| I120: DISKLIB-VMFS  : "/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001-flat.vmdk" : failed to open (Failed to lock the file): ObjLib_Open failed. Type 3

2015-09-08T19:46:26.593Z| Worker#1| I120: DISKLIB-LINK  : "/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001.vmdk" : failed to open (Failed to lock the file).

2015-09-08T19:46:26.593Z| Worker#1| I120: DISKLIB-CHAIN :"/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000002.vmdk": Failed to open parent "/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001.vmdk": Failed to lock the file.

2015-09-08T19:46:26.593Z| Worker#1| I120: DISKLIB-CHAIN : "/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001.vmdk" : failed to open (The parent of this virtual disk could not be opened).

2015-09-08T19:46:26.596Z| Worker#1| I120: DISKLIB-VMFS  : "/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000002-delta.vmdk" : closed.

2015-09-08T19:46:26.596Z| Worker#1| I120: DISKLIB-LIB   : Failed to open '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000002.vmdk' with flags 0xa The parent of this virtual disk could not be opened (23).

2015-09-08T19:46:26.638Z| Worker#1| I120: DISKLIB-VMFS  : "/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000002-delta.vmdk" : open successful (8) size = 30987591680, hd = 317061. Type 8

2015-09-08T19:46:26.638Z| Worker#1| I120: DISKLIB-DSCPTR: Opened [0]: "New Virtual Machine-000002-delta.vmdk" (0x8)

2015-09-08T19:46:26.638Z| Worker#1| I120: DISKLIB-LINK  : Opened '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000002.vmdk' (0x8): vmfsSparse, 73400320 sectors / 35 GB.

2015-09-08T19:46:26.638Z| Worker#1| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain: numLinks = 1, numSubChains = 1

2015-09-08T19:46:26.638Z| Worker#1| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain:(0) fid = 317061, extentType = 0

2015-09-08T19:46:26.639Z| Worker#1| I120: DISKLIB-LIB   : Resuming change tracking.

2015-09-08T19:46:26.672Z| Worker#1| I120: DISKLIB-CBT   : Initializing ESX kernel change tracking for fid 317061.

2015-09-08T19:46:26.672Z| Worker#1| I120: DISKLIB-CBT   : Successfuly created cbt node 8d688-cbt.

2015-09-08T19:46:26.672Z| Worker#1| I120: DISKLIB-CBT   : Opening cbt node /vmfs/devices/cbt/8d688-cbt

2015-09-08T19:46:26.672Z| Worker#1| I120: DISKLIB-LIB   : Opened "/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000002.vmdk" (flags 0x8, type vmfsSparse).

2015-09-08T19:46:26.675Z| Worker#1| I120: AIOGNRC: Failed to open '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001-flat.vmdk' : Failed to lock the file (40003) (0x2011).

2015-09-08T19:46:26.675Z| Worker#1| I120: AIOMGR: AIOMgr_OpenWithRetry: Descriptor file '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001-flat.vmdk' locked (try 0)

2015-09-08T19:46:26.978Z| Worker#1| I120: AIOGNRC: Failed to open '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001-flat.vmdk' : Failed to lock the file (40003) (0x2011).

2015-09-08T19:46:26.978Z| Worker#1| I120: AIOMGR: AIOMgr_OpenWithRetry: Descriptor file '/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001-flat.vmdk' locked (try 1)

Hi *.

Some time the following event shows up in my vCenter:

Alarm 'Host error' on esxi... triggered by event 313752 'Issue detected on esxi...: char_driver: ALL DONE   (2015-09-09T10:36:59.796Z cpu5:34521)'

I recognized this on my ESXi 5.5 and 6.0 hosts (Dell R610) after upgrade to 5.5U2 and 6.0.

Any ideas?

Cheers

David

I'm trying to migrate a Centos 6.6 VM from XenServer 6.5 to vSphere 5.5 but the VM after the migration hangs during boot at "probing EDD"

I export the VM from XenServer to OVF (Citrix OVF files seem incompatible with vSphere, Workstation and VitualBox as they error during the import) but I can attach the .vhd to a new VM in Workstation 10 and VirtualBox v5.0.4 or I can convert the vhd to .vmdk and attach it to a VM in vSphere 5.5, Workstation 10 or VirtualBox v5.0.4 but the end result is the same, the VM fails to boot.

I've tested the migration process with the following o/s':

Server 2008 R2 - Works but you have to set the storage connector on the VM to IDE and not SCSI as it will blue screen

Server 2012 - Works fine

Centos 6.6 - VM hangs at probing EDD

Debian 8.0 - VM hangs at probing EDD

Ubuntu 14.04.2 - Works fine

Red Hat 7.1 - Works only if booted in rescue mode, otherwise it hangs at probing EDD

I've researched Linux VMs hanging at probing EDD and only found 2 possible solutions, the first is disabling EDD, which hasn't worked or enabling EDB in the bios, which is not an option in VMware.

I believe the issue is with the o/s not seeing the disk correctly but Linux is not my area of expertise and I don't know why the o/s is picking up the kernel version (so must be reading from the disk) and then then failing to boot.

Hi I am user of esxi 5.1. I have created on RDP machine with server 2012R2.

Structure :

One disk of 140 GB. Thin provisioned and another disk of 1 TB again thin provisioned as data.

Some how 140 GB. was full and accidentally deleted one RDPxxx3.vmdk which i assumed as a snapshot now machine is complaining that particular part is missing and not switching on. please suggest resolution .

Problem :

I have connected second VMDK of 1 TB. size to new instance of server 2012R2 and this VMDK has all the parts intact, but it is showing older data only and I feel other parts of this VM is not even considered which contains the subsequent new data. So I am not able to get the new data saved in other part of this VMDK. Please give me procedure for merging all part of VMDK into one file so, newer version of data can be retrieved.

I require help desperately.

Hello everybody :-)

I'm struggling trying to find and understand what would be the best configuration for my system (and of course to learn from it)...

Considering the fact that I have :

* A Cisco SB switch capable of LACP bonds

* A Synology NAS where I already configured one bond with several VLANs & IP adresses (seems to work really fine)

* I'm using iSCSI (for the moment - I'm not against migrating to NFS)

* I've 2 hosts with 4 network cards each (1 card with 4 ports)

* I'm only using normal vSwitches (not distributed) but I want to change it.

* vSphere 5.5

Whould the following setup possible (if it actually makes sense) ?

The setup I've in mind :

* Configure 2 distributed vSwitches with several port groups : 1 for VM traffic only, 1 for storage and vMotion together

* Have 2 NICS for each vSwitch

* Configure VM traffic switch with LACP (2 ports)

* Configure vMotion and iSCSI traffic vSwitch with 2x2 port groups, crossed

I can also configure several VLANs but I don't know if this is necessary of preferable.  Would it make sense ? And if not, what would you propose ? NFS is an option if better.

Thanks in advance for your advices ! :-)

Hi,

I can't find an clear answer so I will ask here.

Is it possible to deploy VMware Integrated Openstack with the Cisco Nexus1000V Distributed Switch?

Thanks,
Kevin

I've done this on a separate partition previously, but thought I'd do it on VMware Fusion for convenience on this machine, a new MacBook Pro 15" Retina running 10.10.4.

Selecting to create the new VM from an installation disc mounts the OS X 10.11 installer as a second HD, and booting runs (at first not too badly, then VERY slowly) through the boot process, black screen with a white apple and white progress bar, until the progress bar is 100% an hour or so later — keep in mind this is for booting the installer only — and then...nothing. Even leaving overnight (so eight hours later) makes no difference.

Everything else on this machine (16GB/SSD/i7) is lightning-quick, so I'm a little stumped. Any ideas?

Hello,

I have created a vDS switch with trunk port group having 2 ports connected to two different VMs. VMs are sending tagged packets to vDS. For some reason all packets are dropped at ingress side itself (I am observing "Dropped ingress packets" counter in Ports tab of vDS switch getting incremented all the time). Do I need to change any other property of vDS other than specifying "VLAN Type" as "VLAN Trunking" and "VLAN Trunk range" as "0-4094" to resolve this problem?

I am using ESXi/VCenter 6.0.

I have also tried enabling Promiscous mode. Result was same.

Thanks,

Shashidhar

We have an ESXi5.5 environment and I have been tasked with changing the password for the Active Directory account that is used to run the VMware VirtualCenter Server Service.

There is a Data Source configured for a separate MS-SQL Server which is configured to use Windows Authentication

I have located the KB Article VMware KB: Changing the vCenter Server database user ID and password

On the key: KEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VirtualCenter\DB The values for 2 and 3 are blank

It is not entirely clear to me if the vpxd.exe -p command is required with our environment (AD service account and Windows Authentication) or if that is only if SQL Authentication is set on the Data Source - would anybody have experience of this change and be able to clarify for me?

thanks

Hi All,

I am facing an issue while installing VMtools on windows 2012 server. Getting attached error message at the time of installing VMXnet3 drivers. I already tried to install updated version of VMtools and also tired to clean up old installation of VMtools from registry.

Hi Guys,

I am trying to configure vSphere Replication appliance on my home lab but run into issues.

I have enter the vCenter server IP address for "LookupService Address", SSO password and click Save and restart service. The VRM service will start quickly and return to the stopped state. I also received error"Server returned request expired less than 0 seconds after request was issued but is shouldn't have expired for at least 600 seconds"

I have checked the following so far but could not work out the problem:

- vCenter > Runtime settings > vCenter Server managed address is the IP address of the vCenter

- ESXi host > NTP servers is the IP address of the vCenter

Any help/suggestion would be appreciated.

Hi.

I currently have 3 Windows vCenters.

VC1 = 5.0

VC2 = 5.1

VC3 = 5.5

All hosts ESX 5+

Some VMFS-3 datastores.

We are spread over two data centres so I want to migrate to them all to two Windows v6 VCs in a single SSO domain, with each VC having its own external PCS (I really don't want to use a load balancer!).

I'm trying to ascertain the most seamless way to transition the migration with the minimum downtime and disruption to our clusters/VMs, but the upgrade options seem... limited.

My current thinking is to upgrade VMFS-3 to VMFS-5 on-the-fly, then (as we don't use vDS or vApps, or Resource Pools, etc.) to build a green field VC6 environment and simply remove hosts one-by-one and re-add them to the new VC6 environment and rebuild the cluster configurations.

I would be hugely grateful for anyone's input as to how best to approach this migration.

Hey,

I've a hard fight with the new EUC Access Point.

I have imported the appliance to my vSphere 5.5 environment in various ways and configurations (single NIC, 3 NIC, with and w/o Horizon config) already and followed all steps outlined in the admin guide. Unfortunately I always get the same result. The appliance is booting fine, but refusing every network connection (https & ssh). When I logon to the console I can see the gateway user is running 3 processes called java, of which one consumes 100% CPU (it's actually 200% b/c 2 CPUs). From the appliance I can ping all backend systems and DNS resolution works.

Unfortunately I also did not manage to make the appliance send any message to my Solarwinds Kiwi Syslog server. So I'm flying blind right now.

What am I missing?

Anyone seen this before?

Is there a video or step by step guide I could follow to make sure I'm not doing anything stupid?

Thanks.

VCA-Cloud Retiring End of Sep. 2015? What next?

Hi,

I created a capacity planning Project, say add 10 host into my cluster to increase my cluster capacity.

vROPs then forecast when I will run out of the capacity in the graph.

But how do I generate a report to show my management this is what I added into the cluster, the forecasted additional capacity & how long it will last

We can generate a report in vCOPs but I can't find it in vROPs 6.0

Thanks!

So my vCenter ran out of room on C. On some investigation, the drmdump folder was 50GB!!!!!

Upon futher investigation it seems only on of the cluster folders is the culprit.

Every other cluster folder child to drmdump, has their proposeactions.dmp file zipped in a .gz file.

For some reason the files associated with this particular cluster are not getting zipped.

Anyone have any ideas?

Hey all, in the middle of an upgrade of non-prod to 6.2 from a greenfield 6.1.4. Did the NSX manager, and all controllers followed. Then following the VMware recommended upgrade sequence, I did the ESG. Then started the DLR. When attempting to upgrade the DLR, I got an error message

The "Upgrade Version" operation failed for the entity with the following error message.

[DHCP] To enable DHCP Relay, DR instance needs to be already created with one connected LIF.

Also, the router now displays status in the NSX Edges pane: "Failed while creating/updating edgeAssist interface for edge edge-3. 404 Not Found."

So I tried to clear the DHCP relay configuration on the DLR with the delete button, no dice. Tried to redeploy, fails with the same message. Tried to force sync, changes status to "Failed to force sync. NSX Edge edge-3 is in a bad state. Please retry the operation". The DHCP configuration disappears but the change appears to never commit, because when I browse to the bridging or routing section and browse back to the DHCP relay page, the original configuration is still there. This is a single DLR with no HA configured. I've attached the tech support logs from the DLR in case there are any curious support folks out there. Of note, vCenter 6.0.0 2741530, ESXi 5.5 Patch 5 re-release 2718055.

Was just going to delete the DLR and re-create it since it's a lab, but if this wasn't a lab I just would want to know why it's failing.

Took out a trial for 7. When I went to buy I was directed to 8. But 8 won't download and I'm constantly being asked for the licence key for 7. Which I can't buy! When I put in the licence key for * it's not valid. Not surprisingly. Anyone else having problems trialling 7 and buying 8?

Hi,

I've a set of VMs running a 32 bit guest OS on ESXi 5.5 installed on an UCS server (C240). Basically the server consist of a dual NUMA node equipped each with 64GB RAM (128 GB total).

Two of the total 17 VMs have been configured with 8GB whereas the 15 remaining with 4GB. To enforce VM vcpu -> NUMA node mapping statically we've set NUMA affinity (basically half of VMs are assigned to node 0 and the other half to node 1).

The weird thing to me is that, even with a plenty of RAM (see image attached), a VM (VMware Vcenter) has neverthless a small amount of remotely allocated memory (NUMA Home Node (NHN) 1 with just a small quota (31.30 MB) of configured 8GB remotely assigned to node 0).

Could you help me in understanding why ? Thanks.