On Wed, Sep 28, 2016 at 06:03:21PM +0200, Martin Wilck wrote:
On Wed, 2016-09-28 at 16:41 +0100, Daniel P. Berrange wrote:
Anyone who cares about VMs having the same IP address after resuming from suspend *must* configure persistent DHCP mappings for their guests. Relying on automatic assignment will always fail in the end, may be not immediately, may be not often, but it *will* fail at some point, usually at the worst possible time.
I believe that setting "dhcp-authoritative" will be a major improvement for many setups. Without it, VMs are *never* able to reacquire their expired lease. With it, reacquiring the lease would work most of the time (as far as I'm concerned, practically always). I reckon the dnsmasq man page recommends it for a reason "when dnsmasq is definitely the only DHCP server on a network".
That certainly matches our deployment model for dnsmasq, so unless there's a obvious downside to it, it seems reasonable to add that. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://entangle-photo.org -o- http://search.cpan.org/~danberr/ :|