The virtual machine loses network connectivity after a reboot and the Connected option does not remain selected for the virtual network adapter in the settings for the virtual machine
search cancel

The virtual machine loses network connectivity after a reboot and the Connected option does not remain selected for the virtual network adapter in the settings for the virtual machine

book

Article ID: 324767

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:
  • The virtual machine loses network connectivity.
  • The connected option within Virtual Machine > Edit Settings > Network Adapter > Device Status appears deselected even when you have selected it.
  • The network adapter inside the guest operating system shows:

    Network Cable Unplugged

  • No VMware products such as vShield Zones, Site Recovery Manager,VMware View Horizon or others are in use.
  • When you run this command, while checking the Connected option of Network adapter in Edit Settings of virtual machine:

    tail -f /var/log/hostd.log | grep -i virtual_machine_name

    Where virtual_machine_name is the name of the virtual machine, such as spvs55

    You see entries similar to:

    <YYYY-MM-DD>T<time>.935Z [3D080B90 info 'Vmsvc.vm:/vmfs/volumes/52e1fb72-15468e94-f978-001e0bdad658/<host>.lkm.<subdomain>.lcl/<host>.lkm.<subdomain>.lcl.vmx' opID=20DD2982-000006AB] State Transition (VM_STATE_ON -> VM_STATE_RECONFIGURING)

    <YYYY-MM-DD>T<time>.935Z [3D080B90 verbose 'Vmsvc.vm:/vmfs/volumes/52e1fb72-15468e94-f978-001e0bdad658/<host>.lkm.<subdomain>.lcl/<host>.lkm.<subdomain>.lcl.vmx' opID=20DD2982-000006AB] Invoking interceptor:1-hbr

    <YYYY-MM-DD>T<time>.935Z [3D080B90 verbose 'Vmsvc.vm:/vmfs/volumes/52e1fb72-15468e94-f978-001e0bdad658/<host>.lkm.<subdomain>.lcl/<host>.lkm.<subdomain>.lcl.vmx' opID=20DD2982-000006AB] Done invoking interceptor:1-hbr

    <YYYY-MM-DD>T<time>.941Z [3DA80B90 verbose 'Vmsvc.vm:/vmfs/volumes/52e1fb72-15468e94-f978-001e0bdad658/<host>.lkm.<subdomain>.lcl/<host>.lkm.<subdomain>.lcl.vmx' opID=20DD2982-000006AB] Current VM Tracking state: disabled

    <YYYY-MM-DD>T<time>.944Z [3DA80B90 verbose 'Vmsvc.vm:/vmfs/volumes/52e1fb72-15468e94-f978-001e0bdad658/<host>.lkm.<subdomain>.lcl/<host>.lkm.<subdomain>.lcl.vmx' opID=20DD2982-000006AB] Setting VM's tracking state to disabled.

    <YYYY-MM-DD>T<time>.966Z [3D801B90 verbose 'Vmsvc.vm:/vmfs/volumes/52e1fb72-15468e94-f978-001e0bdad658/<host>.lkm.<subdomain>.lcl/<host>.lkm.<subdomain>.lcl.vmx'] Handling message _vmx8: Failed to connect ethernet1.

    <YYYY-MM-DD>T<time>.966Z [3C8D9B90 info 'vm:/vmfs/volumes/52e1fb72-15468e94-f978-001e0bdad658/<host>.lkm.<subdomain>.lcl/<host>.lkm.<subdomain>.lcl.vmx'] Disconnect check in progress.

    <YYYY-MM-DD>T<time>.967Z [3D801B90 info 'Vimsvc.ha-eventmgr'] Event 4302 : Error message on <host>.lkm.<subdomain>.lcl on c7000blade2.lkm.<subdomain>.lcl in ha-datacenter: Failed to connect ethernet1.

    <YYYY-MM-DD>T<time>.968Z [3C744B90 verbose 'Vmsvc.vm:/vmfs/volumes/52e1fb72-15468e94-f978-001e0bdad658/<host>.lkm.<subdomain>.lcl/<host>.lkm.<subdomain>.lcl.vmx'] Retrieved current VM state from foundry 4, 8

    <YYYY-MM-DD>T<time>.968Z [3C8D9B90 info 'vm:/vmfs/volumes/52e1fb72-15468e94-f978-001e0bdad658/<host>.lkm.<subdomain>.lcl/<host>.lkm.<subdomain>.lcl.vmx'] Disconnect check in progress.

    <YYYY-MM-DD>T<time>.968Z [3CADEB90 verbose 'Vmsvc.vm:/vmfs/volumes/52e1fb72-15468e94-f978-001e0bdad658/<host>.lkm.<subdomain>.lcl/<host>.lkm.<subdomain>.lcl.vmx'] Retrieved current VM state from foundry 4, 8

    <YYYY-MM-DD>T<time>.969Z [3C640B90 info 'Vmsvc.vm:/vmfs/volumes/52e1fb72-15468e94-f978-001e0bdad658/<host>.lkm.<subdomain>.lcl/<host>.lkm.<subdomain>.lcl.vmx'] Answered question _vmx8

    <YYYY-MM-DD>T<time>.986Z [3CCC1B90 verbose 'Vmsvc.vm:/vmfs/volumes/52e1fb72-15468e94-f978-001e0bdad658/<host>.lkm.<subdomain>.lcl/<host>.lkm.<subdomain>.lcl.vmx'] Handling message _vmx9: Failed to connect virtual device Ethernet1.

    <YYYY-MM-DD>T<time>.986Z [3CCC1B90 info 'Vimsvc.ha-eventmgr'] Event 4303 : Error message on <host>.lkm.<subdomain>.lcl on c7000blade2.lkm.<subdomain>.lcl in ha-datacenter: Failed to connect virtual device Ethernet1.

    <YYYY-MM-DD>T<time>.001Z [3C2E2B90 verbose 'Vmsvc.vm:/vmfs/volumes/52e1fb72-15468e94-f978-001e0bdad658/<host>.lkm.<subdomain>.lcl/<host>.lkm.<subdomain>.lcl.vmx'] Retrieved current VM state from foundry 4, 8

    <YYYY-MM-DD>T<time>.001Z [3C8D9B90 info 'vm:/vmfs/volumes/52e1fb72-15468e94-f978-001e0bdad658/<host>.lkm.<subdomain>.lcl/<host>.lkm.<subdomain>.lcl.vmx'] Disconnect check in progress.

    <YYYY-MM-DD>T<time>.002Z [3CDD9B90 info 'Vmsvc.vm:/vmfs/volumes/52e1fb72-15468e94-f978-001e0bdad658/<host>.lkm.<subdomain>.lcl/<host>.lkm.<subdomain>.lcl.vmx'] Answered question _vmx9

    <YYYY-MM-DD>T<time>.002Z [FFD13D20 verbose 'Vmsvc.vm:/vmfs/volumes/52e1fb72-15468e94-f978-001e0bdad658/<host>.lkm.<subdomain>.lcl/<host>.lkm.<subdomain>.lcl.vmx'] Retrieved current VM state from foundry 4, 8

    <YYYY-MM-DD>T<time>.005Z [3DA80B90 info 'Vmsvc.vm:/vmfs/volumes/52e1fb72-15468e94-f978-001e0bdad658/<host>.lkm.<subdomain>.lcl/<host>.lkm.<subdomain>.lcl.vmx' opID=20DD2982-000006AB] State Transition (VM_STATE_RECONFIGURING -> VM_STATE_ON)

    <YYYY-MM-DD>T<time>.007Z [3DA80B90 info 'Vimsvc.ha-eventmgr' opID=20DD2982-000006AB] Event 4304 : Reconfigured <host>.lkm.<subdomain>.lcl on c7000blade2.lkm.<subdomain>.lcl in ha-datacenter

    <YYYY-MM-DD>T<time>.019Z [3DA80B90 verbose 'Vmsvc.vm:/vmfs/volumes/52e1fb72-15468e94-f978-001e0bdad658/<host>.lkm.<subdomain>.lcl/<host>.lkm.<subdomain>.lcl.vmx' opID=20DD2982-000006AB] Time to gather config: 11 (msecs)</time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time>



Environment

VMware vSphere ESXi 5.1

Cause

This issue occurs if the ESXi host is unstable after a network/power outage.

Resolution

To resolve this issue, reboot the host to stabilize the hypervisor.
To reboot the host:
  1. Un-register all the virtual machines from the host and re-register them on different ESXi hosts in the cluster.
  2. Reboot the ESXi host.
  3. vMotion the virtual machines back to the host.


Additional Information



仮想マシンを再起動するとネットワークから切断され、仮想マシンの設定画面上の仮想ネットワークアダプタの接続オプションの選択が解除される

Impact/Risks: