@black3dynamite said in MS weird Hyper-V 2019 pull ?:
@Emad-R said in MS weird Hyper-V 2019 pull ?:
@black3dynamite said in MS weird Hyper-V 2019 pull ?:
@Emad-R said in MS weird Hyper-V 2019 pull ?:
Another Reason why KVM is superior.
Btw I tried Hyper V manager on Win10, and used Gen2 VMs as oppose to using my standard VMware Workstation or Player or VirtualBox, and I was unable to complete the OS install cause it did some checkups on the VM and ISO and told me that the licensing was not valid, however I think cause I slipstreamed offline updates on the ISO that caused the issue.
It feels when you even wish to try MS stuff, they try to give you the finger some how.
How much RAM did you assign to the VM?
It was not RAM issue, it literraly came up and told me you dont have valid license
e85ca49c-edc1-449d-a868-a7084bd18e1a-image.png
The same ISO works perfectly in VMware, what they think we should buy stuff and support without testing it first for the first decade or so.
This is why I asked about the RAM.
Ok I give you that, A feature that they enabled called
dynamic memory
breaks the install of their very own Win10 install. Even though they could have made better error log.
But when I wanted to use VMware Worksation again i was blocked. It gave me another error after Hyper-V got installed. Like WTF breaking the leader in Virtualization to promote your own shit. apparently Vmware WS and Hyper-V can not go exist. so i said screw it, never again, I will learn hyper V if i was forced in company but no need to bother with it now .