Network device in VM gone after moving the VM












0















Background:
I opened a Ubuntu 18.04.1 image that had been created on the same computer, but that had been moved from a different location. When prompted I asked that it had been copied (not moved).



Now, Ubuntu no longer seems to auto-recognize the network device. I have tried removing and adding network devices in the Settings in VMWare, but to no avail. It's not like it's not detected in the kernel. I get a ens33 device (renamed from eth0), which is to be expected. I can also manually use dhclient to get network connectivity (dclient ens33), but nothing shows in Settings->Network (except for VPN and Proxy sections). There should have been a "Wired" section there.



Some tips online hint to Netplan, but its config is pretty empty:



$ cat /etc/netplan/01-network-manager-all.yaml 
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager


Others have mentioned that devices get different UUIDs when imported in VMWare and that this causes some trouble in Ubuntu as it somehow maps (the old) UUIDS to MAC addresses. I am not sure how or where to reset these bindings, but this seems like a step in the right direction.










share|improve this question



























    0















    Background:
    I opened a Ubuntu 18.04.1 image that had been created on the same computer, but that had been moved from a different location. When prompted I asked that it had been copied (not moved).



    Now, Ubuntu no longer seems to auto-recognize the network device. I have tried removing and adding network devices in the Settings in VMWare, but to no avail. It's not like it's not detected in the kernel. I get a ens33 device (renamed from eth0), which is to be expected. I can also manually use dhclient to get network connectivity (dclient ens33), but nothing shows in Settings->Network (except for VPN and Proxy sections). There should have been a "Wired" section there.



    Some tips online hint to Netplan, but its config is pretty empty:



    $ cat /etc/netplan/01-network-manager-all.yaml 
    # Let NetworkManager manage all devices on this system
    network:
    version: 2
    renderer: NetworkManager


    Others have mentioned that devices get different UUIDs when imported in VMWare and that this causes some trouble in Ubuntu as it somehow maps (the old) UUIDS to MAC addresses. I am not sure how or where to reset these bindings, but this seems like a step in the right direction.










    share|improve this question

























      0












      0








      0








      Background:
      I opened a Ubuntu 18.04.1 image that had been created on the same computer, but that had been moved from a different location. When prompted I asked that it had been copied (not moved).



      Now, Ubuntu no longer seems to auto-recognize the network device. I have tried removing and adding network devices in the Settings in VMWare, but to no avail. It's not like it's not detected in the kernel. I get a ens33 device (renamed from eth0), which is to be expected. I can also manually use dhclient to get network connectivity (dclient ens33), but nothing shows in Settings->Network (except for VPN and Proxy sections). There should have been a "Wired" section there.



      Some tips online hint to Netplan, but its config is pretty empty:



      $ cat /etc/netplan/01-network-manager-all.yaml 
      # Let NetworkManager manage all devices on this system
      network:
      version: 2
      renderer: NetworkManager


      Others have mentioned that devices get different UUIDs when imported in VMWare and that this causes some trouble in Ubuntu as it somehow maps (the old) UUIDS to MAC addresses. I am not sure how or where to reset these bindings, but this seems like a step in the right direction.










      share|improve this question














      Background:
      I opened a Ubuntu 18.04.1 image that had been created on the same computer, but that had been moved from a different location. When prompted I asked that it had been copied (not moved).



      Now, Ubuntu no longer seems to auto-recognize the network device. I have tried removing and adding network devices in the Settings in VMWare, but to no avail. It's not like it's not detected in the kernel. I get a ens33 device (renamed from eth0), which is to be expected. I can also manually use dhclient to get network connectivity (dclient ens33), but nothing shows in Settings->Network (except for VPN and Proxy sections). There should have been a "Wired" section there.



      Some tips online hint to Netplan, but its config is pretty empty:



      $ cat /etc/netplan/01-network-manager-all.yaml 
      # Let NetworkManager manage all devices on this system
      network:
      version: 2
      renderer: NetworkManager


      Others have mentioned that devices get different UUIDs when imported in VMWare and that this causes some trouble in Ubuntu as it somehow maps (the old) UUIDS to MAC addresses. I am not sure how or where to reset these bindings, but this seems like a step in the right direction.







      vmware vmware-workstation






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Feb 15 at 10:58









      oligofrenoligofren

      357215




      357215






















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "89"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1118471%2fnetwork-device-in-vm-gone-after-moving-the-vm%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Ask Ubuntu!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1118471%2fnetwork-device-in-vm-gone-after-moving-the-vm%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

          Mangá

          Eduardo VII do Reino Unido