Description of problem:See above


Version-Release number of selected component (if applicable):libvirt.x86_64 0.8.3-10.fc14


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results: libvirt spawns an instance of dnsmasq to handle the bridge from VM's to host. That instance has a finite lease time, about 25 min. consequently, I am getting lots of messages in my syslog file about lease renewals, floods that file, washed other possibly important stuff out of view of a tail, etc. The lease time should be infinite, or at least longer than 25 min.


Expected results:longer lease times, maybe daily or weekly ....


Additional info: example, from a couple of days back:


Nov  8 07:48:19 Q6600 dnsmasq-dhcp[1980]: DHCPREQUEST(virbr0) 192.168.122.213 52:54:00:a4:98:a3 
Nov  8 07:48:19 Q6600 dnsmasq-dhcp[1980]: DHCPACK(virbr0) 192.168.122.213 52:54:00:a4:98:a3 
Nov  8 08:14:14 Q6600 dnsmasq-dhcp[1980]: DHCPREQUEST(virbr0) 192.168.122.213 52:54:00:a4:98:a3 
Nov  8 08:14:14 Q6600 dnsmasq-dhcp[1980]: DHCPACK(virbr0) 192.168.122.213 52:54:00:a4:98:a3 
Nov  8 08:35:26 Q6600 dnsmasq-dhcp[1980]: DHCPREQUEST(virbr0) 192.168.122.213 52:54:00:a4:98:a3 
Nov  8 08:35:26 Q6600 dnsmasq-dhcp[1980]: DHCPACK(virbr0) 192.168.122.213 52:54:00:a4:98:a3 
Nov  8 08:58:10 Q6600 dnsmasq-dhcp[1980]: DHCPREQUEST(virbr0) 192.168.122.213 52:54:00:a4:98:a3 
Nov  8 08:58:10 Q6600 dnsmasq-dhcp[1980]: DHCPACK(virbr0) 192.168.122.213 52:54:00:a4:98:a3

these are pretty much useless, unimportant, longer leases would cut them down ....