Hyper-V virtualization - Setup and Use in Windows 10  

johngalt said:

What I am saying is that I don't change anthing from when I crreate the VM to when I am able to adjust the size to Full Screen. The first boot, which installs the OS, does not allow - but immediately after rebooting the VM I am able to use full screen mde for it at my monitor's native resolution.

Yes, of course but that's not automatic: you have to specifically select full screen. If using normal mode that can't be even saved, using Enhanced Mode and first time setting it full screen it can be saved.

New Hyper-V feature in build 15002: Hyper-V Quick Create - Create or Copy a Virtual Machine

Tweet

— Twitter API (@user) View on Twitter

Kari said:

New Hyper-V feature in build 15002: Hyper-V Quick Create - Create or Copy a Virtual Machine

Tweet

— Twitter API (@user) View on Twitter

Thanks, Kari. That'll be helpful the next time I do a clean install.

Jerry06 said:

Got a question, do I activate Windows 10 or 7 in the Virtual machine? If I do have to activate the OS in the VM can I use the same activation key that the host is using?

A virtual machine, on whatever virtualisation platform (Hyper-V, VMware, VirtualBox etc.) is always an individual machine. It has its specific hardware signature, own individual SID (Security IDentifier) and GUID (Globally Unique IDentifier).

A VM needs its own license, be it operating system or any software installed. Setting up for instance Hyper-V virtualisation on an activated Windows 10 PRO workstation and installing the same edition, Windows 10 PRO on a virtual machine, the host (virtualisation host = computer used to host and run virtual machines) would of course maintain its activation status but the guest (a VM on a virtualisation host) would not be activated.

Think a VM as any other computer on your network; activating PC1 does not mean PC2 will also be activated. Activating PC1 with a specific product key, that key is flagged as used, PC2 needing another valid product key.

A software example: Let's say you subscribe to Office 365 Home which allows you to install Office desktop suite on 5 computers. Installing it on your host is one install, installing it also on your guest would be another install. Both installs are taken from your quota of 5 installs, leaving you three installs at your disposal. Both installs are considered as being installed on different computers.

Luckily Windows can be installed without product key. In Windows 7 you have a 30 day grace period, you can do your stuff on a VM without activation. Windows 10 theoretically has the same 30 day grace period but it seems there are no or very few limitations even after that period in using it unactivated. Of course the huge watermark will be there saying Activate Windows but that's about it. Also some features like personalisation do not work when Windows is unactivated.

Short version: A virtual machine is an independent machine with specific hardware signature. It needs its own license to activate Windows (or any other operating requiring activation) installed on it.

Kari

You are welcome :)

Kari,

Something seems to have flubbed on my machine. I had stopped usig the Hyper-V mgmt console's VMC feature because of your recommendation to ues RDP instead and it worked perfetly fine through IP build 15002.

Now my host is 15007, and I have successfully logged into eah of my Gust VMs on the host exactly once. I cannot get RDP to see that hte hosts are there, and yet at the same time I don't ge the immediate "Host not found" when trying ot connect via RDP. Using VMC is even weirder. I get a nice big dark screen background with a message stating 'Connecting to {VM}... and a big start buttong underneath - but my VM is already started.

If I click the start button, it resets the VM (as in it turns it off, and then srtats it) - but the screen never chagnes. Incidentally, if I open VMC without having the VM started, I get hte same screen, albeit a bit smaller in size, and the effects are exactly the same as well.

Any ideas on this one?

Takes a while before I can test anything. Due lack of Miracast support (essential for me) I cannot use 15007 on my virtualisation host. I am stuck in 15002 until such a future build that supports Miracast. Third build since the very first one in October 2014 I have to skip, two previous ones were due lack of language packs (also essential).

Anyway, in 15002 both RDC and VMC work without issues. I have 15007 on a few Hyper-V virtual machines, need to enable nested virtualisation and setup Hyper-V on one of those before I am able to replicate your issue and do some testing.

Oh, right, forgot about the Miracast thing.

I'll keep poking at it and see if I can get something working.