[vbox-dev] Updating network interfaces list speed-up

Alexey Eromenko al4321 at gmail.com
Mon Apr 13 19:10:10 UTC 2015

How to create 80 "vboxnet<XX>" interfaces ?
I have not found any VboxManage command to do that.

User Manual only shows how to attach a VM to an existing vboxnet interface.

Like this:
VBoxManage modifyvm "HostifVM" --hostonlyadapter1 hostif0

But VM cannot start, because <hostif0> not found.

On Mon, Apr 13, 2015 at 3:23 AM, a.urakov at drweb.com <a.urakov at drweb.com> wrote:
> Hello Mr. Eromenko,
> thank you for porting this patch on beta version.
> As for performance
> Command to clone 70 VMs:
> $ for i in `seq 1 70`; do VBoxManage clonevm "ZeroVM" --mode all
> --register --name "ZeroVM Clone $i"; done
> 70 VMs, Host-only-interface mode:
> I think it can happen because all your VMs have only one interface vboxnet0
> (if I'm not mistaken?). In our case we have separate interfaces for every VM
> (vboxnet1..80), and all of them are in /etc/network/interfaces, so host
> interfaces list updating takes significantly longer time.
> unpatched:
> 2:30 min boot. -- 2:33 min (2nd run)
> patched: (slower by margin of error)
> 2:35 min boot. .. 2:34 (2nd run)
> What does this time mean? If I understand you right, you start VMs without
> OSes, but for simple VM starting this time looks too long...
> Timed manually from smartphone, so 1 second mistake is possible. (not
> via host OS timer)
> We use time field in VBoxSVC log for chronometry (we attached VBoxSVC.logs
> to first letter). This way you can measure execution time for specific
> procedure (FindHostNetworkInterfaceByName in our case) and see how this
> patch affects this.
> Regards,
> Alexander
> _______________________________________________
> vbox-dev mailing list
> vbox-dev at virtualbox.org
> https://www.virtualbox.org/mailman/listinfo/vbox-dev

-Alexey Eromenko "Technologov"

More information about the vbox-dev mailing list