Known incompatibilities with 3rd party drivers on Host

Discussions related to using VirtualBox on Windows hosts.

Re: Known incompatibilities with 3rd party drivers

Postby Jaromir » 16. Jan 2013, 19:10

Hi,

Were there any changes according to this topic ?

I have Win8 x64 and i would want to run Hyper-V AND Virtual Box.
Unfortunately i noticed that when i install Hyper-V first, VirtualBox do not recognize AMD-V virtualization features.

After i removed Hyper-V everything is working on VirtualBox.

Is there any resolution to run both hypervisors in parallel ?
Jaromir
 
Posts: 2
Joined: 16. Jan 2013, 19:00

Re: Known incompatibilities with 3rd party drivers

Postby noteirak » 17. Jan 2013, 00:01

Hyper-V locks for exclusive use the Virtualization feature of the computer at boot time thus prevent any other software to use it in any way.
On the other hand, Virtualbox has an option to enable or disable this exclusive lock on a per vm basis, and does not lock the feature until at least one VM configured for it starts.
The problem is with Hyper-V, not Virtualbox.
Until Microsoft decides otherwise, this will remain a incompatibility.
Hyperbox - Virtual Infrastructure Manager - https://kamax.io/hbox/
Manage your VirtualBox infrastructure the free way!
noteirak
Site Moderator
 
Posts: 5177
Joined: 13. Jan 2012, 11:14
Primary OS: Debian other
VBox Version: OSE Debian
Guest OSses: Debian, Win 2k8, Win 7

Re: Known incompatibilities with 3rd party drivers

Postby Jaromir » 18. Jan 2013, 12:06

@noteirak

Thank you for your reply. It helped a lot unfortunately :|

I wanted to use VirtualBox to host Oracle VM Server / Oracle VM Manager along with OVM templates.
As i see i will have to try to use Hyper-V for that purpose :|
Jaromir
 
Posts: 2
Joined: 16. Jan 2013, 19:00

Re: Known incompatibilities with 3rd party drivers

Postby branic » 1. Feb 2013, 05:44

Can anyone shed any light on what the incompatibility is with the Cisco AnyConnect VPN client? and are there any workarounds?
branic
 
Posts: 7
Joined: 26. Nov 2011, 07:07
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: RHEL, Fedora

Re: Known incompatibilities with 3rd party drivers

Postby vb-boxer » 24. Aug 2013, 17:55

There seems to be a driver incompatibility between "Virtual Box bridged network support" and Emsisoft Internet Security Pack, especially the OnlineAmor firewall component included in EAM:
https://forums.virtualbox.org/viewtopic.php?f=6&t=57001

Issue is well known, is there a workaround or fix?

Thx...
vb-boxer
 
Posts: 24
Joined: 5. Dec 2012, 09:35

Re: Known incompatibilities with 3rd party drivers

Postby Perryg » 24. Aug 2013, 18:14

@vb-boxer,
No one here can help you with this.
You already posted to the tickets in bugtracker. The DEVs are the only ones that can do anything about this.
Perryg
Site Moderator
 
Posts: 34275
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Known incompatibilities with 3rd party drivers

Postby vb-boxer » 27. Aug 2013, 12:04

* :cry: *

It seems that developers don't take care of this issue, bugtracker has been 22 month without any change.
vb-boxer
 
Posts: 24
Joined: 5. Dec 2012, 09:35

Re: Known incompatibilities with 3rd party drivers

Postby spinx73 » 11. Sep 2014, 06:19

hello guys,
I had same problem, but this time with avast antivirus.
well first time I knew it when I choose to re-install my laptop.
Before I re-install my laptop, I had installed 64 bit windows and virtualbox. I can run it and I can install 64 bit guest os.
spec of my laptop pentium i5 with 16GB RAM. so by default and I'm sure it support virtualization.
But when I finished install my laptop. the weird thing happen. It didn't support 64 bit guest os anymore.
so I tried to remember what went wrong. as far as I know, the different was I change the virus scanner from avira to avast.
so I uninstalled avast, and install virtualbox again. whoola the 64 bit guest appear.
so please check it maybe i was wrong.

thanks
spinx73
 
Posts: 1
Joined: 11. Sep 2014, 06:05

Re: Known incompatibilities with 3rd party drivers

Postby andreya » 18. Dec 2014, 10:54

