VMware ESX Server 2.0Features | Documentation | Knowledge Base | Discussion ForumsWith ESX Server and knowledge of a scripting language like Perl or NetShell (in a Windows 2000 guest operating system), you can pass a string from your virtual machine's configuration file to the guest operating system when you use the configuration file to launch a virtual machine. This string is known as machine.id. The content of the string you pass to the guest operating system is up to you. For additional details and sample scripts, including information on passing messages both ways between the service console and a guest, see the VMware Scripting API documentation at www.vmware.com/support/developer/scripting-API/doc/Scripting_API.pdf. You should use this feature only if you have a good understanding of a scripting language and know how to modify system startup scripts. If you use multiple configuration files that point to the same virtual disk, each configuration file can contain its own unique machine.id line. <config_file_1>.vmx contains:
scsi0:1.present = TRUE <config_file_2>.vmx contains:
scsi0:1.present = TRUE Using machine.id, you may pass such strings as the Windows system ID (SID), a machine name or an IP address. In the guest operating system startup script, you may then have the guest service retrieve this string, which can then be used by your script to set your virtual machine's system ID, machine name or IP address. In the following example, we use a Linux guest to illustrate how you can use the guest service to retrieve a string containing what becomes the virtual machine's machine name and IP address. We use RedHat62VM as the machine name and 148.30.16.24 as the IP address.
From the service console, you can prevent the service console from passing a string to the guest operating system via the guest service. To do this, set the following line in your virtual machine's configuration file. isolation.tools.machine.id.get.disable = TRUE |