Hello folk, I'm new here in the forum and I'm needing of a help with my problem. I'm following the steps of this tutorial:
VMware KB: Creating snapshots in a different location than default virtual machine directory
I did every necessary steps, however, I can't see the line that I added in the file .vmx by the vSphere, as you can behold on the picture:
In the last line should has the following parameter: Workingdir: vmfs/volumes/<datastorename>/...
Do anyone know what could be this problem? Or is it normal of the hypervisor?
I thank the help.
P.S: The vSphere I use is the 5.0.
Not all of the VM's configuration file (.vmx) entries can be edited in the Advanced Settings. Some of them are filtered out for different reasons. Please edit the settings from the CLI and don't forget to reload the .vmx once done.
Btw. remember that virtual disks with snapshots are used as chains, i.e. each chain link is active and creating snapshots on slower disks may reduce the VMs performance.
André
Hi,
The format used while adding advanced value is <parameter><value>, for this scenerio you would have to click on add row and then for parameter name use workingDir
and for value use /vmfs/volumes/46f1225f-552b0069-e03b-00145e808070/vm-snapshots.
However I have always used CLI to edit the VMX files, if you want to follow the KB as it and have access to ESXi Shell using SSH then it would be easier to cd to the virtual machine directory and then use the vi command to edit the VM.VMX file.
-Arun
http://highoncloud.blogspot.in/
About VMware Virtualization on NetApp
Hello, I forgot to say, I'm trying add the parameter for this option "Add Row", however, when I set the directory for the snapshot, simply, it's not saved. As if isn't a valid action to do there. Could be any kinda prohibition of permission of system? Or bug?
Not all of the VM's configuration file (.vmx) entries can be edited in the Advanced Settings. Some of them are filtered out for different reasons. Please edit the settings from the CLI and don't forget to reload the .vmx once done.
Btw. remember that virtual disks with snapshots are used as chains, i.e. each chain link is active and creating snapshots on slower disks may reduce the VMs performance.
André
Yes, for some reason the value of workingDir
of is not saved using the edit settings from GUI however the value of snapshot.redoNotWithParent is saved using the edit settings of the VM. For the workingDir
to take affect I had to make the changes from the ESXi Shell. It sounds more to be a bug because other VMX parameters can be set using the GUI except for workingDir
.
You may create a support request with GSS to confirm if its a bug or worked as designed. For now to fix the issue use CLI
-Arun
http://highoncloud.blogspot.in/
About VMware Virtualization on NetApp
Arun Pandey and a.p I thank you guys for this answer. By the shell really worked, it's a bit weird to see others parameters can be set over there. Well, therefore, problem solved.
Have a nice day to you.