virtualbox.org

piggyz wrote:Dear Virtualbox/Oracle developers, it is a mess you should try to clear, networking is a lot more basic than other aspects of the software. Example: audio is fixed, then, IMHO, in a virtual infrastructure, networking should have a priority on audio.

Oracle customers set priorities, non-paying users don't. If you are unhappy with VirtualBox, do not use it.

In case that you actually want to help, please do tell us how to reproduce the problem with "invisible" bridged or host-only adapters. It does not happen on our Windows 10 systems (unlike, say, the problems with audio), which makes it quite difficult to fix.

As a reminder, Windows 10 is currently not a supported VirtualBox host OS. If you insist on using Windows 10 despite that, you need to assume responsibility for the decision.

i have mobo: gigabyte z97 hd3:
http://www.gigabyte.com/products/produc ... id=4955#ov

and for me is the exact contrary..

i'm really not able to select the bridge network cause my adapter is not recognized..and i really do not have nvidia sw..

i'm only able to set NAT

hope this helps

"It does not happen on our Windows 10 systems (unlike, say, the problems with audio),"..:

you mean that you are able to select bridge network..?
so why so many users here are not able to?

is a matter of hw?
i linked my mobo hoping this helps..

win 10 64bit host
win xp guest

Giusi wrote:you mean that you are able to select bridge network..?

Yes, we're able to select bridged adapters and they work.

so why so many users here are not able to?

If anyone could answer that, the problem wouldn't exist.

is a matter of hw?
i linked my mobo hoping this helps..

No, it doesn't really help because we don't have such motherboard. It is probably a matter of hardware, but quite possibly not the hardware per se but rather the drivers or possibly other software installed on the system.

I have two laptops with Windows 10, one is a Lenovo X1 Carbon (Core i5-3427U) and the other a Lenovo Z50-75 (AMD A10). Neither of them has trouble with bridged or host-only networking. Both were upgrades from Windows 8.1. I also have a Windows 10 VM with VirtualBox installed and again no such problem.

So far we have random people shouting "it's not working for me". The vast majority does not bother providing any information at all, and with the few tidbits that we have it's impossible to make any inferences. Presumably none of the people who build VirtualBox on Windows themselves has this problem either, because they could debug it and tell us what's really happening.

You have to wait, sorry. That's the price of upgrading your host OS too soon.

michaln wrote:

Giusi wrote: So far we have random people shouting "it's not working for me". The vast majority does not bother providing any information at all, and with the few tidbits that we have it's impossible to make any inferences. Presumably none of the people who build VirtualBox on Windows themselves has this problem either, because they could debug it and tell us what's really happening.

You have to wait, sorry. That's the price of upgrading your host OS too soon.

here are my datas:

Winblu - Pc Desktop - EXPERT L5 0180

PROCESSORE: Intel® Core™ i5-4590 (3,30Ghz, 6 MB, LGA 1150, 84W, 22NM)
SCHEDA MADRE: mod. GA-Z97-HD3 Intel Z97 LGA1150, HD Audio, Gblan, VGA+DVI+HDMI, 2xUSB2.0, 4xUSB3.0, 6xSata3 Raid 0/1/5/10,
4xSlot DDR3/1600MHz Max. 32GB, 2xPci-Ex16/4 3.0, 2xPci-Ex1, 2xPCI, 1xPS/2, Software bundle Intel Rapid Start Tec., Atx
·
· MEMORIA: 1 X 8GB DDR3 1600Mhz HyperX FURY
· HARD DISK: 1000Gb Serial Ata 3 7200Rpm
· SCHEDA VIDEO: Integrata, connettori VGA+DVI+HDMI (disponibile slot Pci-Ex16 3.0)
· SCHEDA AUDIO: Integrata HD, n° 6 jacks audio
· OTTICO: Masterizzatore per Dvd Dual Layer 24x24x e DVD-RAM 12x SATA
· LETTORE: Card Reader 3,5"
· SCHEDA DI RETE: Integrata Gigabit
CABINET: Miditower colore nero lucido, Alimentatore 460W (efficienza 80%), Dimensioni (PxLxA) 438x190x440mm, Drive Bays 4x5.25 ext. -
1x3.5 ext. - 4x3.5 int., porte Audio e 2xUSB3.0 lato superiore

