VirtualBox

Ticket #6057 (new enhancement)

Opened 4 years ago

Last modified 8 months ago

[feature-request] Installer: warn users for incompatible drivers on Windows host

Reported by: Technologov Owned by:
Priority: major Component: installer
Version: VirtualBox 3.1.2 Keywords:
Cc: Guest type: other
Host type: Windows

Description

I see there are some instances where vboxdrv or vboxnetflt drivers are incompatible with currently installed 3rd party drivers on Windows Host platform.

It would be better, especially for newbie users, if we detect such incompatibilities in our installer, and warn users.

Here is the known list: (and perhaps a few more that I overlook)

#3752 DNS protocol problem with Vista hosts => check Shrew Soft Lightweight filter rules

#5519 vboxnetflt: fatal BSOD installation on Marvell Server NIC

#3370 VBoxNetFlt: Conflict with the Trend Micro Anti-Virus driver

#3724 Host crash: vboxdrv crashes, when run together with coLinux

Other incompatible software:

-decndis.sys caused the crash on one user. decndis is part of the DEC (Digital Equipment Corp) LAT protocol that we use to access the VAX (reported by Huihong Luo of VMlite)

-Microsoft VirtualPC

-Microsoft Hyper-V

The same issues applies to Linux-host installer too, but since installers are platform-specific, it deserves a separate wish.

-Technologov, 22.1.2010

Change History

comment:1 Changed 4 years ago by Technologov

Related bugs: #5526 and #5455

comment:2 Changed 4 years ago by Technologov

Bug #5685 - COMODO internet security

-Technologov

comment:3 Changed 4 years ago by Technologov

Also a user in #639 mentions "Atheros WiFi" as a problem, that makes host BSOD.

 http://www.virtualbox.org/ticket/639#comment:42

-Technologov

comment:4 Changed 3 years ago by Technologov

I have no good ideas, how to handle the case for not-yet-installed drivers (i.e. if incompatible driver was installed _after_ VirtualBox)

-Technologov

comment:5 Changed 3 years ago by Technologov

NVIDIA nForce Network Driver: #6151

comment:6 Changed 3 years ago by Technologov

Few more incompatible drivers reported: (conflict with vboxnetflt; Bug #6933)

-Checkpoint VPN

-firewall (softPerfect)

---

-Technologov

comment:7 Changed 3 years ago by Technologov

Found another 3rd party conflicting software: "Prio", Bug #7930:

 http://www.prnwatch.com/prio.html

-Technologov

comment:8 Changed 3 years ago by Technologov

Found another 3rd party conflicting software: "Windows Phone 7 emulator" is incompatible with VirtualBox 4.0.x.

See:  http://forums.virtualbox.org/viewtopic.php?f=6&t=39350&p=182653#p182653

-Technologov

comment:9 Changed 3 years ago by Technologov

I have new idea how to handle the case for not-yet-installed drivers (i.e. if incompatible driver was installed _after_ VirtualBox): make some Windows-host checker, that lists incompatible drivers, _before_ VMM is started.

-Technologov

comment:10 Changed 3 years ago by Technologov

More incompatible software found: Shrewsoft VPN client and Cisco AnyConnect VPN client.

 http://www.virtualbox.org/ticket/7235

-Technologov

comment:11 Changed 2 years ago by Technologov

More incompatible software found: "Online Armor" firewall. Bug #9726.

-Technologov

comment:12 Changed 2 years ago by willrsnds

More Incompatible software found: Real Media Catcher by Applian ( http://www.applian.com)

Post on there forum about the issue:

 http://forum.applian.com/showthread.php?7328-Blue-Screen-of-Death-after-installing-Replay-Media-Catcher-4.3.0

comment:13 Changed 2 years ago by Technologov

More Incompatible software found: SoftPerfect Networks and Realtek NICs with VLAN tagging.

https://www.virtualbox.org/ticket/7094

-Technologov

comment:14 Changed 8 months ago by vb-boxer

Update Aug 2013: Online Armor is still incompatible with Virtual Box when installed on the host system: Installing Online Armor on a system that has Virtual Box installed will cause a blue screen. Reason: The blue screen is caused by improper parameter validation inside the Virtual Box network driver when releasing NDIS related memory. Solution/Workaround: Because the problem isn't caused by Online Armor directly, there is no way for us to fix it. The only way to use Online Armor at this point is to uninstall Virtual Box and switch to another VM solution.

So solution seems to be depending on Virtual Box.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use