guestinfo vs machine.id variables
I am trying to pass some configuration specs to a VM. These specs. would later be retrieved (with the help of vmtoolsd cmd)by the init services during booting of the VM.
Now i found two choices here:
1. Either i can set the VM specific info using guestinfo. . guestinfo supports multiple key/value pairs.
2. Or i set the info using machine.id . machine.id doesn't support multiple key/value pairs and you have to specify all the paramaters as a string:
machine.id =
Cons of guestinfo:
1. These variables are not saved in the VM's .vmx file.
2. We can set these variables only when a VM is powered-on. Don't know the exact location where these variables are stored. but still we can retrieve these variables using vmtoolsd --cmd "info-get guestinfo." only till VM is powered on. Once VM is powered off, these variables would get lost. So persistence is a problem.
machine.id:
1. This variable is saved in .vmx file and is persisted even during VM's reboot.
I really don't know when machine.id variable should be used. Is using this variable a safe option? Is this variable being used internally by the VM? Is this reserved for something or can i go ahead using this variable for setting some VM info.
↧