virtualbox.org

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

..so the matter is there..??
but with win 8.1 and same pc i had no issue..
thxs for yr patience!!

cheers!!

michaln wrote:

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.

Well, some rock solid point to put it clear related with Sandy Bridges platform /Intel serie 6 Mobile chipset and Virtualbox under Windows 10 hosts bridged mode network issues:

1) If you do NOT activate Virtualbox in COMPATIBILITY MODE (it doesn't matter Windows 7 or Windows 8, it is the same), you can forget to see your hardware network devices in guest bridged mode drop down menu.

2) If you run your virtual machine using Lucid Virtue software to choose Nvidia Card, even with compatibility mode, you can forget to see your network hardware devices in guests beidged mode drop down menu.

So, that's for sure, there is a problem with Sandy Bridge platform and series 6 chipset (maybe other chipsets too?). I can't say for other chipsets, becouse I do not run Virtualbox in such machines and I run Virtualbox on two Sandy Bridges platform machines with the exact same problem.

Now, do not ask me why external video card and virtual Virtualbox network implementation fight. It could be IRQ sharing or whatever. I can help, then I can't fix it.

Now, you always state, we are not (I am not) a payer user so Oracle will iignore me. Fine, then Virtualbox 5.0.2 is broken in some aspects for many people related with network bridge support under brand new Windows 10 Host (I can confirm Windows 7 and 8.1, even on Sandy Bridge platform, are NOT affected by the problem), not just me, many users, so if they want call Virtualbox product compatible with Windows 10 they do have to fix this problems, pay or not to pay.

And them believe me, I suspect Oracle CEO will not be that happy to read that some employe state the company will fix free software just if payibng customers ask and pay for it. It is childish, and Oracle is all, but a childish company. It is a company that makes the history of IT, and it care about his product, pay service or don't.

hi!

1) in my case setting that compatibility unfurtunately did not solve..

"so if they want call Virtualbox product compatible with Windows 10 they do have to fix this problems, pay or not to pay.

And them believe me, I suspect Oracle CEO will not be that happy to read that some employe state the company will fix free software just if payibng customers ask and pay for it. It is childish, and Oracle is all, but a childish company. It is a company that makes the history of IT, and it care about his product, pay service or don't."..:

i really hope they will read this

cheers!!

anyway the last test build VirtualBox 5.0.3-102166 do not solve bridge issue
hope this helps

cheers!

Windows Server 2012 R2's DHCP server doesn't work with Virtualbox.

To solve this I had to give static IP's to both host (Windows 10) & guest (Windows Server).

PS Note: I'm using Host-Only & Bridged adapters in guest.

Giusi wrote:anyway the last test build VirtualBox 5.0.3-102166 do not solve bridge issue
hope this helps

cheers!

unfurtunately also the latest 5.0.3.102217..

and also the very latest 5.0.3.102224

for me, VirtualBox 5.0.2 solved the problem

i got this:

failed to get the oracle_VBoxNetLwf(sun_VBoxNetFlt) component, error (0x1)

Giusi wrote:i got this:

failed to get the oracle_VBoxNetLwf(sun_VBoxNetFlt) component, error (0x1)

I had that too before setting compatibility mode.

Remember you have to reboot the machine after applty compatibility mode to see the results.

With Z97 chipset machine it works fine comatibility mode. Then remember, even if it work, it is not fixed: first of all becouse you absiolutely need compatibility mode and second becouse standby hibernate can break it again until you reboot.

i had this also with compatibility mode...no hybernate and trying lots of reeboots...
you mean the comp. mode for only vbox.exe or all the .exe i have in the vbox folder..??
as for ex vboxsvc.exe and so on...

anyway tried also with all exe set to comp.mode..same issue...

Giusi wrote:i had this also with compatibility mode...no hybernate and trying lots of reeboots...
you mean the comp. mode for only vbox.exe or all the .exe i have in the vbox folder..??
as for ex vboxsvc.exe and so on...

anyway tried also with all exe set to comp.mode..same issue...

No!!! You don't have to put compatibility mode there!

You have to just put compatibility mode to Virtual Box Manager and then start the machines from there. It is probably becouse of it you system doesn't work (with all the limits this "wrking" actually got) in Compatibility Mode.

so which is the exe file i have to set in compat. mode..?
only the vboxmanage.exe?
not also vbox.exe?
chhers!!

Giusi wrote:so which is the exe file i have to set in compat. mode..?
only the vboxmanage.exe?
not also vbox.exe?
chhers!!

NO! Just VirtualBox.exe.

And obviously start the guest machines from there. VirtualBoc.exe is the console program where you manage and start all your machines.

PS: be sure no other exe got compatibility mode setting up in Virtualbox environment.

thxs!
so in the dir folder i set only virtualbox.exe to comp.mode

but should i have also previously to set that comp mode when installing the prog in its installer .exe?

cheers!