Windows 10 Hosts

[dcassell]

I just installed test build 5.0.5 r102676 and it does not fix the problem. Still no communication between host and guests with bridged adapters.

[BoldyBoddinton]

err ok, told to move win 10 bridge network workaround to this topic.

RE communication between host and guests with bridged adapters

VB 5.0.4
on host machine after starting VM goto host network settings tick/untick IPv6 and OK, then got back and tick untick again, OK. bridge now works fine until reboot.

[enroberte]

Hi guys.

I have windows 10 home 64-bit and as soon I install the newest official or test virtualbox version, I immediately loose internet on my windows 10 host and I get the error DNS_PROBE_FINISHED_NO_INTERNET
My laptop is connected with utp cable. Internet starts working again when I uninstall virtualbox.
I have two vms XP3 nad Win2012 which are running well in virtualbox but without internet.

Can you help me , please?

[dfduarte]

err ok, told to move win 10 bridge network workaround to this topic.

RE communication between host and guests with bridged adapters

VB 5.0.4
on host machine after starting VM goto host network settings tick/untick IPv6 and OK, then got back and tick untick again, OK. bridge now works fine until reboot.

I disabled TCP/V6 on the host and the communication with the VM is back!

@enroberte
You probably have an incompatible network adapter. To me it was Panda Cloud AV, its network driver completely disabled internet on my host with that error.

[RoyW]

"Just a quick comment to state that 5.0.5 (102660) has allowed me to get the Bridged Network back up and running... "

I upgraded, directly installed over existing installation.

IPV6 has been removed from both host and guest. ( Windows is relatively easy to disable so I wont detail the actions)

"Disable IPV6" - "Add/Edit the following lines in sysctl.conf"
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1

"Then execute"
sudo sysctl -p

After a reboot of the VM I sometimes have to activate/deactivate the network interface before it obtains an address
"Disable/Enable Ethernet Card"

sudo ifconfig eth0 down
sudo ifconfig eth0 up

It does cause sporadic problem when reading from my NAS.. If I watch a film on Windows, which is located on the NAS, whilst the VM is running, I sometimes receive disk errors, as soon as I stop the VM the errors disappear. VB is interfering with my network card but only sporadically... At least the VM is running..

[Giusi]

@BoldyBoddinton:

could you pls explain with more and simple details yr workaround for
win 10 network bridge

thanks in advance!

cheers!

[ViniestLearner]

Hi,

I have just disabled the IPv6 from my computer's Ethernet cable connection and it works. I haven't restarted the system yet, but at least it works now.

Cheers

[piggyz]

@BoldyBoddinton:

could you pls explain with more and simple details yr workaround for
win 10 network bridge

thanks in advance!

cheers!

For me, apparently and after having a test with a lot of physical and virtual machines, Virtualbox 5.0.4 perfectly fixed my network bridge not found adapter on the guest and every other networking problems related with suspend and hibernation mode still with network adapters loosing configuration and disappear from the bridge list. For now, hosts with guests open retain total network operability also after a suspend or hibernate. No need for any workaround or compatibility mode.

I can say, in my case, Virtualbox is now totally compatible with Windows 10 hosts. I'm referring to Windows 10 0.10240.

[riemer]

The tip to deactivate the IPv6 work

my problem is resolve

THANKS

[gogoud]

Deactivating/reactivating IPv6 works, but it is only a workaround. The underlying problem is not fixed in 5.0.5-102676.

[Giusi]

Deactivating/reactivating IPv6 works, but it is only a workaround. The underlying problem is not fixed in 5.0.5-102676.

for me win 10 home 64 even NOT works at all also the workaround...

[piggyz]

Deactivating/reactivating IPv6 works, but it is only a workaround. The underlying problem is not fixed in 5.0.5-102676.

for me win 10 home 64 even NOT works at all also the workaround...

IMHO, your system and not Virtualbox, is broken. You should reinstall Windows 10 host.

[Giusi]

..just tried..
do not solve at all...
cheers

[eforsberg]

I had the issue with no connectivity between host and guest (host = windows 10, Broadcom 57xx driver)
The 5.0.51 102781 build fixed it for me

[gswa]

VBox crashes when I'm trying to create XP guest.

host Windows 10 x64 AMD A8-5545M w/8Gb RAM
guest Windows XP 32-bit w/1Gb RAM and 10Gb VDI HDD
Vbox 5.0.4 102546 (and previous 5.x too)

Crash happening after HDD setup when creating VM and then when starting VirtualBox.

Errors in log:

Code: Select all

00:01:13.833764          ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Unknown exception
00:01:13.833764          F:\tinderbox\win-5.0\out\win.amd64\release\obj\VBoxAPIWrap\MediumWrap.cpp[2245] (long __cdecl MediumWrap::GetEncryptionSettings(unsigned short **,unsigned short **))}, preserve=false aResultDetail=0
00:01:14.083713          ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={f30138d4-e5ea-4b3a-8858-a059de4c93fd} aComponent={MachineWrap} aText={This machine does not have any snapshots}, preserve=false aResultDetail=0
00:01:14.099384          ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Unknown exception
00:01:14.099384          F:\tinderbox\win-5.0\out\win.amd64\release\obj\VBoxAPIWrap\MediumWrap.cpp[2245] (long __cdecl MediumWrap::GetEncryptionSettings(unsigned short **,unsigned short **))}, preserve=false aResultDetail=0
00:01:14.146188          ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Unknown exception
00:01:14.146188          F:\tinderbox\win-5.0\out\win.amd64\release\obj\VBoxAPIWrap\MediumWrap.cpp[2245] (long __cdecl MediumWrap::GetEncryptionSettings(unsigned short **,unsigned short **))}, preserve=false aResultDetail=0
00:01:28.687724          ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Unknown exception
00:01:28.687724          F:\tinderbox\win-5.0\out\win.amd64\release\obj\VBoxAPIWrap\MediumWrap.cpp[2245] (long __cdecl MediumWrap::GetEncryptionSettings(unsigned short **,unsigned short **))}, preserve=false aResultDetail=0
00:08:14.448325 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Medium 'C:\Users\Пользователь\VirtualBox VMs\xp_one\xp_one.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:08:14.448325 Watcher  ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={0169423f-46b4-cde9-91af-1e9d5b6cd945} aComponent={VirtualBoxWrap} aText={The object is not ready}, preserve=false aResultDetail=0

Is there something to try to avoid this?