VBoxManage createvm --name foo1 --register
VBoxManage modifyvm foo1 --ostype Debian --memory 512
VBoxManage modifyvm foo1 --nic1 hostonly --nictype1 82540EM --hostonlyadapter1 'vboxnet0'
VBoxManage modifyvm foo1 --nic2 bridged --nictype2 82540EM --bridgeadapter1 'eth0'
VBoxManage startvm foo1
Waiting for VM "foo1" to power on...
VBoxManage: error: Failed to open/create the internal network 'HostInterfaceNetworking-' (VERR_INVALID_PARAMETER).
VBoxManage: error: Failed to attach the network LUN (VERR_INVALID_PARAMETER)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component Console, interface IConsole, callee
When I look at the VM in the GUI, I see that the second adapter is not marked as being for eth0. However, if I click on the Settings button, then OK in the dialog without touching any of the settings, I can see that the second adapter is marked as eth0 and the VM starts up just fine, both from the GUI and from the command line.
Has anyone else hit this bug? If so, is there a way around it?