Networking-KVM-2hosts-2vms-lan_router -
i have 2 hosts running opensuse 42.1 connected dlink router via eth0, accessible on 192.168.0.1 , using networkmanager: - vboard/eth0 assigned via router dhcp ip 192.168.0.199 - rihana/eth0 192.168.0.198
using kvm on both hosts, have 2 opensuse vms ( vmvboard, vmrihana) 1 on each host.
i configured on both hosts virbr0 network identically, in range 192.168.100.0/24 , dhcp range 192.168.100.128-254 , nat on physical device.
vm can ping kvm host on both side, vm's cannot talk each other across router network. config used work on opensuse 13.2, not using network manager...
what doing wrong?
is there me configuration: networking 2 hosts, router , 2 vm's, 1 on each host ?
thanks lot in advance ideas.
bridged network hosts , vms in few clicks : using wicked.
- set dlink router settings via firefox/chrome url: 192.168.0.1 user:admin pass: blank ip on 192.168.0.1 subnet mask 255.255.255.224 ( 30 usable ips) enable dhcp: unchecked
note: might easier first reset router standard setting , connect through network manager
- setting bridged network libvirt/virt-manager , wicked opensuse network service.
1.1 clean host1 , host2 previous bridge definitions yast/networkmanager/network settings/
global options tab> select in dropdown: wicked > overview tab > delete interfaces make them appear "not configured" > hostname/dns > note hostname , domain remains there > routing tab> enable ipv4 forwarding off (no routing features host1 , host2) click ok. has cleaned interfaces/bridges , activated wicked network service, instead of network manager:gnome/right upper corner has no wired/wifi settings menu options. 1.2 check cleanup in gnome terminal root: # su root password: # cd /etc/sysconfig/network
ls ifcfg returns only ifcfg-lo ifcfg.template
ls .ifcfg* ls: cannot access .ifcfg*: no such file or directory
but in case there still .ifcfg-br0 .ifcfg-eth0,
rm .ifcfg-br0 # rm .ifcfg-eth0
ifconfig shows lo interface:
lo link encap:local loopback inet addr:127.0.0.1 mask:255.0.0.0 [...] check if wicked active: # systemctl status wicked wicked.service - wicked managed network interfaces loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled) active: active (exited) since fri 2016-01-08 15:37:56 azot; 34min ago 2. setting bridge libvirt: gnome terminal command line: # virt-manager or gnome yast/virtualization/create vm,followed cancel creation 2.1 click on hypervisor qemu/kvm connect ( in case qemu/kvm ) 2.2 menu edit/connections details or right-click details 2.3 goto network interfaces tab > click + (add) > bridge > forward : name : br0 start mode: none activate now: checked on ip settings: leave dhcp or configure, mode: static ( continue on previous example , because vms ip statically defined) address: 192.168.0.2/27 (equivalent subnet mask set 255.255.255.224) gateway 192.168.0.1 bridge settings: turn stp off ( no complex networks ) choose interface(s)to bridge eth0 checked 2.4 finish - take set up. "the virtual interface being created." processing... , br0 or brx shows active. 2.5 adjust vms network nic settings while still down 2.5.0 remove old nic vm: virt-manager > select vm > open > click lamp icon > select nic > click remove (right- down corner). note: if lamp icon not appear after open, goto view , select toolbar checkbox. 2.5.1 add new nic vm: virt-manager > select vm > open > click lamp icon > add hardware > network > network source: bridge br0: host device eth0 mac address: checked, leave suggested one device model: hypervisor default or 1 know vm-guest has driver for.
finish 2.5.2 run vm , test in vm's gnome terminal
ping vm # ping host1 etc...
2.6 repeat steps in host2 bare metal, step 1 , subsequent 2.3 name : br0 start mode: none activate now: checked on ip settings: leave dhcp or configure, mode: static address: 192.168.0.10/27 bridge settings: turn stp off choose interface(s)to bridge eth0 checked 2.7 adjust host2 vms network nic settings according 2.5
conclusion: clean starting situation, virt-manager set bridge , network connection router successfully, in few clicks.
Comments
Post a Comment