HYPER-V does seem to have improved over the last year or so - But :
it might have been fixed now but USB support was always a bit problematical in HYPER-V -- even now I'm not sure if USB3 support is available for GUESTS in HYPER-V. VMware workstation has the ability to set USB2/USB3 support in the VM settings for any particular guest. If your machine has USB3 ports and you use things like external USB HDD's for movie servers etc on your GUEST system then the performance difference between USB2 and USB3 is absolutely worth it..
VM's using HYPER-V seem also to have a problem when you want to connect a lot of external peripherals to them (probably because of the USB problems) - however in the case of external HDD's you can I suppose share those by attaching them to the host and using network sharing. The disadvantage of this is you can't then build a 100% isolated GUEST if you have to share external devices with the Host.
I also tend to dislike having to use RDP (Remote Desktop) as the console to communicate with the GUEST VM's -- if you run your VM's on a remote machine RDP protocol is really slow compared with the full network speed - even on a wireless connection (assuming decent broadband / networking).
But attempts to setup ubunto 15.04 repeatedly and miserably failed.
(I followed your instructions for setting up Linux & Ubuntu in Hyper-V Windows 8.1 host).
Hyper-V virtualized half my RAM (8 GB) without my knowledge. It also cut my internet connection because it changed my "Ethernet" setup, however, reversing this was fairly easy.
But all attempts at retrieving my RAM failed, even after "uninstalling" Hyper-V through "Programs and Features" then "Turn Windows features on and off" then unchecking "Hyper-V".
How could I retrieve my "virtualized" RAM ?
In this very thread I have posted quite simple explanation for that:
Hyper V or VMWare? - Windows 10 Forums
You have plain and simple user errors. I recommend you to read the instructions really through before trying something new, something you do not understand.
I did not make "simple user errors" because it was all made by Hyper-V in Windows 10 on following your own instructions. I actually made a single "simple user error": I trusted your abrupt "No" reply to my question about Hyper-V making changes to my Windows 10 setup.
May be you were drunk when you wrote your arrogant and offensive reply to my simple question and request for help.
I do understand what I do extremely well, I have been using computers since they started with DOS and Windows 3.
And I have scientific qualifications much higher than your ego can comprehend.
Please try to understand this:
- Hyper-V does never - I repeat: never - "virtualize" your RAM when it's not used and no virtual machines are running.
- Hyper-V does not make any changes in your system. Nada. Of course it creates some folders but that's it.
- As is well documented both in the Hyper-V virtual switch tutorial at the EF and all other Hyper-V tutorials at EF and here at TF, to connect your virtual machines to the Internet you need to create and use external virtual switches. If you don't need Internet on your virtual machines, you don't have to create external switches, in which case your host uses Internet as always. However, if your virtual machines need Internet, also your host needs to use an external virtual switch.
- Creating an external virtual switch as instructed does never break your Internet connection.
- Most of my tutorials are written under influence. That's my way.
- I believe I speak not for myself but also for other tutorial makers saying that not a single tutorial of mine will be posted before it has been thoroughly tested, the method in it used in real life scenarios. My way is to print what I have written, take a virgin computer and follow my written instructions as if I had absolutely no idea about the procedure, just the written instructions. I repeat this a few times and first then post the tutorial.
- Statements like "Hyper-V virtualized half of my RAM" and "It also cut my Internet connection because it changed my Ethernet setup", both totally absurd, tell it quite clearly that you tried something you do not understand. I am sorry for that.
Download took about two minutes, setting up a vm in Hyper-V as instructed in the tutorial about a minute, and finally 11 minutes to install Ubuntu following the instructions to the letter:
It's 08:50 now here (8:50 AM), as you can see this vm was created not 15 minutes ago, Ubuntu installed and online:
I run Windows 10 Pro.
My copy of Ubuntu 15.04 was downloaded in July. I used to "try it out".
I had initial difficulties setting up Hyper-V in Windows 10 Pro. A kind member of the appropriate thread replied to my request for help and advised me to turn off all other apps, AV, etc. I did and it worked thanks to his kind and polite advice. Having difficulties setting up a feature of Windows 10 because of this very simple issue indicates that some one somewhere in Microsoft did not know about the potential problem and did not write a solution to it and did not write an appropriate Error Note or an appropriate link to it; why should a mere mortal like me click on a link to find himself in the middle of no where related to his problem such as .NET Framework 3.5 ?!!!
You refer users of TenForums who wish to setup a Linux distro on Windows 10 to your own tutorial in Windows 8.1 because you have not written a specific tutorial for that on Windows 10.
I followed your directions very carefully and several times indeed, before giving up and unistalling Hyper-V in Windows 10 Pro.
I expected to find no changes to my system as you emphatically told me with your "No". But I found the following after-effects of Hyper-V:
- A virtual desk folder, this was easily deleted (it was empty).
- The driver for my Ethernet Realtek was removed, I knew that from the troubleshooter and I successfully and easily re-installed the driver and was re-connected again.
- I noticed that my system was slowing down and stalling on a few occasions, looked at my system properties and System - Performance Monitor and found that my RAM had gone down from 16 to 8 GB. I tried to find out the cause or troubleshoot it and found the following in System Information:
I did not include the snapshots when I reported these problems, but here they are.
I expected to receive practical advice. I would have been happy if the reply was negative. But I must admit I never expected this barrage of ridicule.
I think I should learn not to complain about Microsoft products. This, anyway, is not as bad a problem as uninstalling Microsoft Office 2016 caused, I solved most of the problems but am still struggling to retrieve my July-November email messages that have completely disappeared from Microsoft Outlook 2013 on my desktop, the messages are still there on the Outlook.com server, but for some reason Outlook 2013 synchronizes and downloads the all the messages before and after but this Black Hole in history !!!
The moral of the story is that may be we should all accept that Microsoft products are not all perfect or behave according to particular and regular expectations within different environments.
Sorry to interfere, as an advice to anyone else: If you experience any issue, first make sure you have installed and enabled all the relevant features in Windows and that you have updated drivers when applicable. For example I read somewhere in this thread about Microsoft .NET 3.5. You should have enabled it since not only Hyper-V but many other applications require it and they won't work properly no matter what you do, unless you enable it. So before complaining again, first make sure you have installed and enabled all the relevant features. It's not Microsoft's fault if you didn't. And NO, there is not excuse because most of the times a popup window will inform that you need to enable a specific feature. If you just dismiss it and don't do it, the fault is YOURS.