Why is Hyper-V More Confusing
-
@scottalanmiller said in Why is Hyper-V More Confusing:
@Breffni-Potter said in Why is Hyper-V More Confusing:
I don't see how replacing the underlying FREE hypervisor fixes Microsoft licensing nightmares.
Because an entire category of those nightmares are exclusive to confusion around Hyper-V. Remove Hyper-V and that entire range of issues simply stops existing.
But you've just moved those issues into XS?
What licenses are needed for the core hypervisor and what licenses do you no longer need to buy by using XS?
-
@Breffni-Potter said in Why is Hyper-V More Confusing:
@scottalanmiller said in Why is Hyper-V More Confusing:
@Breffni-Potter said in Why is Hyper-V More Confusing:
I don't see how replacing the underlying FREE hypervisor fixes Microsoft licensing nightmares.
Because an entire category of those nightmares are exclusive to confusion around Hyper-V. Remove Hyper-V and that entire range of issues simply stops existing.
But you've just moved those issues into XS?
What licenses are needed for the core hypervisor and what licenses do you no longer need to buy by using XS?
They've not moved. They don't exist when people use ESXi, KVM or XS. It is an entire range of confusion that is unique and exclusive to Hyper-V. No moving, but gone away entirely.
-
@scottalanmiller said in Why is Hyper-V More Confusing:
@Breffni-Potter said in Why is Hyper-V More Confusing:
@scottalanmiller said in Why is Hyper-V More Confusing:
@Breffni-Potter said in Why is Hyper-V More Confusing:
I don't see how replacing the underlying FREE hypervisor fixes Microsoft licensing nightmares.
Because an entire category of those nightmares are exclusive to confusion around Hyper-V. Remove Hyper-V and that entire range of issues simply stops existing.
But you've just moved those issues into XS?
What licenses are needed for the core hypervisor and what licenses do you no longer need to buy by using XS?
They've not moved. They don't exist when people use ESXi, KVM or XS. It is an entire range of confusion that is unique and exclusive to Hyper-V. No moving, but gone away entirely.
But what is confusing? Help me understand.
We start with a free, no license required, hypervisor. Oh you want to install Windows VMs? That's fine but here's the Microsoft rulebook on licensing.
You want to install Linux VMs? Go for it!
-
@Breffni-Potter said in Why is Hyper-V More Confusing:
@scottalanmiller said in Why is Hyper-V More Confusing:
@Breffni-Potter said in Why is Hyper-V More Confusing:
@scottalanmiller said in Why is Hyper-V More Confusing:
@Breffni-Potter said in Why is Hyper-V More Confusing:
I don't see how replacing the underlying FREE hypervisor fixes Microsoft licensing nightmares.
Because an entire category of those nightmares are exclusive to confusion around Hyper-V. Remove Hyper-V and that entire range of issues simply stops existing.
But you've just moved those issues into XS?
What licenses are needed for the core hypervisor and what licenses do you no longer need to buy by using XS?
They've not moved. They don't exist when people use ESXi, KVM or XS. It is an entire range of confusion that is unique and exclusive to Hyper-V. No moving, but gone away entirely.
But what is confusing? Help me understand.
We start with a free, no license required, hypervisor. Oh you want to install Windows VMs? That's fine but here's the Microsoft rulebook on licensing.
You want to install Linux VMs? Go for it!
Yes, THAT is too confusing. I'm unclear how to make this more clear. You are asking people to go learn something that they are very, VERY confused about. I mean REALLY confused. And your answer is "go stop being confused?" It doesn't work that way.
Hyper-V confuses people in a way that nothing else does. Why are they so confused, I don't know, but they are, consistently and always have been. That Hyper-V is simple to you is irrelevant. That they could go teach themselves what they need to know is irrelevant. The fact is... people are confused and don't go research things (or know what to research or know that they are confused.) And this confusion is totally unique to Hyper-V in this arena.
People can't even figure out that Hyper-V is a hypervisor, that it is free, that Hyper-V doesn't interact with the licenses on top, etc. So your "starting point" is after things are already fixed. People are so confused that they can't even get to your starting point without more effort than needed to install XS.
I think are making my point that you can't be objective... because it's not confusing to you (Or me and shouldn't be to anyone) you are failing to understand that in the real world, actual Windows admins are really, really unable to figure Hyper-V out. They are totally lost (at least in nearly all cases over the years that I've seen.. and it is a huge majority to the point that this confusion is a common topic of discussion and widely recognized and why I even have an article about it that people still can't understand!)
-
Let's put it another way, reading your responses, the average Hyper-V deployer would likely be confused as to what you are even talking about. Because they are sure that Hyper-V is not free, that it affects other licenses and that you can't "just install it" because it goes on top of Windows
-
I think the root of all the confusion with Hyper-V is that it is an MS Server product that doesnt cost money.
Everybody skips the EULA, so MS should just put a big vb message box with blinking bright lights that says "Hyper-V Server is free, if you put windows servers on it you must pay for those, but never for Hyper-V Server". Make people hit that button twice, then say an oath to Cortana, "I know that hyper-v server is free, if i put Windows vms on it i must pay for those" Only then would it install. -
I think the real confusion lies in running Hyper-V as a role on Windows server.
So, that SEEMS like you are then running 3 servers (1 more than allowed) but really aren't, as doing that create a VM of sorts to do the management.
Also, it's confusing that you can't use that server with the Hyper-V role for anything else. Can't server files. Can't run backups. Etc., etc..
-
@BRRABill said in Why is Hyper-V More Confusing:
I think the real confusion lies in running Hyper-V as a role on Windows server.
So, that SEEMS like you are then running 3 servers (1 more than allowed) but really aren't, as doing that create a VM of sorts to do the management.
Also, it's confusing that you can't use that server with the Hyper-V role for anything else. Can't server files. Can't run backups. Etc., etc..
Correct. 100% of the confusion around hyper-v is always people installing Server 2012 R2 + Hyper-V role (and usually other roles) instead of just Hyper-V Server 2012 R2
-
@momurda said in Why is Hyper-V More Confusing:
I think the root of all the confusion with Hyper-V is that it is an MS Server product that doesnt cost money.
Everybody skips the EULA, so MS should just put a big vb message box with blinking bright lights that says "Hyper-V Server is free, if you put windows servers on it you must pay for those, but never for Hyper-V Server". Make people hit that button twice, then say an oath to Cortana, "I know that hyper-v server is free, if i put Windows vms on it i must pay for those" Only then would it install.That would be nice. But it would still confuse the people discussing it and making the decisions but that haven't gotten around to deploying it yet
-
@JaredBusch said in Why is Hyper-V More Confusing:
@BRRABill said in Why is Hyper-V More Confusing:
I think the real confusion lies in running Hyper-V as a role on Windows server.
So, that SEEMS like you are then running 3 servers (1 more than allowed) but really aren't, as doing that create a VM of sorts to do the management.
Also, it's confusing that you can't use that server with the Hyper-V role for anything else. Can't server files. Can't run backups. Etc., etc..
Correct. 100% of the confusion around hyper-v is always people installing Server 2012 R2 + Hyper-V role (and usually other roles) instead of just Hyper-V Server 2012 R2
Definitely. If that didn't exist and/or MS made it clear what was happening, I think it would nearly all clear up. But that one things sprawls into all kinds of other confusion.
-
That they call the Dom0 the "physical" install makes things much worse, too.
-
Everyone who deploys software has to make sure he understands licensing. There is absolutely no difference in Microsoft Hyper-V Server, XS or VMware ESXi free:
- The hypervisor is free, period. No server license, no Cal.
- Run a billion Linux-VMs on it. Perfectly fine. No costs involved.
-Run Netware on it and you have to pay for the license for Netware. Simple as that and the same for Windows. - In case of Windows and possibly other OSes, you have to keep an eye on the "move license" rule. This is more important today because of (live) migration of VMs between hosts. Before virtualization, the license was often used for more than 6 months on a single machine. I know quite a few people in IT who never heard about this restriction, not even today. But it is there.
I have to admit that Microsoft forgot to put a big shiny and blinking website online where they say: Hey, it's free! But to be honest, I rarely find what I am looking for on Microsofts website expect when I use Google.
From a technical point of view, well, there are many threads here at ML with people having a hard time installing or upgrading XS. The same may happen with Hyper-V and to be honest again, getting WinRM running can be a bit tricky for beginners.
But changing the technical platform to XS or any other (free) Hypervisor doesn't solve the licensing problem at all.
-
@thwr said in Why is Hyper-V More Confusing:
I have to admit that Microsoft forgot to put a big shiny and blinking website online where they say: Hey, it's free! But to be honest, I rarely find what I am looking for on Microsofts website expect when I use Google.
They didn't. From day one they've gone over and above getting the message out that it's free and not tied to any licensing anywhere. But even they couldn't convince people.
-
@thwr said in Why is Hyper-V More Confusing:
From a technical point of view, well, there are many threads here at ML with people having a hard time installing or upgrading XS.
But none where they are doing it normally. If you follow the normal, expected, "not trying to push it or reinvent the wheel" procedure, it's super simple. That means no SD card, no software RAID (they specifically hide this), no whatever. Just take a stock enterprise server like a DL380 or an R720 configured with normal, integrated RAID, pop in the installation DVD and go... it's dead simple as AFAIK not one person has had any issues with it. Our interns have done quite a few installs, no issues with the stock installation procedures across several versions.
-
@thwr said in Why is Hyper-V More Confusing:
But changing the technical platform to XS or any other (free) Hypervisor doesn't solve the licensing problem at all.
Except it does, because the biggest problem is Hyper-V licensing. So changing it does resolve that one. Even though there is no licensing for it, the fact that people think that there is, refuse to believe that there is not, makes it less confusing to use something else. There is no getting around that. It's not Hyper-V's fault, it's not MS' fault, it just is what it is... some sad industry myth that has taken on a life of its own.
-
@thwr said in Why is Hyper-V More Confusing:
Everyone who deploys software has to make sure he understands licensing.
Should, but surprisingly few actually do. They might learn enough to know that they are compliant, but learning it well enough to apply that knowledge to decision making is surprisingly rare.
-
@scottalanmiller said in Why is Hyper-V More Confusing:
@thwr said in Why is Hyper-V More Confusing:
From a technical point of view, well, there are many threads here at ML with people having a hard time installing or upgrading XS.
But none where they are doing it normally. If you follow the normal, expected, "not trying to push it or reinvent the wheel" procedure, it's super simple. That means no SD card, no software RAID (they specifically hide this), no whatever. Just take a stock enterprise server like a DL380 or an R720 configured with normal, integrated RAID, pop in the installation DVD and go... it's dead simple as AFAIK not one person has had any issues with it. Our interns have done quite a few installs, no issues with the stock installation procedures across several versions.
Same with Hyper-V, so that point may be on par but doesn't make things simpler at all. Or do I miss something?
-
@scottalanmiller said in Why is Hyper-V More Confusing:
@thwr said in Why is Hyper-V More Confusing:
But changing the technical platform to XS or any other (free) Hypervisor doesn't solve the licensing problem at all.
Except it does, because the biggest problem is Hyper-V licensing. So changing it does resolve that one. Even though there is no licensing for it, the fact that people think that there is, refuse to believe that there is not, makes it less confusing to use something else. There is no getting around that. It's not Hyper-V's fault, it's not MS' fault, it just is what it is... some sad industry myth that has taken on a life of its own.
This can also been seen the other way around: "Hey, I'm using a non MS Type-1 Hypervisor, I probably don't need any licenses for my Windows guests now! Awesome!"
-
@thwr said in Why is Hyper-V More Confusing:
@scottalanmiller said in Why is Hyper-V More Confusing:
@thwr said in Why is Hyper-V More Confusing:
From a technical point of view, well, there are many threads here at ML with people having a hard time installing or upgrading XS.
But none where they are doing it normally. If you follow the normal, expected, "not trying to push it or reinvent the wheel" procedure, it's super simple. That means no SD card, no software RAID (they specifically hide this), no whatever. Just take a stock enterprise server like a DL380 or an R720 configured with normal, integrated RAID, pop in the installation DVD and go... it's dead simple as AFAIK not one person has had any issues with it. Our interns have done quite a few installs, no issues with the stock installation procedures across several versions.
Same with Hyper-V, so that point may be on par but doesn't make things simpler at all. Or do I miss something?
No, Hyper-V is not as simple. It's a good product, I'm not knocking it in ANY way. But it has a few points of complexity that whether its fault or the community's fault, make it harder. Same issues I listed above...
- It does not discourage software RAID but, in fact, through the community promotes it - and on a software RAID system that is poorly understood, has a terrible track record and is far too complex for the audience we are discussing. It is like FreeNAS and ZFS in this way that people are now starting to get confused as to if standard servers even work or if hardware RAID hards have to be pulled out or whatever. XenServer follows VMware's path here and "forces" newbies to do things a sensible way that is simple and understood. But unlike VMware still allows for experts to get tried and true enterprise software RAID if they so desire.
- It has the very, VERY confusing option to install via the "role" methodology. XS does not. There is no simple way to install XS encumbering it with things that should not be in the Dom0 or with licensing problems. Hyper-V doesn't just make this easy, it makes it the most obvious way to install.
- The licensing problem. For whatever reason, people can't figure out the licensing.
You can write off point three, there is value to ignoring it. But either point one or two on their own is more than enough to make Hyper-V rather a bit more complex for a newbie to use than XenServer. It simply requires you to know too much, understand too many things and not listen to all of the hype than can exist to be as simple as XS.
XS has one known point of complexity on a stock install... you have to know to choose thin provisioning up front. It REALLY sucks that they left that decision there, but it's very easy to address and doesn't cause the same level of issues and only exists for local installs.
-
@thwr said in Why is Hyper-V More Confusing:
This can also been seen the other way around: "Hey, I'm using a non MS Type-1 Hypervisor, I probably don't need any licenses for my Windows guests now! Awesome!"
Could be except for two simple facts...
- That doesn't happen, ever. It just doesn't so this isn't applicable.
- Any risk of that happening would also carry over to Hyper-V so this isn't a unique risk, it's one that we would expect to be equal or worse for Hyper-V.
So I don't buy this one. If it did, we'd have this issue on VMware 100 times a day. And yet, I'm not aware of a single example of it ever happening on any platform while the Hyper-V issue is weekly or possibly daily within a much smaller subset of the same pool of IT pros.
