Unable to apply DRS resource settings on host…

Summary:

VMWare KB 1004667 addresses a different scenario than below.

This error can also occur if a VM has issues w/ the vmxf file as evidenced by digging into the hostd.log file.  What’s interesting, the VM can be fully functional, vMotion’d, and not show a single error in vCenter.  Once you dig to find a VM is causing the issue, vMotion’ing this VM to another host, the new host begins having issues applying DRS settings.

Unable to apply DRS resource settings on host (Reason: A general system error occurred: Invalid Fault). This can significantly reduce the effectiveness of DRS.

Hostd.log (/var/log/vmware/hostd.log) contains messages similar to:

[2010-03-22 15:13:05.285 F5CA0B90 info 'Libs'] Vix: [18420 foundryFile.c:2109]: FoundryFile_Save: Failed to open file /vmfs/volumes/volumeID/vmname/vmname.vmxf

[2010-03-22 15:13:05.285 F5CA0B90 info 'Libs'] Vix: [18420 foundryFile.c:2130]: FoundryFile_Save: Failed to close file /vmfs/volumes/volumeID/vmname/vmname.vmxf, Bad file descriptor

[2010-03-22 15:13:05.285 F646DB90 info 'Vmsvc'] SaveWorkingCopy: Error: (4) A file was not found

[2010-03-22 15:13:05.285 F646DB90 info 'vm:/vmfs/volumes/volumeID/vmname/vmname.vmx'] Failed to update resource config: vim.fault.FileNotFound

[2010-03-22 15:13:05.290 F646DB90 info 'App'] AdapterServer caught exception: vim.fault.FileNotFound

Resolution:

Once the VM causing issues is identified, I noticed that the vmware.log file was growing incessantly.  This is what I found in it:

Mar 19 03:41:31.166: vmx| TOOLS received request in VMX to set option 'synctime' -> '0'
Mar 19 03:41:31.171: vmx| VMXVmdb_LoadRawConfig: Loading raw config

Then repeat about thousands of times.  Short answer, in my case, was to upgrade the tools and reboot the VM.

Comments

Anonymous said…
I had a similar case with the exact same error. However, in my case, the solution is described in http://spininfo.homelinux.com/news/VirtualCenter/2008/10/14/Re:_Unable_to_apply_DRS_Resource_Settings..._Invalid_Fault

In short, after a host upgrade, some of the guests did not finish the vmtools installation (Linux machines and some XP machines). Going one by one and forcing vmtools installation to END solved the problem with the DRS.
May 11, 2010 at 4:43 AM
Anonymous said…
I had the same problem with multiple linux VM's, but all the VM's VMtools were updated to the latest version, so I just started the VMtools installation and ended the VM tools installation, but doing so, VM was able to be migrated. I think that the after the VM tools installation the unmounting of the CD drive is having some problem
October 20, 2010 at 8:08 AM
Anonymous said…
Just encountered the message mentioned above. My problem was VM Tools related. The VM's summary said the Tools were not installed, but I found they were installed, just noy running. Thanks for pointing me in the right direction.
January 5, 2013 at 10:46 PM
Post a Comment

Popular posts from this blog

NSX-T: Release associated invalid node ID from certificate

Image
Summary: Basically had an expiring certificate registered in NSX-T that was associated to a node_id that is no longer valid.  Long story short, there wasn't anything obvious in API to delete or disassociate a certificate from a node_id for 3.2.2.  Not sure how things got in this state, but annotating for future reference.  This may change in future revisions, so always check API for latest. Details: Effectively had a stale node associated w/ a certificate that was expiring.  Could not delete certificate until that node was disassociated from the certificate. To get certificate details and associated node_id's, you can use the following curl call (UI works too): curl -k -X GET -H "Content-Type: application/json" -u admin https://<manager ip>/api/v1/trust-management/certificates/<cert UUID> Above will return something like this: Below must be run from one of the manager nodes via elevation to root: ONLY RUN THIS IF YOU ARE ABSOLUTELY SURE OF WHAT YOU ARE DO...
Read more

NSX-T: vCenter and NSX-T Inventory out of Sync (Hosts in vSphere not showing up in NSX-T)

Image
Summary: NSX-T loses synch w/ vCenter inventory, but statuses don't appear to show an issue.  Basically, you add a host to a vCenter cluster, NSX-T bits should start to automatically installing on new host.  Assuming you've created a Transport Node Profile and associated w/ the cluster.  The problem is that NSX-T doesn't see the new host and its link to the compute manager (vCenter) looks fine. Looks fine, Y U NO WORK!? So what's going on here?  This appears to affect NSX-T 2.5 and 2.5.1.  Cause is unknown. Workaround: Restart the cm-inventory service on each NSX-T mgmt/controller node using API or CLI. Details: If you were to query the status of the cm-inventory via API or CLI, you could query all 3 manager/controller nodes and get a status of running.  Even if the primary node associated w/ the VIP, if configured, is not necessarily in charge of inventory.  So you could restart the cm-inventory service till you are blue in the face ...
Read more

MacOS: AnyConnect VPN client was unable to successfully verify the IP forwarding table modifications.

Image
The VPN client was unable to successfully verify the IP forwarding table modification.  A VPN connection will not be established. Summary: I started running into issue utilizing Cisco AnyConnect on my Mac basically complaining about not able to overwrite IP forwarding tables.  This was on 4.6.x.  Since my VPN endpoints were not providing me w/ an updated client and w/ no access to Cisco Anyconnect downloads, my only option was to try openconnect.  It was totally worth it, here is why and how to set it up. PreReqs: Homebrew Installing OpenConnect: Launch MacOS Terminal brew install openconnect Getting VPN IP's/DNS Endpoints from AnyConnect: The information is typically located in your profile xml files located here: /opt/cisco/anyconnect/profile/somethingsomething.xml In the xml file, you are looking for "<HostAddress>typicallyaDNSName.com</HostAddress>" entry.  These are your VPN endpoints that you would need to pass to openconnec...
Read more