The sysadmins at my firm just recently switched from VMWare to Hyper-V recently. The feedback I'm hearing is that they wish they did it sooner. It seems that hardware compatibility is much better with Hyper-V.
VMware is picky about hardware. If you stick to mainstream servers and check the compatibility list you'll be fine, but with old hardware or DIY builds (e.g. for a HomeLab) it can be a pain. Being based on Windows means Hyper-V works on pretty much anything.
Hyper-V drastically accelerates Windows VM, even without a real graphics card passed through to the vm. And now it's being used as WSL2 backend makes its death quite a joke. Unfortunately no sound and virtual-gpu for Linux. But it runs Ubuntu server so reliably, that mostly if you have quite good hardware with many cores and 64Gigs RAM, sometimes it is even better to continue running Win11 or Server'22 and put all the nonGUI(Wayland or X11) Linux server infrastructure inside Hyper-v, it will roll it and roll.
In a previous role, we started virtualization with ESXi. But we needed to dozens of Windows Server VMs each year. Licensing this became too expensive, so we soon switched to Hyper-V using Windows Server Data Center, which allowed unlimited Windows Server VMs. It was not as feature rich as ESXi, but for licensing Windows Servers Hyper-V was a god-send for us.
You can use Windows Datacenter licences with ESXi - you can't type the Windows key in to VMware but as long as you've bought the licences to cover the host hardware (and have records to present if audited) you are covered for the unlimited Windows VMs. You still need to pay VMware as well, of course; but as you've discovered past a handful of VMs it becomes more cost-effective to use Datacenter than Standard. It's also nice to be able spin things up for testing without worrying about additional costs!
I have a preference for VMware in fully-licensed environments, but we have customers that use both, and my preference may not be strong enough to stomach all of Broadcom's changes. I use Hyper-V myself at home because VMware thinks backups should be a chargeable extra.
I keep coming across it - both in online comments and real-world meetings. There was some misinformation spread about when 2022 was released and it seems some people still believe it.
And in addition it's the foundation for a lot of security features on the Windows client OS. So yeah, it will stay for a while. BTW, PCI passthrough is called Discrete Device Assignment (DDA) with Hyper-V.
But it was a smart bare metal server to host Guest OS that could run Windows Server 2019 and 2022 R2 and July Updates. Now that resources are cheaper we can probably get away with running the Windows Server Standard and the GUI. They have done a huge job in slimming down the dist and performance of the machine. But don't we think we should run the domain controller as a Guest VM?
Great video. thanks. VirtualBox users, migrate to Hyper V in Windows 10/11 Pro. It is a Type 1 hypervisor, so VMs run much fatser than VirtualBox, which is Type 2.
@@user-uw3yh1vf2v Hi, in Hyper-V architecture the main OS doesn't become a guest OS. The main OS is the "Parent", with direct access to hardware, memory, CPU. When Hyper-V is enabled as a Windows feature in the parent OS, it doesn't become a guest, like VMs. This video, and others on the channel, goes into the detail of the architecture: ua-cam.com/video/hPqoPtUjQa8/v-deo.htmlsi=YhhAEjPe2x685YFo
Think you find HyperV won’t be gone. It’s run Azure and other services like Xbox. Simple. Hyperv Server is now the Azure Stack HCI. Otherwise Server Core is very much the same. However, Proxmox is going well.
MS support for hyper-v and its performance wasnt that good so my former employer switched back to vmware. After working for MS i found out that MS are ditching hyper-v in favour of a linux based hyper-visor they are developing, the code is already in the upstream linux kernel.
Question: you won't have to give Microsoft any more money? Well kind of. If you want to RDP into the server and manage Hyper-V that way then no. If you want a central management solution then you definitely will. You will also have to setup AD (active directory) well at least you used to have to. I switched to proxmox awhile back and i couldn't be happier.
I think you've misunderstood that statement. It is referring to the retirement of Hyper-V Server and replacing it with Windows Server Hyper-V. The point being that the only extra cost for the latter would be for the host itself, but if you have even a single Windows VM you've already paid for it. You don't need System Center or Active Directory to run Hyper-V, although a domain is usually recommended (and likely covered by the aforementioned Windows licence you probably have). You can manage it from your workstation as well - you don't need a server to do it, just any computer that runs Windows Pro or above. Most people using Hyper-V are running Windows so this a non-issue unless you’re trying to run a completely non-Windows infrastructure on a Windows platform. I know lots of people who are happy with Proxmox at home, but I have yet to meet anyone who is running it in production. I know some people do, but they’re very few and far between right now. I suspect with Broadcom's changes Proxmox will pick up a few customers in the coming months. For me to consider Proxmox in production they need to implement 24/7 support, integration with proper (industry standard and application-aware) backup solutions like Veeam, and they probably need to have decent support for SAN storage (external iSCSI + fibre channel from the big names). Right now, vendors don't care to support Proxmox because they have no business market share to speak of; but I think this is an opportunity for them to gain customers and up their game. It will be interesting to see if Proxmox capitalises on the Broadcom fallout - it could be the chance they need to make the jump from being primarily a hobby platform to mainstream business use.
For 20 years all server editions of windows server has allowed 2 free simultaneously admin users to rdp into that server. So no rdp license is required for this setup and it's always been that way. There's no requirement to enable terminal services for this to work but only enable and allow rdp into that server.
MS realized that any enterprise that would run more than 6 MS VMs on Hyper-V would spend the $6k on a Datacenter license and then run all the VMs they wanted. So, there was no need for the free version of Hyper-V. Anyone who was not going to run MS VMs, instead running dozens of Linux VMs, was not going to even use Hyper-V, and thus would not need the free version. The free Hyper-V had no place anymore.
vSphere to my mind is a superior product, but Hyper-V has proven scalability (see Azure) and the sort of ecosystem integrations most businesses demand. That's why it's the second choice in the market. What do you recommend as a replacement?
@@TEverettReynolds using SCVMM? You must have an entire system center department then. Or have found training that even Microsoft themselves doesn't offer.
The sysadmins at my firm just recently switched from VMWare to Hyper-V recently. The feedback I'm hearing is that they wish they did it sooner. It seems that hardware compatibility is much better with Hyper-V.
VMware is picky about hardware. If you stick to mainstream servers and check the compatibility list you'll be fine, but with old hardware or DIY builds (e.g. for a HomeLab) it can be a pain. Being based on Windows means Hyper-V works on pretty much anything.
Hyper-V is game changer
Hyper-V drastically accelerates Windows VM, even without a real graphics card passed through to the vm. And now it's being used as WSL2 backend makes its death quite a joke. Unfortunately no sound and virtual-gpu for Linux. But it runs Ubuntu server so reliably, that mostly if you have quite good hardware with many cores and 64Gigs RAM, sometimes it is even better to continue running Win11 or Server'22 and put all the nonGUI(Wayland or X11) Linux server infrastructure inside Hyper-v, it will roll it and roll.
In a previous role, we started virtualization with ESXi. But we needed to dozens of Windows Server VMs each year. Licensing this became too expensive, so we soon switched to Hyper-V using Windows Server Data Center, which allowed unlimited Windows Server VMs. It was not as feature rich as ESXi, but for licensing Windows Servers Hyper-V was a god-send for us.
You can use Windows Datacenter licences with ESXi - you can't type the Windows key in to VMware but as long as you've bought the licences to cover the host hardware (and have records to present if audited) you are covered for the unlimited Windows VMs. You still need to pay VMware as well, of course; but as you've discovered past a handful of VMs it becomes more cost-effective to use Datacenter than Standard. It's also nice to be able spin things up for testing without worrying about additional costs!
@@ProTechShow Does AVMA license activation still work if the host hypervisor is ESXi rather than Hyper-V?
AVMA only works with Hyper-V. With VMs on ESXi you'll enter a regular activation key on the VM instead of the AVMA key.
As a hyper v user in the enterprise and home lab , I love it and use it and making work with all my servers all across the world
I have a preference for VMware in fully-licensed environments, but we have customers that use both, and my preference may not be strong enough to stomach all of Broadcom's changes. I use Hyper-V myself at home because VMware thinks backups should be a chargeable extra.
I hate it
WSL2 also relies on Hyper-V, with Hyper-V running bellow the NT and Linux Kernel.
Yup. Docker too, and a few other things.
Hyper-V is awesome, who has even suggested that?!
I keep coming across it - both in online comments and real-world meetings. There was some misinformation spread about when 2022 was released and it seems some people still believe it.
Hyper-V is basically the entirety of Xbox and Azure so I don't think they will ever discontinue it.
KVM is probably better thanks to PCI passthrough.
And in addition it's the foundation for a lot of security features on the Windows client OS. So yeah, it will stay for a while. BTW, PCI passthrough is called Discrete Device Assignment (DDA) with Hyper-V.
But it was a smart bare metal server to host Guest OS that could run Windows Server 2019 and 2022 R2 and July Updates.
Now that resources are cheaper we can probably get away with running the Windows Server Standard and the GUI. They have done a huge job in slimming down the dist and performance of the machine. But don't we think we should run the domain controller as a Guest VM?
Hyper-V made me stay on Windows.
I would love a bare bones ver of hyper-v
Andrew, please make some videos on containers and docker
Great video. thanks. VirtualBox users, migrate to Hyper V in Windows 10/11 Pro. It is a Type 1 hypervisor, so VMs run much fatser than VirtualBox, which is Type 2.
Thanks 🙂
@@user-uw3yh1vf2v Hi, in Hyper-V architecture the main OS doesn't become a guest OS. The main OS is the "Parent", with direct access to hardware, memory, CPU. When Hyper-V is enabled as a Windows feature in the parent OS, it doesn't become a guest, like VMs. This video, and others on the channel, goes into the detail of the architecture:
ua-cam.com/video/hPqoPtUjQa8/v-deo.htmlsi=YhhAEjPe2x685YFo
KVM + ZFS is the future.
Think you find HyperV won’t be gone. It’s run Azure and other services like Xbox. Simple.
Hyperv Server is now the Azure Stack HCI. Otherwise Server Core is very much the same.
However, Proxmox is going well.
Yeah, Hyper-V is going to be around for a long while yet
KVM or BHyve + ZFS are where it's at.
MS support for hyper-v and its performance wasnt that good so my former employer switched back to vmware. After working for MS i found out that MS are ditching hyper-v in favour of a linux based hyper-visor they are developing, the code is already in the upstream linux kernel.
They're not ditching Hyper-V. The kernel contributions they made are to improve support for Linux guest VMs running on Hyper-V.
@@ProTechShow Indeed. It's in Windows Server 2025 and not going anywhere (and Windows Server 2025 is supported for 10 years from GA)
Question: you won't have to give Microsoft any more money? Well kind of. If you want to RDP into the server and manage Hyper-V that way then no. If you want a central management solution then you definitely will. You will also have to setup AD (active directory) well at least you used to have to. I switched to proxmox awhile back and i couldn't be happier.
I think you've misunderstood that statement. It is referring to the retirement of Hyper-V Server and replacing it with Windows Server Hyper-V. The point being that the only extra cost for the latter would be for the host itself, but if you have even a single Windows VM you've already paid for it.
You don't need System Center or Active Directory to run Hyper-V, although a domain is usually recommended (and likely covered by the aforementioned Windows licence you probably have). You can manage it from your workstation as well - you don't need a server to do it, just any computer that runs Windows Pro or above. Most people using Hyper-V are running Windows so this a non-issue unless you’re trying to run a completely non-Windows infrastructure on a Windows platform.
I know lots of people who are happy with Proxmox at home, but I have yet to meet anyone who is running it in production. I know some people do, but they’re very few and far between right now. I suspect with Broadcom's changes Proxmox will pick up a few customers in the coming months. For me to consider Proxmox in production they need to implement 24/7 support, integration with proper (industry standard and application-aware) backup solutions like Veeam, and they probably need to have decent support for SAN storage (external iSCSI + fibre channel from the big names). Right now, vendors don't care to support Proxmox because they have no business market share to speak of; but I think this is an opportunity for them to gain customers and up their game. It will be interesting to see if Proxmox capitalises on the Broadcom fallout - it could be the chance they need to make the jump from being primarily a hobby platform to mainstream business use.
For 20 years all server editions of windows server has allowed 2 free simultaneously admin users to rdp into that server. So no rdp license is required for this setup and it's always been that way. There's no requirement to enable terminal services for this to work but only enable and allow rdp into that server.
Hyper-V is dead - only for the LINUX DEVOTESS 🤣
Thank you, finally a clear view on Hyper-V 😍
You're welcome!
Great video
Thanks!
MS realized that any enterprise that would run more than 6 MS VMs on Hyper-V would spend the $6k on a Datacenter license and then run all the VMs they wanted. So, there was no need for the free version of Hyper-V. Anyone who was not going to run MS VMs, instead running dozens of Linux VMs, was not going to even use Hyper-V, and thus would not need the free version.
The free Hyper-V had no place anymore.
Always preferred Hyper-V anyway.
Hyper-V has better, more mature replacements already.
vSphere to my mind is a superior product, but Hyper-V has proven scalability (see Azure) and the sort of ecosystem integrations most businesses demand. That's why it's the second choice in the market. What do you recommend as a replacement?
KVM is much better
Hyper-v is dead. Anyone who's touched SCVMM or had massive issues with hyper-v understand.
Yes, the free version is actually gone, but the product itself is not worth the trouble, even with Premier Microsoft Support.
@@user-uw3yh1vf2v they forgot to sacrifice an iMac to the Azure alter of BillyG before rebooting, obviously.
We run dozens of Hyper-V servers hosting hundreds of VMs. We don't see any Hyper-V-specific issues.
@@TEverettReynolds using SCVMM? You must have an entire system center department then. Or have found training that even Microsoft themselves doesn't offer.
Proxmox VE > HyperV
I tested proxmox with zfs for a while and its horrible stability cache, poor VM performance