search for: kvmh2

....51.1 eth1/aaa.bbb.ccc.151 <-------------> | | kvmh1 br1/aaa.bbb.ccc.51 | |---> br0/192.168.51.1 | X | kvmh2 |---> br0/192.168.52.1 | br1/aaa.bbb.ccc.52 | | kvmh2g1 eth0/192.168.52.1 | eth1/aaa.bbb.ccc.251 <-------------> |...

...have all of the kvm guests on both hosts, together with the br0 bridge on both hosts, configured with addresses on the same a.b.c.0/24 network then will all communication on a.b.c.0/24 pass over br0 if the target address is on the other host? kvmh1g1 eth0=192.168.51.100 kvmh1 br0=192.168.51.41 kvmh2 br0=192.168.51.42 kvmh2g1 eth0=192.168.51.200 In other words, with the address configuration given above, will traffic from 192.168.51.200 reach 192.168.51.100 via the cross-over cable between 192.168.51.42/192.168.51.41? -- *** e-Mail is NOT a SECURE channel *** Do...

...t;libvir: XML-RPC error : authentication requirederror: failed to connect to the hypervisor* The SSH authentication to hypervisor host 9.113.51.247 has already been established. *kvmh911351246:~ # ssh root at 9.113.51.247 <root at 9.113.51.247>Last login: Tue Jun 3 11:31:56 2014 from scm-kvmh2-rhel6SLES11-51-247:~ #* Hence the cause of the authentication failure is not clear. The second connection to another SLES 11.3 host looks like *virsh # connect qemu+ssh://9.121.58.19:22/system <http://9.121.58.19:22/system>bash: socat: command not foundlibvir: Remote error : socket clos...

...stem>libvir: XML-RPC error : authentication requirederror: failed to connect to the hypervisor* The SSH authentication to hypervisor host 9.113.51.247 has already been established. *kvmh911351246:~ # ssh root@9.113.51.247 <root@9.113.51.247>Last login: Tue Jun 3 11:31:56 2014 from scm-kvmh2-rhel6 SLES11-51-247:~ #* Hence the cause of the authentication failure is not clear. The second connection to another SLES 11.3 host looks like *virsh # connect qemu+ssh://9.121.58.19:22/system <http://9.121.58.19:22/system> bash: socat: command not foundlibvir: Remote error : socket cl...