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

I have not given up. I need to figure this one out since I have 2 other computers which will be running Win10 that I need to install Hyper-v. So what should I do next?

 

Have not heard from you all week. Vacation?
Incidentally this problem existed when I had win8.1 and carried over after upgrading to win10.

While waiting for a reply I went back to 4.6 and removed my virtual switch, continued with 5.1, the 4.9 onward. Reinstalled a local printer in virtual and still unable to print. Don't know what else to do except delete my virtual setup entirely and start over. Wondering if this would eliminated my xp setup to where I would have to install xp again, which would be a problem since I don't have my xp program disk anymore. Where would I get the program again? (I still have the key.}

Or do I need to do something else to discover the problem?

 

I am sorry but to be totally honest I took that quite badly, it's as if you are accusing me of something. For your information my last response to you in this thread is from 2 days ago:


(Click to enlarge)
Since that you have not told anything new, anything that would change the situation, anything that would help me to find something else to suggest.

All of us here at the Ten Forums are doing this voluntarily, in addition to our real life. It's a hobby, not a profession. On these forums in general and my own tutorial threads in particular, I am as active as my real life and other stuff allows.

That being said, I have nothing else to suggest. I have no issues in getting a Windows XP Hyper-V virtual machine to work correctly in my network, including printing to host printer.

 

Sorry you feel that way. I don't see where I accused you of anything or meant to do it. Sorry.

Realize that I have been trying to resolve this problem for many days, feeling very frustrated, and is very time consuming to me as well as you. Frustration brings out a tone that is not normal for me. Sorry again and I really do appreciate all the time you also spent trying to resolve my difficult problem.

 

Hi - I am a newie and not too computer literate but trying hard to get my older desktop to start Hyper-V after doing the upgrade to Win 10 and this great tutorial. Upon starting Hyper-V I get the failing message that hypervision is not running. I noticed that it is grayed out in windows features. Running CoreInfo shows everything good, I think. In running another info program it says that I do not have SLAT capability, even though AMD says my Athlon X2 Dual Core 4850E processor is capable of running Hyper-V. I checked my bios and could not find anywhere to turn it on. Any approach to a solution or ability to fool the computer in thinking that it has or does not need SLAT?

Incidentally, I did have Virtual PC XP Mode running when I had Windows 7 Pro on the computer.

I forgot to include 3 views of the coreinfo output. Maybe it would be helpful to someone more knowledgeable than I.

 

Hi Kari,
First of all thank you for the brilliant post.
I tried to follow all your instructions but got stuck at the very beginning. When I Turned on the Hyper-V feature it did not ask me to reboot. However I did. After the reboot when I started the Hyper-V Manager, it did not show my comp name in the left-hand pane. I said 'Connect to Server' and selected 'Local Computer' and got the following error:

An error occurred while attempting to connect to server "MyCompName". Check that the Virtual Machine Management service is running and that you are authorized to connect to the server.

The operation on computer 'MyCompName' failed: Invalid class

I verified in the Services and there were no such a service - Virtual Machine Management.

Any ideas?

 

followed the procedure, didn't realise until the end that using XP requires a different procedure.....so had to delete everything and start again....maybe at step 4,6 there should be a note to skip to step 5,1.... also why are steps 5,3 to 5,6 required for XP and vista but not for W7 & onwards.....would like to understand the reasons......would be excellent if a separate procedure could be written for legacy OS, to save jumping about through this one........I followed everything, but was told at the end that no OS found....also in image 4,8 there is NO option to use a cd/DVD for installing the OS I had to create an ISO image first.........

 

This quote from the very beginning of this tutorial:

The same titles used in the list of contents are used for each part. I am very sorry about you having difficulties to understand the tutorial but really, I could not make it any clearer and easier to follow: You go through parts 1 through 3 to set up Hyper-V, then according to which OS you want to install you select either Part 4 for Windows guests with Windows 7 or later, Part 5 for legacy Windows (Vista or earlier), or Part 6 for Linux.

Because the New Virtual Machine Wizard does not allow selecting a legacy network adapter which is needed for legacy Windows virtual machines to connect to the network. The tutorial has not a single unnecessary step.

But I have written separate instructions for legacy Windows guests! It's called "Part Five" in this tutorial!

Maybe if you read the tutorial first taking your time in trying to understand it and then followed it logically and to the letter? If and when you install Windows guest on Hyper-V following these instructions to the letter, it works; "OS not found" error is plain and simple a user error, the user has done something wrong.

Please tell me how much easier to understand and clearer I could make this? Quote from the tutorial, step 4.8 which you mentioned:

To be totally honest I cannot see how I could change the tutorial to be any easier to understand? If it as it is now is too difficult to understand for some users, maybe the reason is somewhere else, not in the tutorial?

 

your reply is not very polite.......I admit I missed the beginning contents list and went straight into the procedure, ' my mistake '
what I was trying to sayi about image 4.8 that when I got to this stage there was NOT the option to chose a DVD drive only an ISO image, maybe my W10 PRO is different than the one used for this tutorial.....
obviously I am a bit of a thicky......so will remove what I have done and try again......
thanks

 

My response was accurate and valid, honestly and to best of my knowledge answering each and every point you made. There's nothing even remotely impolite in it. It is quite difficult to answer to someone when all the issues and questions presented are based on the user in question not understanding something.

The option to use a physical DVD install media is always there, except when installing 2nd Generation virtual machine; to install OS on 2nd Generation (UEFI) vm, only ISO image is accepted as install media. See tutorial steps 4.4 to 4.8.

 

ok enough said......

 

put this in my other post, but the XP install disk was faulty failed to install, had to press F3 to exit, is there a way of restarting the XP install ( I have another disk ) or should I start again ?

thanks

 

Just shut down the vm and go to its settings, change the DVD or ISO to the new one:




Save the settings and reboot the vm.

 

Nested virtualization added to Hyper-V in Build 10565 released on Monday 12th of October 2015!

Read more: Windows Insider Preview: Nested Virtualization - Windows Virtualization Team Blog - Site Home - TechNet Blogs

 

Kari

.. yes, beverages are alway good to have while learning and writing. thanks.. Cliff M.