Virtualbox fatal BSOD installation

[myhead]

Can not install Virtualbox 3.0.08 - 3.0.10 - 3.0.12 Windows Vista x64 SP2 and or Win7 x64 SP0 host Marvell Dual 88E8056 network hardware configured as: LACP-TEAM (802.3ad) Fatal BSOD installation error pointing to yk62x64l.sys (also confirmed by Marvell Tech Support) No VBox.log available Thank you

[misha]

Could you attach a minidump for the crash to this report.

[myhead]

crash data

[Technologov]

What happens if you install without USB and without networking option ?

-Technologov

[misha]

We've made some enhancements to networking component installation in VBox 3.1. Could you please try VBox 3.1 to see if the issue is solved for you?

[myhead]

Replying to Technologov:

What happens if you install without USB and without networking option ?

-Technologov

Thanks for your interest. Virtualbox installs without any issue if you disable ALL Virtualbox networking during installation. Please see later post Thanks

[myhead]

Replying to misha:

We've made some enhancements to networking component installation in VBox 3.1. Could you please try VBox 3.1 to see if the issue is solved for you?

Thank you for your interest I have installed Virtualbox 3.1.0 yesterday, default install = BSOD--> Marvell driver

Please see later post Thanks

[myhead]

Update 01-12-2009 From my original post I mentioned that Marvell Tech support confirmed Virtualbox installation causes critical BSOD with their driver. They have kindly emailed me yesterday with a 'workaround' possibility. ============================== To prevent the BSOD please do: 1) Install NCU 2) Install Virtual Box 3) Create a Team ============================== I have just completed VB installation and can confirm that it is successful however my only concern is that upon each VB update, this will require the 'TEAM' to be broken - VB update installed - recreate TEAM again, not ideal but this is the first time on this new hardware that it has ever worked, I'm grateful. Can I ask if Sun-VB will continue to look at this problem and perhaps talk to Marvell so that a full safe resolution can be meet between all parties. Many thanks

[misha]

Replying to myhead: Thanks for the info. Yes, we will continue looking into this problem.

[Technologov]

What causes this conflict between Marvell driver and VBoxNetFlt driver ?

[Technologov]

And what do "teams" do ?

[misha]

Replying to Technologov:

And what do "teams" do ?

​http://en.wikipedia.org/wiki/Link_aggregation

[Technologov]

Aha, so basically those Ethernet ports are running in 802.1AX mode, not in standard Ethernet mode (802.3), and this confuses VirtualBox driver, VBoxNetFlt. VBoxNetFlt is attached to all host's ethernet ports by becoming a service for those ports.

If I understand correctly, VirtualBox with bridged networking works fine with Marvell, if you don't use teams.

The possible better workaround would be to disable/disallow VBoxNetFlt to attach to non-standard Ethernet ports. VBoxNetFlt must scan the ports, and not attach to such ports as a service.

-Technologov

[Technologov]

VBox team: Please change topic "Virtualbox fatal BSOD installation" --> "VirtualBox installation BSOD on bonded Marvell hardware"

This bug is remotely related to bug #4214

-Technologov

[misha]

Replying to Technologov:

Aha, so basically those Ethernet ports are running in 802.1AX mode, not in standard Ethernet mode (802.3), and this confuses VirtualBox driver, VBoxNetFlt. VBoxNetFlt is attached to all host's ethernet ports by becoming a service for those ports.

I can assure you that VBoxNetFlt does bind to only those devices it supports, and adapteris it binds to are ethernet adapters.

As far as I know the yk62x64l.sys is not a physical device driver either, but more likely the one used for creating teams, so it's likely not even loaded when no teams are defined on the system, while when loaded, it could create additional virtual miniports as well and make some protocol binding adjustments while team creation, so more likely the failure occurs due to some issues the yk62x64l.sys experiences while rebinding on NetFlt install.

[Technologov]

Please rename this bug to: "vboxnetflt: fatal BSOD installation on Marvell Server NIC"

Component should also be changed to "vboxnetflt", not "installer". (otherwise it makes very hard to search for this important bug)

And finally: Make it "blocker", as it results in Host BSOD.

-Technologov

[myhead]

21st November 2009 -->12th April 2010 Any chance of a update to this problem - thank you

[myhead]

FAO: Mikhail can I enquire as to whether you received my reply (14th & 21st April) to your email of the 14th April? Thank you

[misha]

Replying to myhead: Yes, (sorry, was on vacation). Just mailed you an answer.

[Technologov]

Please upgrade bug Priority to BLOCKER

Bug #5583 looks like duplicate of this one.

[myhead]

Hi Guys, With the imminent release of your VB4.X will bug #5519 have been sorted? Thanks for your time and help on this matter.

[Technologov]

Oracle: Please upgrade bug Priority to BLOCKER

myhead: There are lots of different 3rd party drivers, that are incompatible with VirtualBox. Marvell Network driver is just one of many.

A theoretically possible fix for this situation is described in Wish #6057

-Technologov

[aeichner]

Please reopen if still relevant with a recent VirtualBox release.