Ran into an interesting issue today. Friend from Japan messaged me that they were having issues connecting to Google and YouTube. I remoted into their computer and found something interesting. Google and YouTube were resolving to IPv6 addresses.
I'm thinking Japan's ISP's are upgrading their networks to IPv6. Still, I found it strange that even though Google and YouTube were resolving properly, the pages wouldn't render. Only those people connected directly to their modem would likely see this issue, if you are behind a router, then this issue would likely not manifest.
Anyway, to resolve this issue just requires that IPv6 be unbound from the Network Adapter setting in Windows. Below a sample screenshot from my Windows 7 VM.
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
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.
This error message can appear when deploying View Pool from a Parent VM (aka Gold Image) that has Microsoft’s App-V 4.5 client installed:
View Composer agent initialization state error (6): Unknown failure (waited 0 seconds)
- On the Parent VM, change the “Application Virtualization Client” service to manual.
- Next steps are completely voluntary. The only reason I went further was so that as soon as a user logs into a View session, their App-V applications would show up immediately.
- Create a batch/cmd file and place it on the root directory of the VM. (Commonly C:\)
- Open Notepad
- Paste the following two lines:
- Save the file as a bat or cmd (For this example, I’m naming mine “Custom.bat”)
- Once you’ve snapshot your changes, all you need to do is change the following setting to use the batch file that was created in the previous step Post synchonization script.
sc config sftlist start= auto
sc start sftlist
One thing the App-V / Softgrid client does is add an entry to the UserInit Key (HKLM\Software\Microsoft\Windows NT\Winlogon) in Windows. From my understanding, best practice from MS is that your supposed to put a comma after any entry that you append to this key. App-V 4.5 / Softgrid don’t do this. So when you install the View Agent, make sure the key reads something like this:
- C:\WINDOWS\system32\userinit.exe,"C:\Program Files\Softricity\SoftGrid for Windows Desktops\sftdcc.exe","C:\Program Files\VMware\VMware View\Agent\bin\wssm.exe",
All I can say, it’s about F’N time! Now I can update my templates on a monthly basis.
- VMWare View 4.0.1
- VMWare vCenter 4.0 U1
When creating a View Desktop Pool, no folder path, or datastores are presented and a whole other slew of errors should you decide NOT to grant the administrator role to the View Composer Service Account.
View Composer Role permissions need to be granted in 1 or 6 places in vCenter depending on how restricted the account should be. 1 place would be to grant the administrator role to the View Composer Service Account @ the vCenter Node Level and propagate down. If the aim to to restrict access to one cluster/host, then the View Composer Role must be applied to the following areas:
Pictures are provided as an example and are not a reflection of how all vCenter servers are configured/designed.
- VM and Templates – Role added to Chosen Target Folder, Gold Image Folder, and the “VMWareViewComposerReplicaFolder”
- Hosts and Clusters – Role added to Host | Cluster
- Datastores – Role added to Datastores related to Cluster or Host chosen.
- Datacenter – Role added to Datacenter node, do NOT propagate the View Composer Role permission.
- vCenter – This would be the name of your vCenter server, Add the role to this node, do NOT propagate.
- Networking – All networks would need to be sorted into folders and your service account granted read-only permissions all networks or just ones you specify.
I came across something interesting today while I was setting up my production View environment. One of the requirements when setting up View Composer is that it needs an account that has be part of the administrator group of the Windows OS on the vCenter server. Not a big deal since we don’t grant access to “BuiltIn\Administrators” rights to vCenter itself.
Now granted, the service account needs rights to vCenter which is up next, requirements state that the vCenter Composer service account be granted what VMWare calls the “View Composer” Role. ACTUAL View Composer Role Permissions needed, to break it down on one table here it is:
[UPDATED Permissions Table found HERE]
|Privilege Group||Privilege(s) to Enable|
|Folder||Create Folder |
|Datastore||Browse Datastore |
File Management - (This is listed in the admin guide, VMWare needs to clarify this.) My understanding is the following:
|Virtual Machine||Inventory (All Rights) |
Configuration (All Rights)
Interaction > Power On
Interaction > Power Off
Interaction > Suspend
Interaction > Reset
Provisioning > Clone
Provisioning > Allow Disk Access
Provisioning > Deploy Template
Provisioning > Read Customization Specifications
|Resource||Assign Virtual Machine to Resource Pool|
|Global||Enable Methods |
NOT in the admin guide:
|Network||NOT in the admin guide: |
|Sessions||NOT in the admin guide: |
View and Stop sessions