virtualbox.org

well ...
i am new here and i have a fresh install for windows 10 version 2004.

i found something i have never seen.
there is a virtual adapter as a Hyper-V Virtual Ethernet Adapter dedicated for VirtualBox.
but there is also a virtual adapter as a VirtualBox Host-Only Adapter created by virtualbox.

is that normal?
which virtual adapter is for virtualbox?

you can take a look at the picture i uploaded here.

It is quite likely that your host PC has Hyper-V enabled. On Windows 10 Pro, Hyper-V virtual machines can be made.

Virtualbox is working on running while Hyper-V is enabled but the code is not ready yet. In most cases we hear of on the forum, Hyper-V interferes with Virtualbox guests.

To turn Hyper-V off completely, do this:

1. Shut down all programs. You will have to reboot your host.

2. See I have a 64bit host, but can't install 64bit guests. This tutorial has a couple more things to look for in step 2. Be sure these are all turned off.

3. Find the Command Prompt icon, right click it and choose Run As Administrator.

4. Enter this command:

bcdedit /set hypervisorlaunchtype off

5. Enter this command:

shutdown -s -t 2

6. When the computer turns off, unplug it for 20 seconds. Then plug it in again and boot up Windows 10.

If your Virtualbox does not start successfully, zip and post another vbox.log. For further info, see https://www.tenforums.com/tutorials/139 ... puter.html

Regarding the two vEthernet network interfaces: The one called vEthernet (Default Switch) is created when Hyper-V is installed. Additionally, when Windows Sandbox is installed, for each existing (physical) network interface X an interface called vEthernet (X) is created. The VirtualBox Host-Only Network interface is the one created by VirtualBox.

Thanks both of you.

one more question.
does it mean that i should remove one of them in order to make it running properly?

i am wondering why microsoft does not provide a set of APIs for all virtual machine to acquire hyper-V.
the Hyper-V will be released and returned to windows system if the target virtual machine is closed.

Hyper-V is a type-1 hypervisor. It runs on the bare metal of the PC, and operating systems, one of which is the main Windows 10, sits on Hyper-V.

Virtualbox is a type-2 hypervisor. It requires an already-running operating system before it can run other operating systems.

For now, Hyper-V must be turned off so Virtualbox can run smoothly under all circumstances. Some limited circumstances may allow Virtualbox to run a guest while Hyper-V is enabled, but the operative word is "limited" so far. See 'Virtualbox 6.0 and Hyper-V' viewtopic.php?f=6&t=90853.

If you want to try Hyper-V and Virtualbox, in most cases it will be one or the other. See the 'tenforums' link above for an at-boot click switch to turn Hyper-V on or off as needed.

thanks for reply.

i got the answer.
wish you all having a nice day.