vboxmanager hostonlyif create --name ""

[Sauraus]

To enable the naming of 'hostonlyif' the create command needs to have a --name option such that (especially) on Windows host systems the name doesn't default to "VirtualBox Host-Only Ethernet Adapter", but instead can be set to something more useful.

[ambrop7]

I would really like to see this feature on Linux. It will be useful for automatic creation of host-only adapters from OS startup scripts.

Currently I'm creating an interface and parsing the vboxmanage output to get the name. But for some reason something seems to be keeping the old interfaces around, and I'm already at vboxnet6... Would be nice if I could tell it to create vboxnet0 explicitly (or not if it already exists).

[derks]

I'm surprised this is open after 3 years without any comment, or other users making the request. It would be extremely helpful in automated environments to be able to control the name of created host only networks.

For our use case, every "environment" gets three dedicated networks. As the previous user mentioned we create the networks with vboxmanage hostonlyif create and then grep the output for the interface name. We then have to store that interface name somehow, so that we can recall it later on... for example when calling vboxmanage hostonlyif remove <name>. This works, but is really not ideal as, if the networks are removed externally... another "environment" might create the same networks where both think they own the networks (and might collide).

Ideally, we should be able to do: vboxmanage hostonlyif create --name 'vboxnet-some-custom-identifier'... for example: vboxnet-env12345-job12.345

Is there a technical reason why this is not already a feature?

[MangoCat]

Concur - I would also like to be able to name my hostonly interfaces, instead of simply having them appear in sequence, for the same reasons as stated above.