https://bugzilla.novell.com/show_bug.cgi?id=854165 https://bugzilla.novell.com/show_bug.cgi?id=854165#c1 --- Comment #1 from Bruno Friedmann 2013-12-07 15:05:40 UTC --- Still true with the last update to 1.2x zypper se -si libvirt Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository --+---------------------------------+---------+-------------+--------+--------------- i | libvirt | package | 1.2.0-353.1 | x86_64 | virtualization i | libvirt-client | package | 1.2.0-353.1 | x86_64 | virtualization i | libvirt-daemon | package | 1.2.0-353.1 | x86_64 | virtualization i | libvirt-daemon-config-nwfilter | package | 1.2.0-353.1 | x86_64 | virtualization i | libvirt-daemon-driver-interface | package | 1.2.0-353.1 | x86_64 | virtualization i | libvirt-daemon-driver-libxl | package | 1.2.0-353.1 | x86_64 | virtualization i | libvirt-daemon-driver-lxc | package | 1.2.0-353.1 | x86_64 | virtualization i | libvirt-daemon-driver-network | package | 1.2.0-353.1 | x86_64 | virtualization i | libvirt-daemon-driver-nodedev | package | 1.2.0-353.1 | x86_64 | virtualization i | libvirt-daemon-driver-nwfilter | package | 1.2.0-353.1 | x86_64 | virtualization i | libvirt-daemon-driver-qemu | package | 1.2.0-353.1 | x86_64 | virtualization i | libvirt-daemon-driver-secret | package | 1.2.0-353.1 | x86_64 | virtualization i | libvirt-daemon-driver-storage | package | 1.2.0-353.1 | x86_64 | virtualization i | libvirt-daemon-driver-uml | package | 1.2.0-353.1 | x86_64 | virtualization i | libvirt-daemon-driver-vbox | package | 1.2.0-353.1 | x86_64 | virtualization i | libvirt-daemon-driver-xen | package | 1.2.0-353.1 | x86_64 | virtualization i | libvirt-daemon-lxc | package | 1.2.0-353.1 | x86_64 | virtualization i | libvirt-daemon-qemu | package | 1.2.0-353.1 | x86_64 | virtualization i | libvirt-daemon-uml | package | 1.2.0-353.1 | x86_64 | virtualization i | libvirt-daemon-vbox | package | 1.2.0-353.1 | x86_64 | virtualization i | libvirt-daemon-xen | package | 1.2.0-353.1 | x86_64 | virtualization i | libvirt-glib-1_0-0 | package | 0.1.7-37.3 | x86_64 | virtualization i | libvirt-python | package | 1.2.0-1.2 | x86_64 | virtualization i | typelib-1_0-LibvirtGConfig-1_0 | package | 0.1.7-37.3 | x86_64 | virtualization i | typelib-1_0-LibvirtGLib-1_0 | package | 0.1.7-37.3 | x86_64 | virtualization i | typelib-1_0-LibvirtGObject-1_0 | package | 0.1.7-37.3 | x86_64 | virtualization -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=854165 https://bugzilla.novell.com/show_bug.cgi?id=854165#c3 --- Comment #3 from Bruno Friedmann 2013-12-11 17:46:09 UTC --- Okay then here's some more informations The libvirtd/kvm virtual guest are hosted on a all-in-one-multipurpose server which act as gateway (both ipv4/ipv6 sixxs tunnel on sit1) I've radvd, dhcpd, named (on both side internal and external view) + openvpn on the external link I've no avahi installed, all the vm are linked to the br0 interface The iptables are managed with shorewall. ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 90:2b:34:d2:60:0e brd ff:ff:ff:ff:ff:ff inet 192.168.23.5/24 brd 192.168.23.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::922b:34ff:fed2:600e/64 scope link valid_lft forever preferred_lft forever 3: eth1: mtu 1500 qdisc pfifo_fast master br0 state UP group default qlen 1000 link/ether 68:05:ca:11:33:c7 brd ff:ff:ff:ff:ff:ff inet6 fe80::6a05:caff:fe11:33c7/64 scope link valid_lft forever preferred_lft forever 4: br0: mtu 1500 qdisc noqueue state UP group default link/ether 68:05:ca:11:33:c7 brd ff:ff:ff:ff:ff:ff inet 10.26.8.1/25 brd 10.26.8.127 scope global br0 valid_lft forever preferred_lft forever inet6 2001:1620:f7c::1/64 scope global valid_lft forever preferred_lft forever inet6 fe80::6a05:caff:fe11:33c7/64 scope link valid_lft forever preferred_lft forever 5: sit0: <NOARP> mtu 1480 qdisc noop state DOWN group default link/sit 0.0.0.0 brd 0.0.0.0 6: sit1: mtu 1280 qdisc noqueue state UNKNOWN group default link/sit 192.168.23.5 peer 213.144.148.74 inet6 2001:1620:f00:80::2/64 scope global valid_lft forever preferred_lft forever inet6 fe80::c0a8:1705/128 scope link valid_lft forever preferred_lft forever 7: tun0: mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 100 link/none inet 192.168.26.1 peer 192.168.26.2/32 scope global tun0 valid_lft forever preferred_lft forever a vtunXXX is added when a vm runs. ip ro default via 192.168.23.1 dev eth0 blackhole 10.0.0.0/8 10.26.8.0/25 dev br0 proto kernel scope link src 10.26.8.1 127.0.0.0/8 dev lo scope link 169.254.0.0/16 dev eth0 scope link blackhole 172.16.0.0/12 blackhole 192.168.0.0/16 192.168.23.0/24 dev eth0 proto kernel scope link src 192.168.23.5 192.168.26.0/24 via 192.168.26.2 dev tun0 192.168.26.2 dev tun0 proto kernel scope link src 192.168.26.1 yoda:~ # ip6 ro 2001:1620:f00:80::/64 dev sit1 proto kernel metric 256 2001:1620:f7c::/64 dev br0 proto kernel metric 256 fe80::/64 dev eth0 proto kernel metric 256 fe80::/64 dev eth1 proto kernel metric 256 fe80::/64 dev br0 proto kernel metric 256 default via 2001:1620:f00:80::1 dev sit1 metric 1024 If any other information could be usefull, just ping -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=854165 https://bugzilla.novell.com/show_bug.cgi?id=854165#c5 --- Comment #5 from James Fehlig 2013-12-13 23:07:22 UTC --- Karol noted on IRC that down/up the bridged interface caused the log spamming to stop. E.g. # route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 151.155.147.254 0.0.0.0 UG 0 0 0 br0 default * 0.0.0.0 U 1002 0 0 enp12s2f0 loopback * 255.0.0.0 U 0 0 0 lo 151.155.144.0 * 255.255.252.0 U 0 0 0 br0 link-local * 255.255.0.0 U 0 0 0 enp12s2f0 192.168.122.0 * 255.255.255.0 U 0 0 0 virbr0 # ifconfig enp12s2f0 down; ifconfig enp12s2f0 up # route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 151.155.147.254 0.0.0.0 UG 0 0 0 br0 loopback * 255.0.0.0 U 0 0 0 lo 151.155.144.0 * 255.255.252.0 U 0 0 0 br0 192.168.122.0 * 255.255.255.0 U 0 0 0 virbr0 No more log spamming. But after rebooting, the routes for iface enp12s2f0 reappear, and we are back to log spamming. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=854165 https://bugzilla.novell.com/show_bug.cgi?id=854165#c7 --- Comment #7 from Bruno Friedmann 2013-12-15 15:36:46 UTC --- About the routing and adresses : I've the following when a vm is activated (the vm get internally the 10.26.8.4/25 ipv4 and get its normal gateway 10.26.8.1 like any other device on the network. ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 90:2b:34:d2:60:0e brd ff:ff:ff:ff:ff:ff inet 192.168.23.5/24 brd 192.168.23.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::922b:34ff:fed2:600e/64 scope link valid_lft forever preferred_lft forever 3: eth1: mtu 1500 qdisc pfifo_fast master br0 state UP group default qlen 1000 link/ether 68:05:ca:11:33:c7 brd ff:ff:ff:ff:ff:ff inet6 fe80::6a05:caff:fe11:33c7/64 scope link valid_lft forever preferred_lft forever 4: br0: mtu 1500 qdisc noqueue state UP group default link/ether 68:05:ca:11:33:c7 brd ff:ff:ff:ff:ff:ff inet 10.26.8.1/25 brd 10.26.8.127 scope global br0 valid_lft forever preferred_lft forever inet6 2001:1620:f7c::1/64 scope global valid_lft forever preferred_lft forever inet6 fe80::6a05:caff:fe11:33c7/64 scope link valid_lft forever preferred_lft forever 5: sit0: <NOARP> mtu 1480 qdisc noop state DOWN group default link/sit 0.0.0.0 brd 0.0.0.0 6: sit1: mtu 1280 qdisc noqueue state UNKNOWN group default link/sit 192.168.23.5 peer 213.144.148.74 inet6 2001:1620:f00:80::2/64 scope global valid_lft forever preferred_lft forever inet6 fe80::c0a8:1705/128 scope link valid_lft forever preferred_lft forever 7: tun0: mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 100 link/none inet 192.168.26.1 peer 192.168.26.2/32 scope global tun0 valid_lft forever preferred_lft forever 13: vnet0: mtu 1500 qdisc pfifo_fast master br0 state UNKNOWN group default qlen 500 link/ether fe:54:00:5d:32:d2 brd ff:ff:ff:ff:ff:ff inet6 fe80::fc54:ff:fe5d:32d2/64 scope link valid_lft forever preferred_lft forever yoda:~/bin # ip ro default via 192.168.23.1 dev eth0 blackhole 10.0.0.0/8 10.26.8.0/25 dev br0 proto kernel scope link src 10.26.8.1 127.0.0.0/8 dev lo scope link 169.254.0.0/16 dev eth0 scope link blackhole 172.16.0.0/12 blackhole 192.168.0.0/16 192.168.23.0/24 dev eth0 proto kernel scope link src 192.168.23.5 192.168.26.0/24 via 192.168.26.2 dev tun0 192.168.26.2 dev tun0 proto kernel scope link src 192.168.26.1 yoda:~/bin # ip -6 or Object "or" is unknown, try "ip help". yoda:~/bin # ip -6 ro 2001:1620:f00:80::/64 dev sit1 proto kernel metric 256 2001:1620:f7c::/64 dev br0 proto kernel metric 256 fe80::/64 dev eth0 proto kernel metric 256 fe80::/64 dev eth1 proto kernel metric 256 fe80::/64 dev br0 proto kernel metric 256 fe80::/64 dev vnet0 proto kernel metric 256 default via 2001:1620:f00:80::1 dev sit1 metric 1024 nothing different from when nothing runs I've by default the default virsh networking off on the server ( the ipv4 nated 192.168.122.0/24 network) as I don't use it. In the example you are using it, it's a virtual bridge (vbr0) I've vnet0 linked to br0. hope this help to clarify or document the situation. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=854165 https://bugzilla.novell.com/show_bug.cgi?id=854165#c9 --- Comment #9 from James Fehlig 2013-12-19 03:05:33 UTC --- (In reply to comment #8)

