Mastering VMware vSphere 5
This price is valid for United States. Change location to view local pricing and availability.
Other Available Formats: E-book
Do you think you've discovered an error in this book? Please check the list of errata below to see if we've already addressed the error. If not, please submit the error via our Errata Form. We will attempt to verify your error; if you're right, we will post a correction below.
|2||39||Qualification regarding boot options shown in Figure 2.8
Figure 2.8 includes a series of boot options to retrieve the installation script from an HTTP URL. The boot options listed do not include the netdevice parameter. Please note that some systems may require the netdevice parameter to be specified (as in netdevice = vmnic0) in order to work properly.
|3||62||Text correction: Minimum hardware requirements
Under Sizing Hardware for vCenter Server, the third bullet should read "4 GB of RAM or more" and the fourth bullet should read "4 GB of free disk space"
|3||67||Text correction: Error under Virtualizing vCenter Server
The third sentence in the sidebar headed "Virtualizing vCenter Server"
"vCenter Server installed as a VM offers increased portability, snapshot functionality, and cloning functionality."
"vCenter Server installed as a VM offers increased portability and snapshot functionality."
Sidebar should read:
Is There Always an Exception to the Rule?
Thus far, in the "Working with NFS Datastores" section, I've been talking about how NFS always uses only a single link, and how you always need to use multiple VMkernel ports and multiple NFS exports in order to utilize multiple links.
Normally, vSphere requires that you mount an NFS datastore using the same IP address or hostname and path on all hosts (you'll see this in the section "Creating and Mounting an NFS Datastore"). vSphere 5 adds the ability to use a DNS hostname that resolves to multiple IP addresses. However, each vSphere host will resolve the DNS name only once. This means that it will resolve to only a single IP address and will continue to use only a single link, as I've described. In this case, there is no exception to the rule. However, this configuration can provide some rudimentary load balancing for multiple hosts accessing a datastore via NFS over multiple links.