Windows 10: Hyper-V virtualization - Setup and Use in Windows 10

Great guide Kari, I have been meaning to try Hyper-V out for quite a while, just installing Windows 10 on it now.

 

An easy way to make the vm to work smoother is to add virtual processors:



I do this always before even starting the installation. If installation hangs using 1 core, just turn the vm off, add virtual processors and restart.

 

Cheers for the tip *Thumbs

I'm used to VirtualBox but this is a new world *Smile

 

If your guest is Windows 8.1 or Server 2012 R2 or newer, it supports enhanced session mode: Overview: Client Hyper-V Enhanced Session Mode in Windows 8.1

 

Note To keep this thread reserved for the questions related to this tutorial, the information and details about the Hyper-V online meeting have been moved here: Solved Hyper-V 101 - The Basics, a TenForums.com Online Meeting - Windows 10 Forums

 

FYI The wiki is wrong, VMM stands for 'Virtual Machine MANAGER" and is part of the System Center line of products *Wink

 

FYI the short "wiki" is based on this Wikipedia article: Hypervisor - Wikipedia, the free encyclopedia. Until the article in question is changed, I will continue using the word "monitor" instead of "manager". The more I use the same terms as the sources used, the less confusing tutorial we have.

 

Excellent write-up and spot in still!

 

Thanks *Smile

Welcome to the Ten Forums Zeuseason! Check the videos, too:

• Hyper-V Part 1 - Setup: Solved Windows 10 instructional videos by Ten Forums members - Page 52 - Windows 10 Forums
• Hyper-V Part 2 - Create a Virtual Machine: Solved Windows 10 instructional videos by Ten Forums members - Page 53 - Windows 10 Forums

 

Hi Kari, nice job on this. Very useful. I know what a pain it is to put together a useful tutorial, and I commend your efforts.

It would have been even more useful had I seen it before I purchased and installed the VMWare Workstation version 12 upgrade, but that's on me. I can report that VMWare Workstation/Player 12 works fine on a Windows 10 host.

 

There's one part namely the last part of the guide you might want to update a little! First any Windows install to VM is temporary only since it can't activated not being on physical hardwares. A valid key simply is seen as not a valid product key. Have the 64bit 7 Ultimate on the first project and gave that a try for the 28 day VM.

As for the last part regarding Legacy and in particular Linux don't rule out selecting the network switch as you can see from the Linux Mint project using the exact same switch created for 7 when following the steps in the guide here.





As far as seeing the network switch taken care of first that is actually a mandate or run into.... *Eek*cry





OOPS! Something didn't go right! *DohSimply rushing to create the new vhd and see the OS installed means you have to step back and review the guide here! *Smile

 

I have to say I have absolutely no idea about what you are trying to say, don't understand you, don't even know how to reply.

Let's try this way: No, I most definitely see no reason to update the tutorial regarding Windows guest activation.



Note A Windows operating system installed on a Hyper-V virtual machine, regardless of its version can be activated without any issues as long as the product key used is valid. There is absolutely no difference in activating Windows when installed on a physical machine or on a Hyper-V virtual machine.

Of course the same rules apply regardless if activated on physical or virtual machine. When for instance a retail product key has already been used to activate a physical Windows installation, you cannot use the same key to activate a virtual installation.

Wrong!

I have never had any issues in activating any Windows from XP to 10 installed on Hyper-V virtual machine.

In first screenshot below an example, a Windows 10 Pro Build 10525 (upgraded from an activated Windows 7 Professional SP1) Hyper-V vm which I had installed and activated a dozen or so reinstalls and about two years ago in Hyper-V when still using Windows 8.1 and the vm was still running Seven, always exporting the vm before the next reinstall and importing it to Hyper-V in new installation.

Now when I imported it again after clean installing 10525 on my host only two days ago, I suddenly decided to use it as the test vm to see how smooth the free upgrade from Seven to Ten goes. I have several valid retail keys for 7 and 8.1 so even if it didn't work it would not be a big deal.

I imported this Seven vm to a new vm in my fresh installation two days ago, the 25th, it was still activated of course. Upgraded it to 10 build 10240 and further to build 10525. It is permanently activated, subject to of course a new preview build coming before July 16th 2016 when this build 10525 expires:


Let's see two other of my Hyper-V virtual machines. First a Windows 8.1 Pro upgraded to Windows 10 Pro build 10240, the underlying Windows 8.1 Pro was activated without issues and of course Windows remains permanently activated also after the upgrade:



Then Windows 8.1 Pro N on Hyper-V guest. Naturally, this vm is also permanently activated:


The two last examples are not imported from old host, they are fresh clean activated installs on this host after.

Again, no idea what you talking about. Hyper-V and its built-in integration components support Red Hat Enterprise Linux and CentOS Linux. These distros can be set up and installed as any Windows vm, using default components. Installing legacy Windows and other Linux distros it is recommended that you use the virtual legacy NIC.

The part in this tutorial about Linux guests is not yet done, mainly because since the beginning of the Windows 10 I have constantly been reinstalling new builds. Now I might do it when I have time, until that this tutorials gives link to Linux in Hyper-V tutorial at our sister site the Eight Forums. That tutorial is still valid.

 

When referring to the last part that was in regards to the network switch being left at "not connected" when this is the actual first time any Linux distro on any VM has connected online to the web. This is likely to upgrades seen with the other guy's OS there now able to properly detect network adapters as well as virtual adapter used in Windows. I thought I would let you know about the positive result in that area.





As for activation this is what I keep running into using the key that came with the 7 Ultimate full version I've been running since 7 was launched. It didn't come from MSDN or TechNet where those keys are applied to developer builds but the actual retail product bought in a Staples. The conclusion would be that since the key is already is use for the 7 install on the other OS drive it's not being seen as valid for this project even while being booted in 10.

The Bing search for that error brings you to the MS page seen at Windows 7 activation error: 0xC004C008
For some reason it's simply not taking the key on a VM while I just recently saw to a clean install of 7 with the same key in order to upgrade the clean install to 10 on the same physical machine however.

 

Still not understanding you.

The Linux on Hyper-V vm tutorial at the Eight Forums Part 6 of this tutorial links to tells clearly and in logical order how to setup an OpenSUSE vm. I will not do that tutorial for each available Linux distro separately; we are on Windows Forums, that tutorial is only for reference.

These instructions as told in the tutorial are valid for most Linux distros I have tried:

• Set up a Linux VM (step 1.2)
• When setting up the vm, do not connect to a virtual switch (step 1.2.5)
• Add a Private virtual switch to a Legacy virtual adapter (step 1.3)
• Install OpenSUSE (step 1.4)
• When installed, connect the legacy virtual adapter to an external virtual switch for network and Internet connectivity (step 1.4.15)

I am totally unable to understand your point. Following those instructions, the vm will be created, Linux installed, and finally the vm connected to the network and Internet.

I am sorry that you have issues with your product key but that has nothing to do with Hyper-V.

 

Well that's what I have been trying to figure why the same retail key is found invalid except for it already being in use for the 10/7 dual boot. I can't sub with 7 Pro either since that is on the second system's 10/7 dual boot.

As far as connecting online with any distro this was a first seen with Hyper-V where I simply tried the same switch used for 7. I didn't wait to add the switch later but initially as you would have for 7 when testing the other distro. But as we both know there are simply too many flavors to keep track of! It will vary between on which will need Legacy or able to use the Windows type in case someone over at 8F should ask that was the finding here.