Vagrant private_network auto_configure false interface cleanup on reload

Vagrant private_network auto_configure false interface cleanup on reload

Goal: confirm whether repeated reload cycles leave stale private network interfaces on the host when auto_configure: false is set.

auto_configure: false is intended to delegate IP configuration to the guest, but the teardown boundary during a non-destructive reload is not clearly defined. It is uncertain whether Vagrant removes the host-only adapter, whether the provider retains it, or whether behavior differs between VirtualBox and libvirt.

Assuming Vagrant 2.4.x, the missing constraint is cleanup responsibility among Vagrant, the provider, and the guest OS.

• Does Vagrant remove the private network adapter during reload when auto_configure is false?
• Is interface release handled by the provider or the guest when the machine is not destroyed?
• Does this behavior differ between VirtualBox and libvirt?