On 03/24/2013 01:05 PM, Frank Murphy wrote: > On Sun, 24 Mar 2013 12:29:26 +0000 > Frank Murphy <[email protected]> wrote: > > > Can now ping both nics in the host. > But that as far as it goes. > Update F18 with all virt\qemu updates-testing. > No joy am unsure if firewalld problem, > though I have a checkmark against libvirt in public zone. > > ~$ dmesg | grep virbr0 > [ 54.567869] device virbr0-nic entered promiscuous mode > [ 54.688887] virbr0: topology change detected, propagating > [ 54.689764] virbr0: port 1(virbr0-nic) entered forwarding state > [ 54.690613] virbr0: port 1(virbr0-nic) entered forwarding state > [ 54.749869] virbr0: port 1(virbr0-nic) entered disabled state > > Mar 24 23:45:45 testvm kernel: [ 54.567869] device virbr0-nic > entered promiscuous mode > Mar 24 23:45:45 testvm kernel: [ 54.688887] virbr0: topology change > detected, propagating > Mar 24 23:45:45 testvm kernel: [ 54.689764] virbr0: port > 1(virbr0-nic) entered forwarding state > Mar 24 23:45:45 testvm kernel: [ 54.690613] virbr0: port > 1(virbr0-nic) entered forwarding state > Mar 24 23:45:45 testvm avahi-daemon[808]: Joining mDNS multicast > group on interface virbr0.IPv4 with address 192.168.1.1. > Mar 24 23:45:45 testvm avahi-daemon[808]: New relevant interface > virbr0.IPv4 for mDNS. > Mar 24 23:45:45 testvm avahi-daemon[808]: Registering new address > record for 192.168.1.1 on virbr0.IPv4. > Mar 24 23:45:45 testvm kernel: [ 54.749869] virbr0: port > 1(virbr0-nic) entered disabled state >
firewalld should be fairly isolated I believe. you can try yum remove firewalld and reboot, and see if that makes any difference. - Cole _______________________________________________ virt mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/virt