I have laptop windows 8.1
1 wireless card realtek RTL8723AE
1 ethernet card realtek RTL8168-8111
my problem is my laptop get bluescreen when i install virtualbox
then i unsintall all my network interface and reinstall again and the installation is complete without bluescreen
but the problem is my network interface not working properly(can't get ip address)
then i reinstall (right click in my broken interface in device manager and choose unisntall)
my network interface again then it's working again but just the wifi not the cable

do that install again then uninstall then do that again do it with another version of virtualbox and etc etc
and then now have this in my device manager(attachment 0 and 1)
and I ended up posting thread in this forum
hoping someone to help me
so that i not need to uninstall my laptop
FYI: i already install the network driver from my laptop cd but still no help
when i reinstall the virtualbox i do this too
from super user Unable to uninstall virtualbox network drivers
The registry keys for Oracle VirtualBox are located there:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VBoxDrv
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VBoxNetAdp
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VBoxNetFlt
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VBoxUSBMon
Corresponding files in the file system:

VBoxDrv VirtualBox Support Drive: c:\windows\system32\drivers\vboxdrv.sys

VBoxNetAdpVirtualBox Host-Only Network Adapter Driver" c:\windows\system32\drivers\vboxnetadp.sys

VBoxNetFltVirtualBox Bridged Networking Driver: c:\windows\system32\drivers\vboxnetflt.sys

VBoxUSBMonVirtualBox USB Monitor Driver: c:\windows\system32\drivers\vboxusbmon.sys

Suggested tool to finds these keys. disable, delete or access them in the file system or the registry:

MS TechNet Sysinternals Autoruns

Okay, this was really really a hard one. I've tried a felt 100 things.

My solution (Windows 8) was

Uninstall VirtualBox and reboot
Download RunAsSystem and start "C:\Windows\regedit.exe" with it (You can check with TaskManager that it really runs as "System")
Remove "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\SUN_VBOXNETFLTMP"
Remove the keys recommended by @climenole
Go to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\ROOT\NET and delete all "VirtualBo Host-Only ..." adapters.
Reboot
Use something like CCleaner to clean the registry
Reinstall VirtualBox
Attachments
0.png
0.png (117.98 KiB) Viewed 3159 times
andreya
 
Posts: 2
Joined: 18. Dec 2014, 07:40

Re: Known incompatibilities with 3rd party drivers

Postby gabe80million » 19. May 2015, 02:49

Sometimes, when I plug in my USBs, then I put it into the VirtualBox, it errors and won't let me put it into the system. It does this on all of my OSes.
Windows 10
Manufacturer: Dell
Model: Inspiron
Processor: AMD FX-8800P Radeon R7, 12 Compute Cores 4C+8G 2.10 GHz
RAM: 16 GB
System Type: 64-bit
gabe80million
 
Posts: 25
Joined: 28. Mar 2015, 01:51
Primary OS: MS Windows 8
VBox Version: OSE other
Guest OSses: Windows 95, NT 4, 98, ME, XP, 2000, Whistler, Server 2003, FLP, XP 64-bit, XP Black, etc.

Re: Known incompatibilities with 3rd party drivers

Postby mpack » 19. May 2015, 09:55

@gabe: This topic is about incompatibility between VirtualBox and any drivers on the HOST. Note what forum we are in. This is not the place to post about drivers you installed in a guest.
mpack
Site Moderator
 
Posts: 25490
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Known incompatibilities with 3rd party drivers

Postby Technologov » 19. May 2015, 09:57

@gabe: mpack is right. This post will soon be removed.
Technologov
Volunteer
 
Posts: 3245
Joined: 10. May 2007, 16:59
Location: Israel

Re: Known incompatibilities with 3rd party drivers on Host

Postby usr258 » 22. May 2015, 16:51

I'm a little confused by this thread. I have been running VB on my work computer(s) at least since version 4.1.2, and possibly earlier.

In that time, my host computer(s) have run Windows XP, Windows 7, and currently Windows 8.1. The VMs have been Windows XP, Windows 7, Linux Mint 16, Lubuntu, Ubuntu, CentOS, Tails, and others.

For work, I have had Checkpoint VPN and Cisco Systems VPN client installed on all three host machines, and in numerous Windows VMs. I have never had an issue between either of the VPN software and VB. In fact, the VPN software is the primary reason I started using VB. I had to have both running at the same time, but they occasionally caused problems with each other on my Windows XP host. I started using VB to segregate them in different VMs.

I realize they have been reported (in the past) as being incompatible with VB by some users, but my experience tells me that it cannot be true all the time. Also, it is possible that the reported "Cisco AnyConnect VPN client" is different from the Cisco Systems VPN Client (version 5.0.07.0440) that I use. I cannot make a comparison on the Checkpoint VPN client, but the version I use has varied from E75.30 Build 835017083 to E80.42 Build 986000092.

For what its worth...
usr258
 
Posts: 2
Joined: 22. May 2015, 15:18

Re: Known incompatibilities with 3rd party drivers on Host

Postby ikar.us » 22. May 2015, 17:45

If you use VB to seperate them,
then you are running the VPN clients in the guests?
This shouldn't be an issue.

As I understand, the problem is having them on the host.
Because both VPN and the VB bridge need to hook in the host's network stack.
ikar.us
 
Posts: 48
Joined: 26. Aug 2010, 01:40
Location: Baden
Primary OS: MS Windows 8
VBox Version: PUEL
Guest OSses: Debian u.a.

Re: Known incompatibilities with 3rd party drivers on Host

Postby ElQuia » 3. Jun 2015, 14:19

My THREE sistems that have VBox (4.3.12 working on x64 Win7 SP1) have nForce networking.
As today (july 3-2015) is there any change in the status of nforce incompatibilities or any known stable workarround???? :?:
ElQuia
 
Posts: 155
Joined: 30. May 2008, 23:31

PreviousNext

Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: Martin and 27 guests