<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Bug: After hard power off == virtual network link in bad state == virtual network dead in VMware Workstation Pro Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Bug-After-hard-power-off-virtual-network-link-in-bad-state/m-p/2963487#M180849</link>
    <description>&lt;P&gt;I suspect (now) that there is a bug in VMware Workstation 17.0.1 which corrupts the product's _internal_ state tracking associated with a virtual NIC's connected / disconnected state.&lt;/P&gt;&lt;P&gt;The net effect of this is that&lt;BR /&gt;* in the product's status bar, the virtual network is flagged as _connected_&lt;BR /&gt;* inside the virtual machine (guest) the virtual network link is flagged as DOWN&lt;/P&gt;&lt;P&gt;It would seem as if this erratic state can somehow be triggered by a hard power off of the virtual machine (VM -&amp;gt; Power -&amp;gt; Power Off), possibly also by a hard shutdown of the host (resulting in a rather unclean shutdown of VMware Workstation).&lt;/P&gt;&lt;P&gt;Adding or removing a virtual network adapter does not change any of that, which is totally surprising.&lt;/P&gt;&lt;P&gt;Obviously, the net effect of all this is that the guest system has no networking at all, and no amount of rebooting fixes that. That is ... not good.&lt;/P&gt;&lt;P&gt;The reason that I suspect that this is a bug in the VMware Workstation product is that&lt;BR /&gt;* it has happened to me twice now, both in hard shutdown scenarios (see above)&lt;BR /&gt;* the first time, I was unable to recover the network&lt;BR /&gt;* this (just now) second time, with a different guest, I played enough with command-line tools to get the network working - and it has been working ever since, after a reboot&lt;/P&gt;&lt;P&gt;... and the only one magic trick that I think that I applied is literally click "Disconnect" and then "Connect" on the virtual NIC status bar icon, to make the product "see" that I took down the&amp;nbsp;link and brought it up again.&lt;/P&gt;&lt;P&gt;I did not make _any_ persistent changes whatsoever to the guest operating system - the only persistence therefore is coming from VMware Workstation.&lt;/P&gt;&lt;P&gt;This only affected the one _running_ virtual machine which got hard-killed. The other VM running at the time continued to work fine, totally unaffected.&lt;/P&gt;&lt;P&gt;The command-line commands I used to "play" were&lt;/P&gt;&lt;P&gt;* `ip link set ens160 up` &amp;lt;-- I _had_ to do that in the broken state although the status bar suggested that the NIC was in fact connected&lt;BR /&gt;* `systemctl restart NetworkManager`&lt;BR /&gt;* `nmcli networking off`&lt;BR /&gt;* `nmcli networking on`&lt;BR /&gt;* `ip addr show`&lt;/P&gt;&lt;P&gt;Honestly, I do not believe that any of these commands did anything to contribute to getting the network situation sorted out. For lack of (and motivation to create) a full reproducer I do only strongly believe that simply toggling via the VMware Workstation UI the virtual NICs "Disconnect" / "Connect" state fixed that.&lt;/P&gt;&lt;P&gt;This post, in a way, is also a reminder for myself for troubleshooting, in case the VMware Workstation 17.0.1 virtual network for a guest dies (again).&lt;/P&gt;</description>
    <pubDate>Wed, 12 Apr 2023 07:08:46 GMT</pubDate>
    <dc:creator>cynar</dc:creator>
    <dc:date>2023-04-12T07:08:46Z</dc:date>
    <item>
      <title>Bug: After hard power off == virtual network link in bad state == virtual network dead</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Bug-After-hard-power-off-virtual-network-link-in-bad-state/m-p/2963487#M180849</link>
      <description>&lt;P&gt;I suspect (now) that there is a bug in VMware Workstation 17.0.1 which corrupts the product's _internal_ state tracking associated with a virtual NIC's connected / disconnected state.&lt;/P&gt;&lt;P&gt;The net effect of this is that&lt;BR /&gt;* in the product's status bar, the virtual network is flagged as _connected_&lt;BR /&gt;* inside the virtual machine (guest) the virtual network link is flagged as DOWN&lt;/P&gt;&lt;P&gt;It would seem as if this erratic state can somehow be triggered by a hard power off of the virtual machine (VM -&amp;gt; Power -&amp;gt; Power Off), possibly also by a hard shutdown of the host (resulting in a rather unclean shutdown of VMware Workstation).&lt;/P&gt;&lt;P&gt;Adding or removing a virtual network adapter does not change any of that, which is totally surprising.&lt;/P&gt;&lt;P&gt;Obviously, the net effect of all this is that the guest system has no networking at all, and no amount of rebooting fixes that. That is ... not good.&lt;/P&gt;&lt;P&gt;The reason that I suspect that this is a bug in the VMware Workstation product is that&lt;BR /&gt;* it has happened to me twice now, both in hard shutdown scenarios (see above)&lt;BR /&gt;* the first time, I was unable to recover the network&lt;BR /&gt;* this (just now) second time, with a different guest, I played enough with command-line tools to get the network working - and it has been working ever since, after a reboot&lt;/P&gt;&lt;P&gt;... and the only one magic trick that I think that I applied is literally click "Disconnect" and then "Connect" on the virtual NIC status bar icon, to make the product "see" that I took down the&amp;nbsp;link and brought it up again.&lt;/P&gt;&lt;P&gt;I did not make _any_ persistent changes whatsoever to the guest operating system - the only persistence therefore is coming from VMware Workstation.&lt;/P&gt;&lt;P&gt;This only affected the one _running_ virtual machine which got hard-killed. The other VM running at the time continued to work fine, totally unaffected.&lt;/P&gt;&lt;P&gt;The command-line commands I used to "play" were&lt;/P&gt;&lt;P&gt;* `ip link set ens160 up` &amp;lt;-- I _had_ to do that in the broken state although the status bar suggested that the NIC was in fact connected&lt;BR /&gt;* `systemctl restart NetworkManager`&lt;BR /&gt;* `nmcli networking off`&lt;BR /&gt;* `nmcli networking on`&lt;BR /&gt;* `ip addr show`&lt;/P&gt;&lt;P&gt;Honestly, I do not believe that any of these commands did anything to contribute to getting the network situation sorted out. For lack of (and motivation to create) a full reproducer I do only strongly believe that simply toggling via the VMware Workstation UI the virtual NICs "Disconnect" / "Connect" state fixed that.&lt;/P&gt;&lt;P&gt;This post, in a way, is also a reminder for myself for troubleshooting, in case the VMware Workstation 17.0.1 virtual network for a guest dies (again).&lt;/P&gt;</description>
      <pubDate>Wed, 12 Apr 2023 07:08:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Bug-After-hard-power-off-virtual-network-link-in-bad-state/m-p/2963487#M180849</guid>
      <dc:creator>cynar</dc:creator>
      <dc:date>2023-04-12T07:08:46Z</dc:date>
    </item>
  </channel>
</rss>

