• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

re: Hyper-V

E

Elf_Boy

2[H]4U
2FA
Joined
Nov 16, 2007
Messages
2,610
Hi guys,

I have not done much with virtual machines.

I downloaded the Win 10 public test and made a hyper-v box on my win8.1 machine.

Could one of the kind and knowledgeable people here tell me how to get networking going from within the VM?

I tried to install a virtual router/hub/switch (I forget the exact language at work right now) and it took out my Ethernet on the host computer till I removed it.

I'll probably end up putting it on my 'old' mobo/system - I was hoping to check it out on the VM first though.

Thanks again for any help,

*EB*
 
When you create a vSwitch and select a physical NIC for it to use you have the option of sharing that vSwitch with the host OS or not. If you share it, a virtual ethernet adapter will be created for the host OS to use. You can tag that virtual adapter with a VLAN or leave it untagged.

If you do not share the vSwitch with the host OS, then that physical network adapter is not available for the host OS to use and will only be available to virtual machines. If the physical network adapter you created the vSwitch on was for the host OS's management network, then you won't be able to access the host OS anymore.

When you create a VM and give it a virtual network adapter you choose the vSwitch you want that VM's network adapter tied to and can tag it with a VLAN or not.
 
What CoW means to say is.....

When you setup the networking in HyperV, make sure you either "share" the existing network adapter or install another physical network card in your windows 10 machine and use that new adapter for your virtual network.

If your network dropped then you probably told it to "use" the adapter instead of share it. This took control away from windows 10 and gave it to your HyperV network.

Mr Child of Wonder sir... He said he hasn't done much with virtual machine stuff so I had to do a quick translation between uber NSX Cert to laymans.. Although your response did remind me of some good lines in the VMware press networking book!

Nick
@vmnick0
 
Thank you again, as of last night I had time to implement the suggestions and everything is working perfectly.

Thanks again,

*EB*
 
You must log in or register to reply here.
Back
Top