Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Ethernet0 fails to connect to the vSwitch/vDS In the vmware.log file for the affected virtual machine, you see entries similar to:vcpu-0| Msg_Post: Errorvcpu-0| [msg.ethernet.e1000.openFailed] Failed to connect ethernet0.The error in the vmware.log file may differ depending on the network driver used in the virtual machine, such as:vcpu-0| Msg_Post: Errorvcpu-0| [msg.ethernet.<network_driver>.openFailed] Failed to initialize ethernet0. In the hostd.log file on the ESXi host where the affected virtual machine is running, you see entries similar to:[F4DDDB90 info 'vm:/vmfs/volumes/4bdef87a-55e8feda-d5eb-001e0bc421ac/DomainController/DomainController.vmx'] Question info: Failed to connect ethernet0., Id: 2 : Type : 3, Default: 0, Number of options: 1[F4F88B90 verbose 'vm:/vmfs/volumes/4bdef87a-55e8feda-d5eb-001e0bc421ac/DomainController/DomainController.vmx'] Retrieved current VM state from foundry 4, 8[F4F88B90 warning 'vm:/vmfs/volumes/4bdef87a-55e8feda-d5eb-001e0bc421ac/DomainController/DomainController.vmx'] Received a duplicate transition from foundry: 8, 1[F4DDDB90 verbose 'Vmsvc'] VixVM_AnswerMessage returned 0[F4DDDB90 info 'ha-eventmgr'] Event 235 : Message on DomainController on wdc-tse-d55.wsl.vmware.com in ha-datacenter: Failed to connect ethernet0.[F4DDDB90 verbose 'vm:/vmfs/volumes/4bdef87a-55e8feda-d5eb-001e0bc421ac/DomainController/DomainController.vmx'] Auto-answered question Failed to connect ethernet0.[576C4B90 verbose 'vm:/vmfs/volumes/5044aaba-2a1bbfe8-d62d-0024e87dbb6b/MyVM01/MyVM01.vmx '] Handling message _vmx2: Failed to connect ethernet0. -->[576C4B90 warning 'Locale'] FormatField: Invalid (vim.vm.Message.1)[57189B90 info 'vm:/vmfs/volumes/5044aaba-2a1bbfe8-d62d-0024e87dbb6b/MyVM01/MyVM01.vmx'] Disconnect check in progress.[576C4B90 warning 'Locale'] FormatField: Invalid (vim.vm.Message.1)[576C4B90 info 'ha-eventmgr'] Event 62 : Error message on MyVM01 on VMHost1 in ha-datacenter: Failed to connect ethernet0. --> The Connected option does not remain selected for the virtual network adapter in the settings for the virtual machine. The virtual machine is manually removed (powered off, removed from inventory) from a host being managed by vShield App Firewall and then manually registered (browse datastore, add vmx to inventory) on a host that is not managed by vShield App Firewall. When connecting a virtual machine to a vSwitch that no longer has vShield App Firewall installed, you see an entry similar to this in the /var/log/vmkernel log file:vmkernel: 0:04:21:50.355 cpu7:4359)DVFilter: 2373: Could not find filter 'vshield-dvfilter-module'.
This issue can occur due to an incomplete installation or improper configuration of vShield App Firewall on the cluster.
To work around this issue, add the affected virtual machine(s) to the vShield Manager App Firewall Exclusion list.Alternatively, remove left over information from the failed installation or improperly configured vShield App Firewall from the virtual machine's .vmx configuration file.To remove vShield related changes to the network from the .vmx file: Power off the affected virtual machine. Remove the virtual machine from inventory. Open the virtual machine's .vmx file using a text editor. Remove these lines (most likely at the end of the file):ethernet0.filter0.name = "vshield_filter_module_name"ethernet0.filter0.name = "uuid=uuid_number"The lines may also appear as:ethernet0.filter0.name = "vshield_filter_module_name"ethernet0.filter0.param1 = "uuid=uuid_number"Note: These lines are created during installation of vShield zones, and are recreated when it is installed again. Register the virtual machine on the ESXi/ESX host.Notes: The alternate solution only works if the VMware vShield App Firewall is completely un-installed. Otherwise, vShield Manager will re-add the lines again instantly. If you see these symptoms and removing the filter lines resolves the issue, but you are not using vShield App Firewall, you may be experiencing a known issue with the dvfilter kernel module not loading. For more information, see Booting the ESXi/ESX host fails with the error: initialization of module dvfilter failed (1031044).
To uninstall a vShield Zones instance: Log in to the vSphere Client. Select the ESXi/ESX host in the inventory. Migrate all the virtual machines or power them off, as uninstalling vShield zones will put the host into maintenance mode. Click the vShield tab. Click Uninstall for the vShield Zones service. Reboot the ESXi/ESX host. For more information, see the Quick Start Guide.Booting the ESXi/ESX host fails with the error: initialization of module dvfilter failedVMware vShield App Firewall の使用中、仮想マシンが vSwitch/vDS/ネットワークへの接続に失敗し、次のエラーが表示される： Failed to connect virtual device Ethernet0使用 VMware vShield App Firewall 时，虚拟机无法连接到 vSwitch/vDS/网络并显示错误： 无法连接虚拟设备 Ethernet0