VMware VirtualCenter 1.1 Support DocumentationFeatures | Documentation | Knowledge Base | Discussion Forums Completing a Guest Operating System CustomizationCustomization completes when the new virtual machine boots for the first time. Windows guest operating system virtual machines, sometimes require a reboot after the initial boot. Linux guest operating system virtual machines do not require a reboot after the initial boot. The customization process does not complete until the guest operating system boots, runs the finalization scripts, and reaches the logon screen. If the new virtual machine encounters errors when booting for the first time, many of those errors are reported in a system log. Customization errors seen after booting up the customized virtual machine are logged in both Linux as well as Windows guest operating systems. In Linux these are errors are logged to /var/log/boot.log. In Windows they are written to the Event Viewer under Application Log. Steps required to finalize guest operating system customization are covered in the following sections:
A customized Linux virtual machine does not need any additional reboots and is operational as soon as the logon screen appears after the first boot. If configuration errors occur, they are displayed on the virtual machine's console screen while the guest operating system is booting. When a customized virtual machine is powered on for the first time, its guest operating system runs a set of scripts that finalize the customization and configuration process. Depending on the guest operating system type, this process may involve additional reboots which are automatically performed by the scripts. The customization process installs scrips that run once in the target virtual machine when it powers on (or boots) for the first time after being deployed or cloned. Those scripts complete the customization process by performing final configuration operations on the guest operating system. After powering on for the first time, a customized Windows virtual machine automatically reboots twice to finalize the configuration process. It becomes operational when the logon screen appears after the second reboot. This process can take several minutes, depending upon the speed and load of the host. If any errors occur during the final configuration process, events are logged to the guest operating system's event database, and can be viewed using Program > Administrative Tools > Event Viewer from the Windows Start menu. If any of the information required in the configuration finalization process is not correct, the guest operating system pauses when the new virtual machine boots and waits for you to enter the correct information. This information includes:
To determine if the system is waiting for information check the virtual machine icon in the inventory panel, if it is flashing, it is waiting for a response. Alternatively, check the Status field in the virtual machine Summary tab. If it is displaying a link, the system is waiting for a response. Refer to Answering a Pending Question for additional information.
|
