Unable to start a Linux virtual machine with Bridget Adapter

[Maarvin]

Hi,

I have a physical host that runs with Windows 10.

I have Oracle VirtualBox 6.1.16-140961-Win running on it.

I can create a virtual machine running with OEL 7.4 without configuring the network for it (linkd to: NAT)
But when I attempt to configure the network (linked to: Bridget Adapter), I get this error and I cannot start the virtual machine:

---
00:00:02.179957 hrc=ERROR_TRUST_FAILURE 0x800706FE
00:00:02.180354 Constructor failed with rc=VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR pfnCFGMConstructor=00007ffda5090ee0
00:00:02.180637 VMSetError: F:\tinderbox\win-6.1\src\VBox\VMM\VMMR3\VM.cpp(318) int __cdecl VMR3Create(unsigned int,const struct VMM2USERMETHODS *,void (__cdecl *)(struct UVM *,void *,int,const char *,unsigned int,const char *,const char *,char *),void *,int (__cdecl *)(struct UVM *,struct VM *,void *),void *,struct VM **,struct UVM **); rc=VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR
00:00:02.180641 VMSetError: The configuration constructor in main failed due to a COM error. Check the release log of the VM for further details.
00:00:02.181483 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={The configuration constructor in main failed due to a COM error. Check the release log of the VM for further details. (VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR)}, preserve=false aResultDetail=-6400
00:00:02.181784 Console: Machine state changed to 'PoweredOff'
00:00:02.261842 Power up failed (vrc=VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR, rc=E_FAIL (0X80004005
---

and prompted:

---
The configuration constructor in main failed due to a COM error.
Check the release log of the VM for further details.
(VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR).


Resultaatcode:
E_FAIL (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
---

Does someone know what can be the problem, and how to investigate further?
Is related to Windows 10 or VirtualBox?

Thanks and Regards

[mpack]

AFAIK you only get this error when there's a mix of executables from different VirtualBox versions installed on this PC. To avoid this, don't copy VirtualBox executables outside the VirtualBox installed program folder.

p.s. small thing, but the word is "bridged", not "Bridget". The latter is a girl's name, e.g. "Bridget Jones".

[Maarvin]

Yes, you are right.
After having created the virtual machine, I modified "Linked to/Attached to: NAT" to "Linked to/Attached to: Bridged Adapter), and then I got that error.
You wrote "you only get this error when there's a mix of executables from different VirtualBox versions installed on this PC. To avoid this, don't copy VirtualBox executables outside the VirtualBox installed program folder".
What do you mean with "VirtualBox executables", such a file VirtualBox-6.1.10-138449-Win?
I have uninstalled VirtualBox, and re-installed it again (restarting the Windows host), but I still get the error.
Any idea how I could solve it?

[fth0]

The VirtualBox hardening code rejected the NetSetupShim.dll. Please provide a zipped copy of the VBoxHardening.log file.

[Maarvin]

I started eveerything frm scratch:
1) De-installing VirtualBox
2) Restart physical host
3) Re-installing VirtualBox (VirtualBox-6.1.10-138449-Win.exe)
4) Create and OEL 7.4 Linux machine (oel74-base-linux) with default Linked to/Attached to: NAT
5) The modified Linked to/Attached to: NAT to Linked to/Attached to: Bridged Adapter
I get the same error than previously, see the configuration network_bridged.png.
I send of the NAT and bridged logs I have: Logs_NAT.zip and Logs_bridged.zip.
Any idea where to investigate further?

[fth0]

The VirtualBox hardening code seems to be satisfied (despite the NetSetupShim.dll signature topic). I'd suggest to try the current VirtualBox 6.1.18 then.

[Maarvin]

I removed completely the prvious installation, restarted the physical host, and then installed VirtualBox with version VirtualBox-6.1.18-142142-Win.exe.
I can start the created virtual machine if I use Linked to/Attached to: NAT.
But, unfortunately I get the same error and I am unable to get it started with the Bridged Adapter, see: network-bridge-configuration.png.
See: NAT log network-NAT-log.zip and network-bridged-logs.zip.
Any idea where to investigate further?

[fth0]

The errors in the VBox.log file indicate that something is wrong with the installation of the VBoxNetFlt driver. You could search for installation failures on your Windows host, or maybe the VirtualBox User Manual can help: 12.6.5. Bridged Networking Adapters Missing.

[Maarvin]

I followed indications on "12.6.5. Bridged Networking Adapters Missing", but I don't see "MaxNumFilters", see Windows10_regedit_network.png.
Furthermore, how can I chick if VBoxNetFlt driver is installed?
Any other idea? Thanks.

[mpack]

You shouldn't need to go into the registry. Just go the Network Properties panel (right click network icon on taskbar, Open Network and Internet settings. In the advanced section click on "Change adapter options", right click the adapter you want to bridge to and view its properties. "VirtualBox NDISx Bridged Networking Driver" should be present in the list of services, and it should be checked (enabled). If not present it was not installed. If present but disabled, enable it.

[Maarvin]

Yes, "VirtualBox NDISx Bridged Networking Driver" is present and checked, see windows10_netwerkcon_box.png.
But further, I don't know what can be wrong.

[Maarvin]

See: windows10_netwerkcon_box.png

[mpack]

I don't think your failure has anything to do with VirtualBox. It seems to be policy. You seem to have some kind of extra security layer over your adapters, and it prevents VirtualBox from bridging to them. I disagree that this problem has been resolved or is non fatal. It's only delayed until you try to actually make the connection. Then VirtualBox fails, not because of hardening, but because it's configured to bridge to a NIC it can't bridge to.

[Maarvin]

I really don't know what I have to correct or check.

[mpack]

Nor me, or I would have suggested something. It's really your local IT support you should be talking to, since I assume it was they who configured these extra levels of security.