<div style="FONT-FAMILY: Arial; COLOR: rgb(0, 0, 0); FONT-SIZE: 12px"><div>Thanks, I followed the 2nd article, and it got the existing virtual machines communicating with each other.<br /><br />However, any new virtual machines I created after making the changes can't communicate with anything, they can't even get out to the internet, even if I manually set the IP address info. Any suggestions on that?<br /><br />Paul<br /></div><div> </div><div> </div><div style="border-top:1px solid #bcbcbc;margin:5px 0px;"></div><span style="font-size:12;font-family:arial;color:#000000;">On 03/15/16, <span>Digimer<lists@alteeve.ca></span> wrote:</span><div> </div><div style="font-size:12;font-family:arial;color:#000000;">On 15/03/16 08:07 PM, <a class="parsedEmail" href="mailto:paul.greene.va@verizon.net" target="_blank">paul.greene.va@verizon.net</a> wrote:<br />> Hi all,<br />> <br />> New to KVM. Did a group install for "Virtualization Host" on CentOS 7.<br />> Created two virtual machines - one with centos and one with an<br />> evaluation copy of Windows 2012 server.<br />> <br />> Both virtual machines correctly did updates out to their respective<br />> vendors (Centos and MS respectively), but they can't talk to each other<br />> or talk to any other system in my internal network. From what I've found<br />> so far, if I understand correctly, this is the default behaviour for KVM<br />> out of the box.<br />> <br />> What I would like to be able to do is allow the virtual machines to<br />> appear on my internal network just like any other machine, in the same<br />> IP address space, without using dhcp for assigning addresses. The KVM<br />> machines are using 192.168.122.x, my other machines are using 192.168.1.x.<br />> <br />> Any guidance/suggestions greatly appreciated.<br />> <br />> Paul Greene<br /><br />You need a traditional bridge (that acts more like a network switch).<br /><br />A quick google turns up these, which might help:<br /><br /><a class="parsedLink" href="http://jensd.be/207/linux/install-and-use-centos-7-as-kvm-virtualization-host" target="_blank">http://jensd.be/207/linux/install-and-use-centos-7-as-kvm-virtualization-host</a><br /><br /><a class="parsedLink" href="http://unix-linux-server.blogspot.ca/2014/10/centos-7-kvm-installation-and-bridge.html" target="_blank">http://unix-linux-server.blogspot.ca/2014/10/centos-7-kvm-installation-and-bridge.html</a><br /><br />-- <br />Digimer<br />Papers and Projects: <a class="parsedLink" href="https://alteeve.ca/w/" target="_blank">https://alteeve.ca/w/</a><br />What if the cure for cancer is trapped in the mind of a person without<br />access to education?<br />_______________________________________________<br />CentOS-virt mailing list<br /><a class="parsedEmail" href="mailto:CentOS-virt@centos.org" target="_blank">CentOS-virt@centos.org</a><br /><a class="parsedLink" href="https://lists.centos.org/mailman/listinfo/centos-virt" target="_blank">https://lists.centos.org/mailman/listinfo/centos-virt</a><br /></div></div>
On 17/03/16 04:47 PM, paul.greene.va at verizon.net wrote:> Thanks, I followed the 2nd article, and it got the existing virtual > machines communicating with each other. > > However, any new virtual machines I created after making the changes > can't communicate with anything, they can't even get out to the > internet, even if I manually set the IP address info. Any suggestions on > that? > > PaulCheck that they're using your static bridge. 'virsh dumpxml <vm>' will have a section like: === <interface type='network'> <mac address='52:54:00:71:20:fa'/> <source network='bcn_bridge1' bridge='bcn_bridge1'/> <target dev='vnet2'/> <model type='e1000'/> <alias name='net2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </interface> === That tells you that the interface is MAC '52:54:00:71:20:fa' is "plugged in" to the bridge 'bcn_bridge1'. If that doesn't connect to the right bridge, then you need to change it (virt-manager has a simple to use GUI for this, or you can use 'virsh edit <vm>' if you're comfortable editing XML). -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education?
Paul, On Thu, Mar 17, 2016 at 5:47 PM, Digimer <lists at alteeve.ca> wrote:> On 17/03/16 04:47 PM, paul.greene.va at verizon.net wrote: > > Thanks, I followed the 2nd article, and it got the existing virtual > > machines communicating with each other. >Right, so your VMs are on the same bridge group now (at Layer2 of OSI).> > > > However, any new virtual machines I created after making the changes > > can't communicate with anything, they can't even get out to the > > internet, even if I manually set the IP address info. Any suggestions on > > that? > > > > Paul >Have you verified connectivity to the VMs' default gateway? Does the ARP (address resolution protocol) process succeed? arp -a | grep <Default_Gateway_IP_here> http://linux-ip.net/html/ether-arp.html You may not have a NIC connected to your physical network in that bridge group. If so you need to modify your network-scripts to make that happen automatically on boot. You do not necessarily need an IP address on your bridge interface unless the VM host is acting as a router (default gateway). https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s2-networkscripts-interfaces_network-bridge.html Here's an example: ~]# cat /etc/sysconfig/network-scripts/ifcfg-XX_br0 DEVICE=XX_br0 TYPE=Bridge BOOTPROTO=static ONBOOT=yes DELAY=0 NM_CONTROLLED=no You can temporarily add an interface to the bridge group for testing purposes though. brctl addif <bridge> <interface> http://www.tldp.org/HOWTO/BRIDGE-STP-HOWTO/set-up-the-bridge.html> > Check that they're using your static bridge. 'virsh dumpxml <vm>' will > have a section like: > > ===> <interface type='network'> > <mac address='52:54:00:71:20:fa'/> > <source network='bcn_bridge1' bridge='bcn_bridge1'/> > <target dev='vnet2'/> > <model type='e1000'/> > <alias name='net2'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x05' > function='0x0'/> > </interface> > ===> > That tells you that the interface is MAC '52:54:00:71:20:fa' is "plugged > in" to the bridge 'bcn_bridge1'. If that doesn't connect to the right > bridge, then you need to change it (virt-manager has a simple to use GUI > for this, or you can use 'virsh edit <vm>' if you're comfortable editing > XML).An additional command to run to verify your Ethernet bridge(s) operation is: brctl show brctl show <bridge> ~]# brctl show XX_br0 bridge name bridge id STP enabled interfaces XX_br0 8000.00151713fdbc no p1p1 vnet0 vnet1 vnet11 vnet12 vnet13 vnet19 vnet2 vnet4 vnet6 vnet7 -- ---~~.~~--- Mike // SilverTip257 // -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20160318/0d883b73/attachment-0002.html>