ifcfg-eth0: ----------- BOOTPROTO='static' STARTMODE='manual'

I changed STARTMODE from 'auto' to 'manual' in the ifcfg file for the bridge port interface and no longer see the link-local routes nor the log file spamming, even after rebooting the host. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=854165 https://bugzilla.novell.com/show_bug.cgi?id=854165#c11 --- Comment #11 from Bruno Friedmann 2013-12-19 12:27:34 UTC --- I've changed the eth1 to manual start for my br0 I don't have anymore the link-local but with last build nothing has changed the spam is still there. zypper se -si libvirt Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository --+---------------------------------+---------+-------------+--------+--------------- i | libvirt | package | 1.2.0-353.3 | x86_64 | virtualization i | libvirt-client | package | 1.2.0-353.3 | x86_64 | virtualization i | libvirt-daemon | package | 1.2.0-353.3 | x86_64 | virtualization i | libvirt-daemon-config-nwfilter | package | 1.2.0-353.3 | x86_64 | virtualization i | libvirt-daemon-driver-interface | package | 1.2.0-353.3 | x86_64 | virtualization i | libvirt-daemon-driver-libxl | package | 1.2.0-353.3 | x86_64 | virtualization i | libvirt-daemon-driver-lxc | package | 1.2.0-353.3 | x86_64 | virtualization i | libvirt-daemon-driver-network | package | 1.2.0-353.3 | x86_64 | virtualization i | libvirt-daemon-driver-nodedev | package | 1.2.0-353.3 | x86_64 | virtualization i | libvirt-daemon-driver-nwfilter | package | 1.2.0-353.3 | x86_64 | virtualization i | libvirt-daemon-driver-qemu | package | 1.2.0-353.3 | x86_64 | virtualization i | libvirt-daemon-driver-secret | package | 1.2.0-353.3 | x86_64 | virtualization i | libvirt-daemon-driver-storage | package | 1.2.0-353.3 | x86_64 | virtualization i | libvirt-daemon-driver-uml | package | 1.2.0-353.3 | x86_64 | virtualization i | libvirt-daemon-driver-vbox | package | 1.2.0-353.3 | x86_64 | virtualization i | libvirt-daemon-driver-xen | package | 1.2.0-353.3 | x86_64 | virtualization i | libvirt-daemon-lxc | package | 1.2.0-353.3 | x86_64 | virtualization i | libvirt-daemon-qemu | package | 1.2.0-353.3 | x86_64 | virtualization i | libvirt-daemon-uml | package | 1.2.0-353.3 | x86_64 | virtualization i | libvirt-doc | package | 1.2.0-353.3 | x86_64 | virtualization i | libvirt-glib-1_0-0 | package | 0.1.7-37.3 | x86_64 | virtualization i | libvirt-python | package | 1.2.0-3.1 | x86_64 | virtualization i | typelib-1_0-LibvirtGConfig-1_0 | package | 0.1.7-37.3 | x86_64 | virtualization i | typelib-1_0-LibvirtGLib-1_0 | package | 0.1.7-37.3 | x86_64 | virtualization i | typelib-1_0-LibvirtGObject-1_0 | package | 0.1.7-37.3 | x86_64 | virtualization Dec 19 13:20:06 yoda.labaroche.ioda.net libvirtd[20856]: setting addrs not yet implemented for 10 Dec 19 13:20:06 yoda.labaroche.ioda.net libvirtd[20856]: setting addrs not yet implemented for 10 Dec 19 13:20:06 yoda.labaroche.ioda.net libvirtd[20856]: Unable to find interface index in netlink route message Dec 19 13:20:06 yoda.labaroche.ioda.net libvirtd[20856]: Unable to find interface index in netlink route message Dec 19 13:20:06 yoda.labaroche.ioda.net libvirtd[20856]: Unable to find interface index in netlink route message Dec 19 13:20:06 yoda.labaroche.ioda.net libvirtd[20856]: setting addrs not yet implemented for 10 Dec 19 13:20:06 yoda.labaroche.ioda.net libvirtd[20856]: setting addrs not yet implemented for 10 Dec 19 13:20:06 yoda.labaroche.ioda.net libvirtd[20856]: Unable to find interface index in netlink route message Dec 19 13:20:06 yoda.labaroche.ioda.net libvirtd[20856]: Unable to find interface index in netlink route message Dec 19 13:20:06 yoda.labaroche.ioda.net libvirtd[20856]: Unable to find interface index in netlink route message Dec 19 13:20:06 yoda.labaroche.ioda.net libvirtd[20856]: setting addrs not yet implemented for 10 each time I use virt-manager locally or remotely using virsh console works ... so the problem is the interaction between virt-manager and the libvirt daemon. ----- There's also a new phenomena : systemctl restart libvirtd.service is taking 120 second to restart I've determined this is the timeout of udevadm settle during a restart I can see this systemctl status libvirtd.service libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled) Active: deactivating (stop-sigterm) since Thu, 2013-12-19 13:14:59 CET; 26s ago Main PID: 20418 (libvirtd) CGroup: name=systemd:/system/libvirtd.service ├ 20418 /usr/sbin/libvirtd --listen └ 20698 /sbin/udevadm settle Dec 19 13:09:55 yoda.labaroche.ioda.net systemd[1]: Unit libvirtd.service entered failed state Dec 19 13:09:55 yoda.labaroche.ioda.net systemd[1]: Starting Virtualization daemon... Dec 19 13:09:55 yoda.labaroche.ioda.net systemd[1]: Started Virtualization daemon. Dec 19 13:09:55 yoda.labaroche.ioda.net libvirtd[20418]: libvirt version: 12.0 Dec 19 13:09:55 yoda.labaroche.ioda.net libvirtd[20418]: Configured security driver "none" disables default policy to create confined guests Dec 19 13:14:01 yoda.labaroche.ioda.net libvirtd[20418]: End of file while reading data: Input/output error Dec 19 13:14:59 yoda.labaroche.ioda.net systemd[1]: Stopping Virtualization daemon... Dec 19 13:14:59 yoda.labaroche.ioda.net systemd[1]: Cannot add dependency job for unit xencommons.service, ignoring: Unit xencommons.service failed to load: No such file or ...or details. Dec 19 13:14:59 yoda.labaroche.ioda.net systemd[1]: Stopping Virtualization daemon... Dec 19 13:16:29 yoda.labaroche.ioda.net systemd[1]: libvirtd.service stopping timed out. Killing. Dec 19 13:16:29 yoda.labaroche.ioda.net systemd[1]: libvirtd.service: main process exited, code=killed, status=9/KILL Dec 19 13:16:29 yoda.labaroche.ioda.net systemd[1]: Unit libvirtd.service entered failed state Dec 19 13:16:29 yoda.labaroche.ioda.net systemd[1]: Starting Virtualization daemon... Dec 19 13:16:29 yoda.labaroche.ioda.net systemd[1]: Started Virtualization daemon. Test on a simple laptop, without a bridge and using dnsmask and default nated network just work correctly. On my server the default network is disabled (not used so I disable it), could it be the root cause of the messages ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=854165 https://bugzilla.novell.com/show_bug.cgi?id=854165#c13 --- Comment #13 from Bruno Friedmann 2013-12-19 21:08:52 UTC --- Jim the sit0/sit1 are my main ipv6 tunnel and are heavily used. so no way to stop or remove them. But what I don't understand (or was lost in my mind), this configuration was working perfectly before 1.2x enter the repository. (it's just a reminder) running udevadm settle in root console is just 0.004s I've try to activate the default network, it activate a vibr0 but nothing stop the spamming log of virt-manager. I can't find a reason why the gui is failing, using virsh console just work, even the remote ssh one. So I would recenter the bug around virt-manager gui only Or I'm wrong? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=854165 https://bugzilla.novell.com/show_bug.cgi?id=854165#c15 Bruno Friedmann changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|bruno@ioda-net.ch | --- Comment #15 from Bruno Friedmann 2013-12-20 09:30:40 UTC --- Environment one : openSUSE_12.3 + kernel-stable 3.12.5 + all virt coming from repo virtualization. The spamming bombing message occur only if libvirt version is 1.2+ and only when used with virt-manager 0.10 connecting the local or remote libvirtd (ssh+qemu) If I use virsh console even with remote, I don't get spamming in log. That's why I narrow down the trouble to a bad interaction between virt-manager & libvirtd. This server has double stack networking ipv6 + ipv4 enable and fully operationnal eth0 is wan interface (all traffic routed from the router) 192.168.23.5/24 sit0 (dummy sit) sit1 (end point tunnel for sixxs ipv6 connectivity) br0 enslave eth1 and has ipv4 10.26.8.0/25 network + ipv6 2001:1620:f7c::1/64 tun0 is the openvpn endpoint 192.168.26.0/24 iptables & ip6tables are managed by shorewall(6) Before 1.2x libvirt the configuration was working well. I've now access to a 13.1 qemu/kvm server which is less complicated : openSUSE_13.1 + kernel:stable 3.12.5 + virt from repo virtualization This one has a br0 on top of a bond0 enslaving eth1/eth2 with only one network ipv4 and local ipv6 Connecting to this host, with the "faulty" virt-manager doesn't show spamming log. Thus my assumption is partially wrong, there's a case certainly linked to the number and type of network interface that drive the spamming with virt-manager. So it's not reproducible easily. So what can we try ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=854165 https://bugzilla.novell.com/show_bug.cgi?id=854165#c17 James Fehlig changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |mt@suse.com --- Comment #17 from James Fehlig 2014-01-24 21:37:51 UTC --- I'm not really sure what to do here from the libvirt side. Marius, what is your take on squelching these netcontrol messages? Thanks! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=854165 https://bugzilla.novell.com/show_bug.cgi?id=854165#c19 James Fehlig changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |schwab@suse.com --- Comment #19 from James Fehlig 2014-06-04 15:45:28 UTC --- *** Bug 869366 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=869366 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=854165 Aaron Williams changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aaronw@doofus.org --- Comment #21 from Aaron Williams --- I am seeing the same problem. It's flooding /var/log/messages -- You are receiving this mail because: You are on the CC list for the bug.