Hyper-V & Win10

  1. Posts : 3,502
    Win_8.1-Pro, Win_10.1607-Pro, Mint_17.3

    Hyper-V & Win10

    I decided to install Win10 in a Virtual Machine and settled on Hyper-V.

    I'm using the setup now to create this thread. There were a few hurdles to get over.

    1) Hyper-V needed to be added to my Win8 install
    Program & Features-> Turn on Windows features->Hyper-V
    When things didn't work, I went back to P&F only to find that the platform option was inactive (greyed out)
    Some of Hyper-V installed (manager and config), but not the platform

    This required a BIOS change (HP InsydeH2O BIOS is not always friendly)
    Searching didn't provide much help, so I took a gamble and enabled SVM - turns out that is Secure Virtual Machine
    - most results referred to Intel Virtual Technology (VTx) and pointed to BIOS system configuration - I have an AMD processor.

    I was able to turn on the Hyper-V platform.

    Building the VM wasn't all that difficult - you could use the express install, but I wanted to know more, so it was a custom setup.

    The nice thing was you can install Win10 directly from the ISO file. There was a hiccup when I hit finish (before the install began). I changed boot from HDD (VHD) and it complained about no OS, so I went back to the DVD (vDVD) with the Win10 ISO mounted and the install began. It didn't take very long - maybe 45 minutes ... maybe.

    I looked around a bit - not much different than 7 & 8 so the learning curve won't be too bad

    Then I tried to connect.

    Ok, this wasn't easy at first.

    In Hyper-V Right click your local host (it was the physical machine's name in my case)
    select Virtual Switch Manager

    Add an internal network
    Back to the physical machine
    Select properties of the vWLAN and change the adapter from Ethernet to Wireless
    Select both the vWLAN created in the Virtual Switch Manager with the physical Wireless adapter and right click
    Select Bridge from the alt menu
    this creates another entry in network
    Network Bridge with the physical adapter name (or unidentified network if inactive)

    This thread was written while I was trying to figure it out myself. The protocols installed were wrong for a VM switch function. It worked, but it was flaky - both bridge and the physical adapter had IP protocols and Attachment 5653the bridge I kludged did not have the Hyper-V protocols.

    Setup up the network connections per Kari's tutorial. Create the Virtual Switch as an
    External switch

    Hyper-V virtualization - Setup and Use in Windows 10


    After that - I'm up and typing.

    This is a pretty sweet Preview release. I haven't really played too hard, but it feels solid.
    Last edited by Slartybart; 08 Oct 2014 at 08:17. Reason: correct the Virtual Switch
      My Computer

  2.   My Computer

  3. Posts : 14,050
    Windows 11 Pro X64 22H2 22621.1848

    I can't get the internet connection to work. I'm using Ethernet rather than WLAN but all I get is Cable

    Windows 8.1 Host

    Hyper-V & Win10-hyper-vnetworkprobhost.jpg

    Windows 10 Client

    Hyper-V & Win10-hyper-vnetworkprob.jpg
    Any idea what I'm doing wrong?

    Never mind, figured it out. You left off a step where I had to go into the VM settings and connect the Network to the new Bridged one I just created. Did that and it works great.
    Last edited by Ztruker; 07 Oct 2014 at 20:13.
      My Computers

  4. Posts : 17,661
    Windows 10 Pro

    Ztruker said:
    Never mind, figured it out. You left off a step where I had to go into the VM settings and connect the Network to the new Bridged one I just created. Did that and it works great.
    That's not a good way to do that, bridging an internal switch by yourself does not setup the bridge correctly.

    This from the tutorial, discussion about this subject:

    Kari said:
    Slartybart said:
    I created a Network bridge between the physical wireless adapter and the virtual adapter, selecting wifi in the bridge properties. This might be due to the fact that I chose an internal virtual adapter instead of external when I set up the Win10 VM. Some quick research mentioned it was more secure - it's all new to me.
    Internal switch is more secure because it has no Internet access, it can only communicate with the local network. A bridged internal switch is no longer internal switch.

    Slartybart said:
    One note - I mucked around with the virtual adapter, changing some options - that produced a warning dialog telling me that all options would be disabled (including IP4 and IP6-I can't recall if it said the physical or the virtual). So I canceled and left it alone.

    The bridge makes my connections go limited as it tries to connect to a machine that might not be running, but it clears up in a few seconds and my Internet connection doesn't seem to be affected.
    As soon as you created the bridge, your internal switch became external. The setup you have now is an external switch setup, you are most definitely not using internal switch. This is important to understand so I repeat it: An internal switch is a switch which is connected to local network only but has no internet access. To connect to Internet you need to select an external switch. Bridging an internal switch will create a de facto external switch but can bring connectivity issues.

    This from my tutorial at Eight Forums:

    A Virtual Switch can be external, internal or private.
    • External Virtual Switch: will connect a vm to host NIC. If host NIC is connected to Internet through router, the vm is also connected to Internet. If host NIC (LAN) is not connected to router or if the router has no Internet access, the internal network will still work allowing computers (physical and vm) belonging to the same subnet and workgroup or domain to communicate with each other (file and media sharing etc.). When connecting external switch to host WLAN NIC, the vm loses all connectivity when WLAN is disabled or not connected on host.
    • Internal Virtual Switch: When a virtual NIC is connected to Internal VS it can communicate with other computers and vms on the same subnet but has no Internet access.
    • Private Virtual Switch: When a virtual NIC is connected to Private VS it can communicate with other vms on same Hyper-V server but cannot communicate with host PC nor has it Internet access. A Private vs is often needed when installing a legacy Linux or pre-XP Windows vm. After installation you need then to disable Private Switch and use Internal or External to connect to the network.

    In your case, to get rid of those minor issues, I would disconnect and delete the bridge, create an external switch and change settings for each of your virtual machines to set them use the external switch you created.

    When you create an external switch assigning a WLAN adapter to it, Hyper-V takes care of creating the bridge with correct settings.
    Tutorial: Hyper-V virtualization - Setup and Use in Windows 10. Written for Windows 10, works exactly the same way in Windows 8 & 8.1.

    Last edited by Kari; 07 Oct 2014 at 20:53. Reason: Added quote
      My Computer


  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 05:21.
Find Us

Windows 10 Forums