Creating a quiesced snapshot failed because the (user-supplied) custom pre-freeze script in the virtual machine exited with a non-zero return code

During one of the P2V I got below mention error message

Do not panic, just reinstall the VM tools and retry to the HOT cloning again. This will work

Snapshot dependency on .vmsd file

There were a VM which has been spreads across multiple folder . One folder were holding .flat file and delta file. While other was holding all the snapshot.

We have to shift this VM to a different host in different site. We created the same folder structure at different site but still all the snapshot were lost. I started looking at each vmdk files (Every snapshot has its own VMDK to refer to) and corrected the file location /vmfs/volumes/<file_system_UUID>.

After fixing I was still not able to see my all snapshot under snapshot manager. Finally I had a look at .vmsd file .It has few pointers to old datastore

"snapshot0.disk0.fileName =". After I fix I was able to see all the snapshot.

Cloning a snapshot attached Virtual Machine

I am returning back after a long vacation. Thanks to my new family member.

If you want to clone a snapshot machine you have to be very careful because snapshots are lost on cloned machine. This was usual method which we were using for migrating from one location to other location in order to save WAN bandwidth.

The method which we adopted was to clone the VM's to a cheap filer (FAS2020) and ship the filer . This way WAN link will be saved. With VC2.5 U5 and all we can do live cloning of VM's For the VM's which has snapshot I usually copy it "as it is " to the filer and then do the same thing out of filer. Register the VMX and all set.

Copy using SCP was very painful so I found new way to do it TAR

Get inside the VMFS volume.

tar zcf - <vm_folder_name>/ | ssh root@<target ESX host name> "cd /vmfs/volumes/<target vol name>/; tar zpxvf -"

I became DAD again

On 18-7-2009 me and my wife blessed with the baby boy. Baby weight 3.34KG and every thing was normal by GOD grace. It happen just like that. For our first kid my wife spend around 14hrs for the labour but this time it was really different experiance.

Around 8:30 AM my wife asked me to take her to the hospital and 10:37AM baby boy arrived.

Almighty was very very kind for both us . HE did not want to trouble us

Thank You

vCenter 2.5u4 Performance Overview - Chart could not be loaded .Error :The URI is empty

When I was trying to install plugin using plugin manager I was getting “Invalid URI: The URI is empty ”

VMTM forum suggested

http://communities.vmware.com/thread/196315

“ dlane's post above put me on the right track to a fix in our environment, so thanks for that! Ultimately I had a service ticket go all the way to VMware Engineering to verify what was wrong and nail down the process to fix it, but this was the key. Our vCenter server had two NICs, one of which is on a private non-routed subnet. The URL to the statsReportExtension.xml file was pointing to the unroutable IP instead of the one it should be, so clients couldn't reach it. Manually pointing a web browser to the URL with the correct IP can confirm this.

So, fixing this is a two step process. First of all, find the offending XML file and correct the IPs in it (should be like 3 instances, one in each stanza).This will point clients to the right data once they get the correct XML file. You should be able to find it under Program Files\VMware\Infrastructure\VirtualCenter Server\tomcat\webapps\statsreport\extension or something similar. Confirm the correct values by manually pointing to the URL with correct IP from a client system.

Second, you need to correct the values in the vCenter DB that tell the clients how to reach the XML file in the first place. You need to stop the vCenter service and Web Infrstructure Access service first. I also advise a backup of the vCenter database. Use a SQL query editor to connect to the DB and look at the entries in the VPX_EXT_SERVER table. Find the entry with EXT_ID=com.vmware.vim.stats.report, and correct the IP address in the URL column - don't change anything else, just the IP in that one entry. Save the changes and restart the vCenter and Web services. This should now correctly point clients to the XML file. Confirm that Perf Overview still works OK on the server itself (open VI3 client to "localhost"), and if that's working, see if it fixes the plugin on the client side as well by opening a new VI3 client session to your server. You should see that the Performance Overview tab appears when you have a Host, VM, or Resource Pool selected. You should NOT need to go to Manage Plugins and download anything, it should just be there when you start the client and select the inventory item... Trying to download the "report" plugin is NOT going to work and will result in the "Invalid URI" error.

If you're still having problems, it's probably a different issue... try some of the other fixes/articles already linked here, or open a Support case with VMware. Good luck! ”

One More VMTM thread discussed different solution

http://communities.vmware.com/thread/196237

But I got it resolved this by restarting