If a KVM machine at my ThinkPad previously was configured to get a 169.x.x.x address, then at the following reboot of the KVM guest the eth0 interface needs few seconds more to reconfigure it to get a 192.x.x.x address (KVCM guest NIC is confgiured to "Bridge br0(Host device tap0)", and Device model "virtio"). I can circumvent it here with 'dhcpc_eth0="-t 10"') for the KVM guest but do wonder if it would make sense for dhcpcd to wait a little bit longer ?
Hi Toralf. I'm not entirely sure what you're asking for, but the semantics for --timeout and --reboot have changed slightly in dhcpcd-6.6.7. Why don't you try that and if it still doesn't work for you try re-phrasing your question a little better :)
a - thx for pointing me th the --reboot option
