Haack's Wiki

User Tools

Site Tools

Trace:
computing:virtmanagerhell

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
computing:virtmanagerhell [2021/10/29 23:31] – oemb1905computing:virtmanagerhell [2021/10/30 00:17] – oemb1905
Line 49: Line 49:
     nameservers 8.8.8.8     nameservers 8.8.8.8
  
-The VM interface is listed inside the guest/VM as epr1 - but remember, that's connected to the virtual switch and bridge through the previous steps, so don't worry.  After this step, restart the networking service and check to see if your IP address is assigned, and do the same tweaks to resolv.conf on the VM for stability for upstream requests:+The VM interface is listed inside the guest/VM as epr1 - but remember, that's connected to the virtual switch and bridge through the previous steps, so don't worry.  After this step, restart the networking service and check to see if your IP address is assigned.  Also, in my use-case my VM is Ubuntu which does not allow manual over-writing of resolv.conf, so I also add upstream DNS as follows:
  
   sudo service networking restart   sudo service networking restart
   ip a   ip a
   sudo apt install resolvconf   sudo apt install resolvconf
-  echo nameserver 8.8.8.8 > /etc/resolv.conf+  sudo nano /etc/resolvconf/resolv.conf.d/tail 
 +   
 +Enter the name server as follows: 
 +   
 +  nameserver 8.8.8.8
  
-At this point, I would probably reboot and then ping each external IP from a device outside of the network of the physical host.  Everything should be rosy ;>.  Some folks might be concerned about ARP and such, but virt-manager handles that with the gateway entry combined with the bridge, so no need to alter proc and pass traffic, etc.  Of course, replace Google's DNS if you so choose, but I had reliability problems with Level 3 during testing myself (sad).+At this point, I would probably reboot and then from within the VM, ping 8.8.8.8, and then ping google.com to ensure you have link and upstream DNS.  Everything should be rosy ;>.  Some folks might be concerned about ARP and such, but virt-manager handles that with the gateway entry combined with the bridge, so no need to alter proc and pass traffic, etc.  Of course, replace Google's DNS if you so choose, but I had reliability problems with Level 3 during testing myself (sad).
    
  --- //[[jonathan@haacksnetworking.com|oemb1905]] 2021/10/29 16:39//  --- //[[jonathan@haacksnetworking.com|oemb1905]] 2021/10/29 16:39//
computing/virtmanagerhell.txt · Last modified: 2023/01/15 17:47 by oemb1905

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: GNU Free Documentation License 1.3
GNU Free Documentation License 1.3 Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki