virtualbox.org

Btw, the ticket should say "NAT DHCP", not "VBox DHCP", as VirtualBox has several different DHCP services. Oh, my issue is for host-only network. Now I've noticed that original issue is with NAT. I guess the root cause will be the same. I'll definitely mention that in bug report.

That's what I expected. Isn't it clearly a bug in Vbox's DHCP server? Is it reported? Unfortunately, restarting vbox service is not solution for me. My workaround is to have forever-running VM with static IP that has DHCP server installed and turn off vbox's DHCP. This works well and is not overhead...

Issue is, that lease time seems not working. I think it's hardcoded 20 minutes in virtualbox DHCP, but after a much longer time after VM with some particular IP was deleted, it is still not assigned to the new VM so you end up stuck with no IP. I run automated tests in virtualbox. I have jenkins ins...

I think the issue is properly described by first @JJon post. I can provide more info, but I don't know what. What else do you need to know?

Hi, have you solved the issue? I'm meeting the same now.