virtualbox.org

I started having an issue today where i am receiving the following error on any virtual machine that uses hostonly

Failed to start the virtual machine

Failed to open/create the internal network
'HostIntefaceNetworking-Virtualbox Host-Only Ethernet Adapter'
(VERR_INTNET_INCOMPATIBLE_TRUNK)

Unknown error creating VM
(VERR_INTNET_INCOMPATIBLE_TRUNK)


I've tried removing / reconfiguring the interface, removing the networking info from the xml and re-establishing it and still get the same error.

This is on a Windows 7 Ultimate 64bit host
VM's are Windows 7 and WIndows 2003

VBox 3.1.4

The tail of the logfile shows this:
00:00:01.744 IntNet#0: szNetwork={HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter} enmTrunkType=4 szTrunk={\DEVICE\{4131DF7D-BDD0-4990-BD66-E2A24A638002}} fFlags=0x0 cbRecv=223232 cbSend=36864
00:00:01.744 VMSetError: D:\tinderbox\win-3.1\src\VBox\Devices\Network\DrvIntNet.cpp(1071) drvIntNetConstruct
00:00:01.744 VMSetError: Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter'
00:00:01.744 PDM: Failed to construct 'pcnet'/0! VERR_INTNET_INCOMPATIBLE_TRUNK (-3603) - The network already exists with a different trunk configuration.
00:00:01.932 VMSetError: D:\tinderbox\win-3.1\src\VBox\VMM\VM.cpp(323) VMR3Create
00:00:01.932 VMSetError: Unknown error creating VM
00:00:01.933 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={6375231a-c17c-464b-92cb-ae9e128d71c3} aComponent={Console} aText={Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_INCOMPATIBLE_TRUNK).
00:00:01.933 Unknown error creating VM (VERR_INTNET_INCOMPATIBLE_TRUNK)} aWarning=false, preserve=false
00:00:01.935 Power up failed (vrc=VERR_INTNET_INCOMPATIBLE_TRUNK, rc=E_FAIL (0X80004005))

I was able to fix it...

I had to remove the interface then reboot the host.

after that re-adding it and i no longer get that error and the network works as I expected

SO, because I moved my network card to a different slot, now I have to:

take my computer apart again,
remove the card,
restart windows,
let windows figure out I don't have a network card
start VB, let VB figure out I don't have a network card (do I have to actually start the virtual machine, or is starting virtual box enough?)
Shutdown windows,
reinstall my network card,
start windows again (do I start in admin mode so windows can find and install the network card again?)
restart VB, and maybe VB will now figure it out?

All of this risking damaging my machine because we all know how stable windows is when playing with hardware.

THIS IS A BUG!!! and needs to be fixed.

It seems to be a similar problem to moving or renaming VDI files and the UUID issues.

STOP USING UUID's or have a way to EASILY reassign them.

Mark.

A bug? On a [SOLVED] topic?!

This more-than-3years-old topic is about HOST-ONLY interface, a virtual software-based interface created by Virtualbox.
You are talking about a real physical interface on which you try to bridge.
I think this is the bug here.

To prevent further talk, I will lock this topic. If you have an issue, please create a new topic after reading the Minimum information needed for assistance topic.