Hyper-V virtualization - Setup and Use in Windows 10

Fronk · 15 May 2016

Cliff S said:

I currently have a 512GB 850 PRO for the Host OS and use 485GB of a 1TB 850 EVO for the VM's. As the VM's are also operating systems, albeit virtual, placing them on an SSD, sppeds them up. They are not just data that's called up into memory to be used, they are read and written to, and the I/O operations are much faster this way.
As they don't have all the software loading, on them as my host does, they even "boot" much faster than my PC does.

Oh Crap.
That matches what i thought then.( the petrol head theory still applies).
Or-the power needs to be applied closest to where it is needed most and connected to it.
Translation =pure power and speed rules>Vmware or any other resource hungry program needs too "be in and run from" a location that can support that exclusively . i.e in the same way a primary OS needs to.
I also assume that this would generally mean the primary source dictates the outcome and that the only exception to that is files/dlls/etc not necessary to the functioning of "that " program can be called from a less efficient source/storage location.
Which is in my case is not only another drive but" the program itself is running from another drive". Yipes

Looks like i have to upgrade in the SSD dept

Cliff S · 15 May 2016

Of course there is what I have learned from Kari & essenbe, it also depends on how much CPU(cores/threads) and RAM you allot your VM's too.
This is where Hyper-V beats VMWare, as it has Dynamic Memory and one created and switched to, will only use memory when the VM is in actual use.
Read this at TechNet: Hyper-V Dynamic Memory Overview

Fronk · 19 May 2016

I have just installed and tried Virtual box,this has been a dramatic change for me(no idea as to why).
The Vm's respond as i would like.
I don't know what has caused my issues but for some reason my machine just does not like or get along with Vm-ware, go figure.
I have even been able to install win 10 on this "with hyper-v on that".( it has failed as expected up to launch of actual VM)
I assume this is because virtual box has been detected and Hyper-v installation is not complete due to that.
What a Hoot--------

.
I might uninstall virtual box and see what happens if i re initialize hyper-v and try to run the the Vms i have with Hyper V.
None of the software soft ware like to play nice together, it looks like they detect each others presence and then refuse to work.....LOL

.

drburdi · 02 Jul 2016

Kari said:

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:

Attachment 36124
(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.

Problem Solved - hooray! Had to do a fresh install of windows 10 since something was messed up when I updated from windows 8.1. However even then I could not get the virtualxp to print. After months and months of searching the web and trying different variations to this tutorial I came across a post which recommended to install the virtual printer using as herein suggested through a local port but with a \\host computer\printer name location, not the tcp. This still did not work until another reader stated that one needs to shut down the virtual and restart the host. Behold the virtual printer did print. Thank you Kari for spending so much time with me in trying to solve my problem. Maybe this post will help others having the same difficult time as I did.

oseose · 06 Aug 2016

Thanks for sharing

johngalt · 13 Dec 2016

Kari - in making all these Vms for testing since 14986 came out, I've noticed something odd.

I'm using 14971 ESD-based .ISO to create these VMs. In hte VMs, instead of restarting after installation to complete the post-install setup, the VM invariably hangs, then BSOD appears and it reboots muhc faster than I am able to read the info on th BSOD.

Have you been experiencing anything like this?

Kari · 13 Dec 2016

johngalt said:

Have you been experiencing anything like this?

No, in fact I believe I've not had a single BSOD on Hyper-V virtual machines in at least a year. I've never used ESD based ISO for install, not saying that 's the reason for your BSOD just stating a fact.

Wynona · 17 Dec 2016

Whoooooooooeeeeeeeeeee, I finally tried Hyper-V once more and I think I have it!

I had to tell it I'll install the OS later, though, since I have my ISO of Build 10971 on a flash drive and couldn't figure out whether I could use it or not.

Kari · 17 Dec 2016

Wynona said:

Whoooooooooeeeeeeeeeee, I finally tried Hyper-V once more and I think I have it!

I had to tell it I'll install the OS later, though, since I have my ISO of Build 10971 on a flash drive and couldn't figure out whether I could use it or not.

Nice! Now to test it :)

You can get 14981 PRO x64 ESD file here: Insider Announcing Windows 10 Insider Preview Build 14986 for PC - Page 27 - Windows 10 Forums

... and make an ISO from it: ESD to ISO - Create Bootable ISO from Windows 10 ESD File - Windows 10 Tutorials

Kari

Wynona · 17 Dec 2016

Kari said:

Nice! Now to test it :)

You can get 14981 PRO x64 ESD file here: Insider Announcing Windows 10 Insider Preview Build 14986 for PC - Page 27 - Windows 10 Forums

... and make an ISO from it: ESD to ISO - Create Bootable ISO from Windows 10 ESD File - Windows 10 Tutorials

Kari

Thanks, Kari. I forgot I got that when you posted the other day. I just hadn't created an ISO, since I wasn't thinking in terms of a clean install just yet. :)

If I use the Image file (ISO), under Installation Options, will that be using my flash drive?