Do you think it's possible to implement some logic on VirtualBox side to bypass/workaround that M$ bugs?
Maybe it's possible i think...?
VirtualBox VM shows 2 pcs of VirtualBox Host-Only Ethernet Adapter, but there is only one...?
-
- Posts: 341
- Joined: 9. Mar 2012, 00:14
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: VirtualBox VM shows 2 pcs of VirtualBox Host-Only Ethernet Adapter, but there is only one...?
Anything's possible. But I wouldn't know how (unless Virtualbox were programmed in VBscript, that is ). There is no such filtering now. And since it's really a Windows bug, it may not be possible to filter on it.
Try suggesting the filter in your bug report. But don't lose sight of the web-search: I have a vague recollection this was cleared up by tweaking Windows in a previous forum topic.
Try suggesting the filter in your bug report. But don't lose sight of the web-search: I have a vague recollection this was cleared up by tweaking Windows in a previous forum topic.
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: VirtualBox VM shows 2 pcs of VirtualBox Host-Only Ethernet Adapter, but there is only one...?
That isn't so clear to me.jmar83_the2nd wrote:OK - so now it has CLEARLY shown that VirtualBox ist NOT ABLE to handle that issue correctly
VirtualBox gets a list of NICs from the host and eliminates those which the bridged driver hasn't been enabled for. It has no way of knowing which NICs are real and which are fictional until it actually tries to use one. It could for example be a USB NIC that isn't plugged in right now.
OTOH, failing to properly present the list given by the OS would be a bug. Intruding on OS domains (e.g. management of host OS device lists) would be a violation of good design practice.
-
- Posts: 341
- Joined: 9. Mar 2012, 00:14
-
- Posts: 341
- Joined: 9. Mar 2012, 00:14
Re: VirtualBox VM shows 2 pcs of VirtualBox Host-Only Ethernet Adapter, but there is only one...?
-> The thing is that i NEVER created a #2 host only adapter by myself / manually...
regards, jan
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: VirtualBox VM shows 2 pcs of VirtualBox Host-Only Ethernet Adapter, but there is only one...?
jmar83_the2nd wrote:i NEVER created a #2 host only adapter by myself / manually...
mpack wrote:This is normal behaviour on Windows. When you do an feature update it will copy all the NICs.
You didn't make the adapter, Windows did.scottgus1 wrote:This "bug" is caused by Windows OS updating behavior, not by Virtualbox.
-
- Posts: 341
- Joined: 9. Mar 2012, 00:14
Re: VirtualBox VM shows 2 pcs of VirtualBox Host-Only Ethernet Adapter, but there is only one...?
I would say VirtualBox should be able the same thing i've done in a machine-to-machine way - instead of mine - the human-to-machine way.
And yes, i believe that it is a Window$ issue - but, nevertheless, i would try to do that stuff if i'm a VirtualBox developer
And yes, i believe that it is a Window$ issue - but, nevertheless, i would try to do that stuff if i'm a VirtualBox developer
regards, jan
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: VirtualBox VM shows 2 pcs of VirtualBox Host-Only Ethernet Adapter, but there is only one...?
They were hiring some short time ago. And user-contributed code is considered for inclusion.jmar83_the2nd wrote:i would try to do that stuff if i'm a VirtualBox developer
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: VirtualBox VM shows 2 pcs of VirtualBox Host-Only Ethernet Adapter, but there is only one...?
I don't understand how you think that could ever be possible. You know what devices on your system really exist, VirtualBox does not. VirtualBox only knows what the host OS reports.jmar83_the2nd wrote:I would say VirtualBox should be able the same thing i've done in a machine-to-machine way - instead of mine - the human-to-machine way.