Hyper-V virtualization - Setup and Use in Windows 10  

Page 45 of 47 FirstFirst ... 354344454647 LastLast
  1. Golden's Avatar
    Posts : 1,635
    Windows 10 Pro x64
       #440

    Yes, I noticed there is no equivalent to the Guest-Add-On functionality such as that seem in VMWare or Oracle’s Virtual Box......that might be an issue for me.....
      My Computers

  2. Kari's Avatar
    Posts : 17,434
    Windows 10 Pro
    Thread Starter
       #441

    Golden said:
    Yes, I noticed there is no equivalent to the Guest-Add-On functionality such as that seem in VMWare or Oracle’s Virtual Box......that might be an issue for me.....
    An easy method to run both Hyper-V (for Win8 and later guests) and VBox (for Win7 and older guests) on same computer: Run Hyper-V, VirtualBox and VMware on same Computer

    Kari
      My Computer

  3. Golden's Avatar
    Posts : 1,635
    Windows 10 Pro x64
       #442

    Kari said:
    An easy method to run both Hyper-V (for Win8 and later guests) and VBox (for Win7 and older guests) on same computer: Run Hyper-V, VirtualBox and VMware on same Computer

    Kari
      My Computers


  4. Posts : 2
    Win 10 Build 17763
       #443

    I have followed this and every other article I found on setting up and running Hyper-V, but I cannot get it to open up a working window.

    The VM seems to load but is only visible in the preview pane. as screen shot below.

    I would be most grateful if anyone might give me some pointers.

    Thanks.
    Hyper-V virtualization - Setup and Use in Windows 10-hyper-v-screen-shot.jpg
      My Computer

  5. Bree's Avatar
    Posts : 18,615
    10 Home x64 (20H2) (10 Pro on 2nd pc)
       #444

    Welcome to Ten Forums @Griff

    What do you see if you select the 'XP Test' machine in the 'Virtual Machines' pane, then click 'Connect...' in the Actions pane on the right?

    This should open a window connected to the VM. If not, what (if any) error messages do you see?
      My Computers


  6. Posts : 2
    Win 10 Build 17763
       #445

    Thank you for your prompt reply Bree.

    Nothing at all happens if I click on "connect", but if I click on "shut down" then I get an error message
    "XP Test failed to stop. The device is not ready for use (0x800710DF)
      My Computer

  7. Bree's Avatar
    Posts : 18,615
    10 Home x64 (20H2) (10 Pro on 2nd pc)
       #446

    Griff said:
    Nothing at all happens if I click on "connect", but if I click on "shut down" then I get an error message
    "XP Test failed to stop. The device is not ready for use (0x800710DF)
    An XP VM cannot respond to a shut down from Hyper-V manager, it should be possible to turn it off though (the equivalant of powering down a PC without shutting it down first).

    Occasionally I have had a VM that gets stuck and cannot be stopped, turned off or connected to. I've found that a Restart of the host machine can get things working normally again. It may take a long time to shut down but be patient, it should eventually complete the shutdown.

    If you can still access the Settings for this VM, before restarting the host set the Automatic Start Action to Nothing and the Automatic Stop Action to 'Turn off the virtual machine'.
      My Computers

  8. Silky's Avatar
    Posts : 75
    Windows 10 Pro
       #447

    Chnage default swich binding created by Hyper-V


    When I install Hyper-V the default switch it creates is bound to my wireless adapter automatically. As I'm using a wired Ethernet connection on the host, the default switch prevents me from connecting to the internet or network with the VM unless I connect to wireless on the host. I usually run with wireless off and this behavior is a bit problematic for me.

    Is there a way to either edit the default switch to bind it to my Ethernet NIC, or… create a new default switch bound to the wired adapter and delete the original "default" switch?

    I know I can create a new external switch. But I never use wireless on the host, so there's got to be a way to bind the default to the NIC of my choosing. I shouldn't have to do a workaround and I don't need a boatload of network switches.

    Any thoughts on how?
      My Computer

  9. Bree's Avatar
    Posts : 18,615
    10 Home x64 (20H2) (10 Pro on 2nd pc)
       #448

    Silky said:
    I know I can create a new external switch. But I never use wireless on the host, so there's got to be a way to bind the default to the NIC of my choosing. I shouldn't have to do a workaround and I don't need a boatload of network switches.
    Any thoughts on how?

    It's not been a problem for me, as I do use WiFi on my host. But I have in the past messed up and ended up with a boatload on unnecessary network switches (multiple Default switches, only one of which worked).

    To tidy up the mess, I turned off Hyper-V in Windows Features, then turned it back on again. This sets up the Default switch again from scratch. All your VMs will still be there after doing this, if they were set to use the default switch then they will be fully functional. If they were set to use any other switch then you will need to set up their network settings again, either connecting them to the default switch or setting up a new switch.

    Try turning off Hyper-V, temporarily disable the WiFi in Device Manager, then turn Hyper-V back on. Ethernet should be the only available NIC for the Default switch to use. After that I would expect you to be able to enable WiFi again without it becoming the Default switch.
      My Computers

  10. Silky's Avatar
    Posts : 75
    Windows 10 Pro
       #449

    Thanks Bree. I've installed and uninstalled several times and end up with the same scenario so I was thinking about disabling the WiFi adapter and reinstalling. You've just confirmed that this is a reasonable workaround so thanks for that.

    It IS annoying that there is no obvious way to configure Hyper-V to select a network device of your choice given that most PC's that have wireless, also have wired. Isn't wired faster? (that's rhetorical).

    - - - Updated - - -

    Well this is rather disappointing. I disabled the WiFi adapter, re-installed Hyper-V via Windows Features, and the result? The default switch was the appropriate NIC (wired Ethernet - Realtek adapter) and I still get no internet connection. If I then enable the WiFi adapter and turn wireless on, I can connect and move along my merry way.

    So it appears that regardless of whether the default switch is bound to the Ethernet card or the Wireless, I get no internet unless I manually turn on and connect the host to wireless.

    With that in mind, can anyone help me configure Hyper-V to use my default NIC and have internet/network access? I can't believe that I'll have to run Hyper-V with wireless only. Once it's installed on my host, I have no wired network access. I've read through this and several other tutorials on Hyper-V here, and their respective threads looking for some clue about what I may be doing wrong, and frankly....? I can't spot it.

    Thoughts?
      My Computer


 
Page 45 of 47 FirstFirst ... 354344454647 LastLast

Tutorial Categories

Hyper-V virtualization - Setup and Use in Windows 10 Tutorial Index Network & Sharing Instalation and Upgrade Browsers and Email General Tips Gaming Customization Apps and Features Virtualization BSOD System Security User Accounts Hardware and Drivers Updates and Activation Backup and Restore Performance and Maintenance Mixed Reality Phone


  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 16:46.
Find Us




Windows 10 Forums