Specifications

Table 6‑1. Files Migrated During Migration or Upgrade to ESXi (Continued)
File Migrated Comments
/etc/vmware/vmauth/provider.xml
/etc/hosts
Migrated.
/etc/resolv.conf
Migrated.
/usr/lib/vmware
Not migrated.
/etc/fstab
Partially migrated. Only NFS entries will be migrated to
ESXi.
/etc/passwd
Partially migrated. Only the root user password will be
saved, if possible.
/etc/shadow
/etc/groups
Not migrated.
Firewall Configuration Changes After Migration or Upgrade to ESXi 5.0
The migration or upgrade from ESX/ESXi 4.x to ESXi 5.0 results in several changes to the host firewall
configuration.
When you migrate from ESX 4.x to ESXi 5.0, the ESX 4.x rulesets list is replaced by the new rulesets list in
ESXi 5.0. The following configuration from the /etc/vmware/esx.conf file is preserved:
n
The existing enabled/disabled status.
n
The allowedip added by esxcfg-firewall.
Ruleset files that are added by the user and customized firewall rules created in ESX 4.x. are not preserved
after the migration. In the first boot after the migration, for those rulesets that don't have entries in the ESX
4.x /etc/vmware/esx.conf file, the ESXi 5.0 firewall loads the default enabled status.
After the migration to ESXi 5.0, the default block policy is set to false (PASS all traffic by default) on ESXi 5.0
only when both blockIncoming and blockOutgoing values of the default policy are false in the ESX
4.x /etc/vmware/esx.conf file. Otherwise the default policy is to deny all traffic.
Custom ports that were opened by using the ESX/ESXi 4.1 esxcfg-firewall command do not remain open
after the upgrade to ESXi 5.0. The configuration entries are ported to the esx.conf file by the upgrade, but
the corresponding ports are not opened. See the information about ESXi firewall configuration in the vSphere
Security documentation.
IMPORTANT The ESXi firewall in ESXi 5.0 does not allow per-network filtering of vMotion traffic. Therefore,
you must install rules on your external firewall to ensure that no incoming connections can be made to the
vMotion socket.
Resource Pool Settings Affected by the Upgrade from ESX 4.x to ESXi 5.0
After the upgrade to ESXi 5.0, ESX 4.x resource pool settings might be insufficient to start all virtual
machines in the pool.
The upgrade to ESXi 5.0 affects the amount of memory available to the host system. As a result, in resource
pools that are set to use nearly all of the resources available, some virtual machines might not have enough
resources to start after the upgrade. When this happens, a system alert will be issued. You can find this alert
by pressing Alt + F11 in the ESXi direct console. Reconfigure the resource pools to solve the problem.
Chapter 6 Upgrading and Migrating Your Hosts
VMware, Inc. 81