Differences

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

--- computing:virtmanagerhell [2021/10/29 23:26] – oemb1905
+++ computing:virtmanagerhell [2021/10/29 23:31] – oemb1905
@@ Line 31: / Line 31: @@
         nameservers 8.8.8.8
-Once that's done, run ''ip a'' to make sure your primary interface connects upstream to the Data Center, and also make sure that the interface ``br0`` appears at the bottom and that the secondary interface shows it as bound to the bridge in its output.  Personally, I do not like automated DNS and I find that sometimes the interface entry does not populate to resolv.conf, so I do the following so that my ``resolv.conf`` configurations stick and I don't lose upstream DNS:
+Once that's done, run ''ip a'' to make sure your primary interface connects upstream to the Data Center, and also make sure that the interface ''br0'' appears at the bottom and that the secondary interface shows it as bound to the bridge in its output.  Personally, I do not like automated DNS and I find that sometimes the interface entry does not populate to resolv.conf, so I do the following so that my ''resolv.conf'' configurations stick and I don't lose upstream DNS:
   sudo apt install resolvconf
   echo nameserver 8.8.8.8 > /etc/resolv.conf
-Next up, it is time to configure the guest / VM machine.  I saw a lot of good tutorials online, but most of them got sloppy at this stage as far as interfaces and bridging was concerned, so I'll try to be clear where they were not.  When you set up the new VM (not covered here), instead of relying on the NAT-based default network, change the option to "Bridge" (this is in the virt-manager GUI) and enter the name of the bridge, in my case ``br0``.  (You can also use ``virsh`` for this step, but why lol - I just use X forwarding and open the GUI.)  This step connects the hypervisor NIC to the virtual switch of the bridge on the physical host.  Once that's done, spin up the VM and open up the Terminal (the one **inside** the VM).  In the VM's Terminal, configure the NIC interface as follows:
+Next up, it is time to configure the guest / VM machine.  I saw a lot of good tutorials online, but most of them got sloppy at this stage as far as interfaces and bridging was concerned, so I'll try to be clear where they were not.  When you set up the new VM (not covered here), instead of relying on the NAT-based default network, change the option to "Bridge" (this is in the virt-manager GUI) and enter the name of the bridge, in my case ''br0''.  (You can also use ''virsh'' for this step, but why lol - I just use X forwarding and open the GUI.)  This step connects the hypervisor NIC to the virtual switch of the bridge on the physical host.  Once that's done, spin up the VM and open up the Terminal (the one **inside** the VM).  In the VM's Terminal, configure the NIC interface as follows:
   sudo nano /etc/network/interfaces
@@ Line 56: / Line 56: @@
   echo nameserver 8.8.8.8 > /etc/resolv.conf
-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.
+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).
  --- //[[jonathan@haacksnetworking.com|oemb1905]] 2021/10/29 16:39//

Haack's Wiki

User Tools

Site Tools

Differences

Page Tools