[libvirt] iptables complains about a bad rule

[Laine Stump]

  On 10/27/2010 02:02 PM, Matthias Bolte wrote:
> With libvirt from git on Ubuntu 10.04 I get this 3 errors (actually 2
> warnings an 1 error) when starting libvirtd:
>
> 23:15:45.221: error : virRunWithHook:855 : internal error
> '/sbin/iptables --table mangle --delete POSTROUTING --out-interface
> virbr0 --protocol udp --destination-port 68 --jump CHECKSUM
> --checksum-fill' exited with non-zero status 2 and signal 0: iptables
> v1.4.4: unknown option `--checksum-fill'
> Try `iptables -h' or 'iptables --help' for more information.
>
> 23:15:45.238: error : virRunWithHook:855 : internal error
> '/sbin/iptables --table filter --delete INPUT --in-interface virbr0
> --protocol udp --destination-port 69 --jump ACCEPT' exited with
> non-zero status 1 and signal 0: iptables: Bad rule (does a matching
> rule exist in that chain?).
>
> 23:15:45.275: error : virRunWithHook:855 : internal error
> '/sbin/iptables --table mangle --insert POSTROUTING --out-interface
> virbr0 --protocol udp --destination-port 68 --jump CHECKSUM
> --checksum-fill' exited with non-zero status 2 and signal 0: iptables
> v1.4.4: unknown option `--checksum-fill'
> Try `iptables -h' or 'iptables --help' for more information.
>
> The first and the last one just indicate that my iptables here is too
> old to know about --checksum-fill, but what about the second one?

Ah - that one is harmless too, but is a bonafide bug - when starting the 
network we only add the rule to allow port 69 if the network def has a 
non-empty tftproot, but when destroying the network we try to remove it 
no matter what.

I'm following this message with a patch to remedy the problem.