Page 1 of 1

Fail to start bridged guest vm

Posted: 3. Apr 2015, 14:37
by Plouf
Dear community,

This has been a few month I'm looking to troubleshoot a problem with the latest VirtualBox 4.2.28 on Windows 7 pro.
When I start the vm I get the following message (cf below). I've attached the log files.

Please help me to troubleshoot that, this is driving me crazy.

Best regards
IntNet#0: szNetwork={HostInterfaceNetworking-Intel(R) Ethernet Connection I218-LM} enmTrunkType=3 szTrunk={\DEVICE\{166F0B7A-2863-497D-9E49-F9E564682B72}} fFlags=0x8000 cbRecv=325632 cbSend=196608 fIgnoreConnectFailure=false
VMSetError: F:\tinderbox\win-4.2\src\VBox\Devices\Network\DrvIntNet.cpp(1752) int __cdecl drvR3IntNetConstruct(struct PDMDRVINS *,struct CFGMNODE *,unsigned int); rc=VERR_SUPDRV_COMPONENT_NOT_FOUND
VMSetError: Failed to open/create the internal network 'HostInterfaceNetworking-Intel(R) Ethernet Connection I218-LM'
VMSetError: F:\tinderbox\win-4.2\src\VBox\Devices\Network\DevE1000.cpp(7721) int __cdecl e1kConstruct(struct PDMDEVINS *,int,struct CFGMNODE *); rc=VERR_SUPDRV_COMPONENT_NOT_FOUND
VMSetError: Failed to attach the network LUN
PDM: Failed to construct 'e1000'/0! VERR_SUPDRV_COMPONENT_NOT_FOUND (-3700) - The component factory was not found.
ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={Failed to open/create the internal network 'HostInterfaceNetworking-Intel(R) Ethernet Connection I218-LM' (VERR_SUPDRV_COMPONENT_NOT_FOUND).
Failed to attach the network LUN (VERR_SUPDRV_COMPONENT_NOT_FOUND)}, preserve=false
Power up failed (vrc=VERR_SUPDRV_COMPONENT_NOT_FOUND, rc=E_FAIL (0X80004005))

Re: Fail to start bridged guest vm

Posted: 3. Apr 2015, 14:39
by loukingjr
The latest VirtualBox is 4.3.26

Re: Fail to start bridged guest vm

Posted: 3. Apr 2015, 14:54
by loukingjr
Looked at your log. First you only have 192MB RAM assigned to the guest. I suppose XP will run in 192MB but not very well. Try 512 or even 1024MBs. You also have WindowsXP_64 selected in the settings which you most likely don't have. Try the normal XP in the settings. You might want to increase the VRAM setting to 24MB.

The main issue is you need to switch the Network Adapter to PCnet-Fast III

Re: Fail to start bridged guest vm

Posted: 6. Apr 2015, 01:51
by zerkms
loukingjr wrote:Looked at your log. First you only have 192MB RAM assigned to the guest. I suppose XP will run in 192MB but not very well. Try 512 or even 1024MBs. You also have WindowsXP_64 selected in the settings which you most likely don't have. Try the normal XP in the settings. You might want to increase the VRAM setting to 24MB.

The main issue is you need to switch the Network Adapter to PCnet-Fast III
I have the same issue (which I explained at viewtopic.php?f=6&t=64797&p=317689#p317689) and switching to `PCnet-Fast III` does not change anything

Re: Fail to start bridged guest vm

Posted: 6. Apr 2015, 01:55
by zerkms
@Plouf,

any chance you have kaspersky products running? Seems like I have found the solution for my problem (which looks suspiciously similarly)