i have also unistalled the net adapt and re installed with its latest driver..

"Presumably none of the people who build VirtualBox on Windows themselves has this problem either, because they could debug it and tell us what's really happening.
"..:

what you mean..?

thxs for yr kind helping and patience too!!

cheers!


·

Giusi wrote: · SCHEDA DI RETE: Integrata Gigabit

That's not terribly detailed; although we can probably find out what it is based on the motherboard type, could you please tell us what the network adapter model is?

Also, I assume your system has only one wired Ethernet NIC and that is what you're using?

Finally, is your Windows 10 installation an upgrade (from what?) or is it a clean install? Which flavor is it (32-bit/64-bit, Home, Pro, etc.)?

I'm sure there is something the affected systems have in common, but it's not at all clear what.

"Presumably none of the people who build VirtualBox on Windows themselves has this problem either, because they could debug it and tell us what's really happening.
"..:
what you mean..?

There are people (not many) who build VirtualBox on Windows themselves from sources, but they probably don't see this problem, possibly because they're not on Windows 10.

michaln wrote: That's not terribly detailed; although we can probably find out what it is based on the motherboard type, could you please tell us what the network adapter model is?

Also, I assume your system has only one wired Ethernet NIC and that is what you're using?

Finally, is your Windows 10 installation an upgrade (from what?) or is it a clean install? Which flavor is it (32-bit/64-bit, Home, Pro, etc.)?

I'm sure there is something the affected systems have in common, but it's not at all clear what.

because they could debug it and tell us what's really happening.
"..:
what you mean..?

hi!

first so many thxs again!

1)realtek PCIe GBE RTL8168E

2) yes is the only NIC

3) upgrade from win 8.1 home 64bit now is win 10 home 64bit , so not a clean install

4)"because they could debug it and tell us what's really happening."..:

this is what i do not understand..pls aplogize my very very few and bad english..

thxs for yr patience!!

cheers!!

michaln wrote:

piggyz wrote:Dear Virtualbox/Oracle developers, it is a mess you should try to clear, networking is a lot more basic than other aspects of the software. Example: audio is fixed, then, IMHO, in a virtual infrastructure, networking should have a priority on audio.

Oracle customers set priorities, non-paying users don't. If you are unhappy with VirtualBox, do not use it.

In case that you actually want to help, please do tell us how to reproduce the problem with "invisible" bridged or host-only adapters. It does not happen on our Windows 10 systems (unlike, say, the problems with audio), which makes it quite difficult to fix.

As a reminder, Windows 10 is currently not a supported VirtualBox host OS. If you insist on using Windows 10 despite that, you need to assume responsibility for the decision.

Hello and thankx for your reply. For me, it happen on two systems with the same hardware. I'm wondering if it could also be related with the double video card, considering if I do use the integrated graphic I can choose Bridge Mode and if I don't (do use Nvidia card),

Attached the specs of one of the computers having the problem (the other is pretty much simllar same hardware).

If you need more, just ask.

@ Giusi:

Here is how I mananged to fix this problem:

