Hyper V doesn't start Free Dos due to out of memory error

jimbo45 said:

Hi there
loads of people have helped you out a lot here
Now it's time to sit down and understand a bit about Virtual Machines and their setup and limitations.
It just takes a bit of patience.

Once you've got the basics you'll be in a much better situation about what you want to do exactly and to be able to describe the real problems more accurately.

People have given you enough hints -- as for that one with VMWare - you could have tried it - all the components are free - would have taken you probably all of 15 mins.

People are here always willing to help others but also those being helped also have to show a bit of eagerness to try solutions proposed etc.

I like others have finished with this thread .

Cheers
jimbo

All what I understand from your comments is that Hyper V both sucks and Hyper V is also a piece of both shit, crap, poop, trash and garbage, because Hyper V is both very limited and very problematic, and I should switch from Hyper V to either VirtualBox or VMWare Workload Player or VMWare Workload Pro right now and never ever return/go back to use Hyper V ever again in my both entire and whole life!

Thank you very so much!

Also considering to switch from Windows 10 operating system to either Linux or Unix or MacOS someday too!

By the way:

I have just read that "VMWare Workload Player" does not support snapshots at all but "VMWare Workload Pro" does support snapshots but "VMWare Workload Pro" is not freeware unlike "VMWare Workload Player" so probably that I will have to switch from Hyper V to VirtualBox then.

VirtualBox is the only free option now in hope that VirtualBox does support snapshots at all unlike "VMWare Workload Player"!

Hi there

I never said it was all those things you mentioned -- I did say that it wasn't IMO the best piece of Virtual Machine software I've ever used - especially if you want to run Non Windows VM's on it. It also isn't IMO the most user friendly system for people to use when they are fairly inexperienced with using Virtual Machines in the first place - especially if trying to use it on a Windows system (HOME) for which it wasn't designed for in the first place.

Also if you are running "micky mouse" type OS's like Freedos - who needs snapshots anyway - I've run VM's for years and I can't say that I've ever bothered with or needed snapshots -- others though of course have different needs.

Be careful before assuming people say pieces of Software are a load of brown stuff -- for some situations and people I'm sure HYPER-V works very well --remember it is more targeted at Enterprise server type systems - these servers aren't concerned with games / sound etc but are providing a "Virtual desktop Infrastructure" for their clients.

Cheers
jimbo

Erez said:

...I understand ... is that Hyper V ... sucks ... and I should switch from Hyper V to either VirtualBox or VMWare Workload Player or VMWare Workload Pro right now and never ever return/go back to use Hyper V ever again in my both entire and whole life!!

Hyper-V works extremely well for what it was designed for - to run virtual Windows machines in Enterprise environments. Hyper-V running on servers provides VM workstations for all employees to use.

Initially Hyper-V was only available in Server editions of Windows, starting with Windows Server 2008. It wasn't added to desktop machines until 2012, starting with Windows 8 Pro (or Enterprise). For a Windows guest it works very well (and in enhanced session mode for Pro and above guests). For a non-windows OS VMWare/Virtualbox may be a better choice.