Re: [CentOS-virt] Networking in KVM
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?Paul On 03/15/16, Digimer wrote: On 15/03/16 08:07 PM, paul.greene...@verizon.net wrote:> Hi all,> > New to KVM. Did a group install for "Virtualization Host" on CentOS 7.> Created two virtual machines - one with centos and one with an> evaluation copy of Windows 2012 server.> > Both virtual machines correctly did updates out to their respective> vendors (Centos and MS respectively), but they can't talk to each other> or talk to any other system in my internal network. From what I've found> so far, if I understand correctly, this is the default behaviour for KVM> out of the box.> > What I would like to be able to do is allow the virtual machines to> appear on my internal network just like any other machine, in the same> IP address space, without using dhcp for assigning addresses. The KVM> machines are using 192.168.122.x, my other machines are using 192.168.1.x.> > Any guidance/suggestions greatly appreciated.> > Paul GreeneYou need a traditional bridge (that acts more like a network switch).A quick google turns up these, which might help:http://jensd.be/207/linux/install-and-use-centos-7-as-kvm-virtualization-hosthttp://unix-linux-server.blogspot.ca/2014/10/centos-7-kvm-installation-and-bridge.html-- DigimerPapers and Projects: https://alteeve.ca/w/What if the cure for cancer is trapped in the mind of a person withoutaccess to education?___CentOS-virt mailing listCentOS-virt@centos.orghttps://lists.centos.org/mailman/listinfo/centos-virt ___ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Networking in KVM
On Fri, 2016-03-18 at 13:02 -0400, Mike - st257 wrote: > Paul, > > > On Thu, Mar 17, 2016 at 5:47 PM, Digimer wrote: > On 17/03/16 04:47 PM, paul.greene...@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 > 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 > http://www.tldp.org/HOWTO/BRIDGE-STP-HOWTO/set-up-the-bridge.html > > > > Check that they're using your static bridge. 'virsh dumpxml > ' will > have a section like: > > > > > > > > >slot='0x05' > function='0x0'/> > > > > 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 ' if you're > comfortable editing > XML). > > > An additional command to run to verify your Ethernet bridge(s) > operation is: > brctl show > brctl show > > > ~]# 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 // > ___ > CentOS-virt mailing list > CentOS-virt@centos.org > https://lists.centos.org/mailman/listinfo/centos-virt Hi, You need to look at the requirements for this package. If I spin a build of that SRPM in mock I get: Error: No Package found for aubio-devel >= 0.3.2 Error: No Package found for cwiid-devel >= 0.6.00 Error: No Package found for itstool >= 2.0.0 Error: No Package found for jack-audio-connection-kit-devel >= 1.9.10 Error: No Package found for libgnomecanvasmm26-devel >= 2.16 Error: No Package found for liblo-devel >= 0.24 Error: No Package found for liblrdf-devel >= 0.4.0 Error: No Package found for libltc-devel >= 1.1.1 Error: No Package found for lilv-devel >= 0.14.0 Error: No Package found for lv2-devel >= 1.0.0 Error: No Package found for rubberband-devel >= 1.0 Error: No Package found for serd-devel >= 0.14.0 Error: No Package found for sord-devel >= 0.8.0 Error: No Package found for sratom-devel >= 0.2.0 Error: No Package found for suil-devel >= 0.6.0 I have only checked the first, but aubio is neither in CentOS nor EPEL. Thus the failure. Regards Phil signature.asc Description: This is a digitally signed message part ___ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] kernel-3.18.25-19 xen kernel with XSA-171 in virt6 and virt7 testing
George has built and I have pushed to virt6-xen-common-testing and virt7-xen-common-testing the kernel-3.18.25-19 kernel. Please test this kernel and we can release it. It also has the fix for XSA-171: http://xenbits.xen.org/xsa/advisory-171.html Thanks, Johnny Hughes signature.asc Description: OpenPGP digital signature ___ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Networking in KVM
Paul, On Thu, Mar 17, 2016 at 5:47 PM, Digimer wrote: > On 17/03/16 04:47 PM, paul.greene...@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 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 http://www.tldp.org/HOWTO/BRIDGE-STP-HOWTO/set-up-the-bridge.html > > Check that they're using your static bridge. 'virsh dumpxml ' will > have a section like: > > > > > > > > >function='0x0'/> > > > > 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 ' if you're comfortable editing > XML). An additional command to run to verify your Ethernet bridge(s) operation is: brctl show brctl show ~]# 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 // ___ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