Enable "Windows 8" compatibility for VirtualBox executable: right-click on VirtualBox shortcut>Properties: in Properties dialog box: switch to "Compatibility" tab, under "Compatibility mode" section, select the check box next to: "Run this program in compatibility mode", make sure "Windows 8" is selected in combo box. click Ok, run VirtualBox again! (it's not needed to run as Administrator)
then you'll see the Network Adapters appear again.
I hope this solution will be helpful.

@michlan:
As you mentioned, Windows 10 is not a supported system for VirtualBox, It seems that VirtualBox doesn't yet fully support Windows 10, so some features might not work properly on some computers. I wonder is there a way to debug or log VirtualBox operation while it's being launched and it's preferences is changed (in this case when network configuration is changed)?

counter24 wrote:@ Giusi:

Here is how I mananged to fix this problem:

Enable "Windows 8" compatibility for VirtualBox executable: right-click on VirtualBox shortcut>Properties: in Properties dialog box: switch to "Compatibility" tab, under "Compatibility mode" section, select the check box next to: "Run this program in compatibility mode", make sure "Windows 8" is selected in combo box. click Ok, run VirtualBox again! (it's not needed to run as Administrator)
then you'll see the Network Adapters appear again.
I hope this solution will be helpful.

thxs so much for yr helping!

unfurtunately this is the very first thing i've tried ..even before registering on this forum..
but of course in my case did not solve..

anyway so much thxs indeed!!

anyway the matter is also in the sw cause with my previous win 8.1
, i had the same pc and obviously the same hw,
i did not have this issue...

cheers!

piggyz wrote:For me, it happen on two systems with the same hardware. I'm wondering if it could also be related with the double video card, considering if I do use the integrated graphic I can choose Bridge Mode and if I don't (do use Nvidia card)

To be honest that doesn't make much sense, but anything is possible. That sounds like it might be a bug in Windows though, because I really don't see how the choice of the graphics device could influence network drivers. How exactly do you switch, is that something you can do while Windows is running, or do you boot differently?

Attached the specs of one of the computers having the problem (the other is pretty much simllar same hardware).

OK, that's another Realtek GBE NIC. Interesting. So, anyone else?

Just to add to what michaln has said, I updated a 4 month old ASUS UX305FA laptop that came with Windows 8.1 pre-installed. I had VB 5.0.0 installed. I upgraded to Windows 10 "In place" using the Media tool. The only issue I had was the audio problem which was fixed in VB 5.0.2. NAT works, Bridged works. The laptop is Wi-Fi'd into my network.

I assume everyone installed VirtualBox using "Run As Administrator".

loukingjr wrote:I assume everyone installed VirtualBox using "Run As Administrator".

I didn't. It really should not be necessary, the installer should ask for elevated privileges when it needs them. But I will not go on record saying that it makes no difference

okie doke.

edit: I am willing to go on record to say I have no idea why bridged isn't working for some users.

michaln wrote:

piggyz wrote:For me, it happen on two systems with the same hardware. I'm wondering if it could also be related with the double video card, considering if I do use the integrated graphic I can choose Bridge Mode and if I don't (do use Nvidia card)

To be honest that doesn't make much sense, but anything is possible. That sounds like it might be a bug in Windows though, because I really don't see how the choice of the graphics device could influence network drivers. How exactly do you switch, is that something you can do while Windows is running, or do you boot differently?

Attached the specs of one of the computers having the problem (the other is pretty much simllar same hardware).

OK, that's another Realtek GBE NIC. Interesting. So, anyone else?

Need to clarify that NEVER USED Realtek cabled interface, then it doesn't appear too on the list of selectable bridge adapter on the list. When they are not recognised, BOTH the network card are not visible and chooseable.

I always do use Intel wi-fi interface.

Related with the double display card, I always reply to your question. Sandy Bridges processors do integrate a video card in the central unit and there is a software called LUCID VIRTUE that offer the option to automatically handle the dual video card automatically choosing the one needed by the system for a particular application. Example: for a game, it will always choose the Nvidia Card then using LUCID VIRTUE software you can manually choose which card to apply to a particular application when the application start.

In the past I used to force Virtualbox to always use Nvidia video card for best performance and full 3D support. I can see, now, it is not needed anymore.

When afrer the inplace uograde to windows 10 deom windows 7 i had intermittent problems with Bridge Mode, i tried to force Nvidia card again and I can see with this Nvidia card enabled, bridge adapters never ever show in guest configuration network interface.

Then when I do run with Intel integrated video card, bridge mode do work then NAT family mode load fine then it not allow network connection in the sense u got the private ip 10.x.x.x but the virtual system do not receiveor transmit any network data packet.

If you need more infos or logs, please let me know. You guys should try to find a sandy bridge based machine with double video card and lucid virtue software installed.

piggyz wrote:You guys should try to find a sandy bridge based machine with double video card and lucid virtue software installed.

Sorry, there is no way we can spend that much time and money on a non-paying user.

Anyway, it should not matter if the Realtek NIC is used or not. What matters is whether the drivers are installed. If you can disable the adapter completely, that can be worth a try. I mean physically remove or (more likely) disable in the BIOS, so that the device doesn't show up at all.