Hypervisor, hypervisor - who's got the best hypervisor?
-
@coliver said:
You have a lot of Windows, it may be easier to manage if you maintain the same stack. Not saying XenServer is hard or anything, I actually find it easier, but Hyper-V is very capable and you already have the Windows Infrastructure in place to support it.
Hyper-V is the hardest to use regardless of stack, IMHO. Not sure when it would be chosen based on ease of use. If you are an all Windows shop and wanted ease of use, I think XenServer still wins.
-
@art_of_shred said:
What's the issue with VMware? Cost? Or something else?
Cost and lack of features. Just doesn't stack up to the other three all of which are free and loaded with features lacking in any potentially affordable Vmware license.
-
@art_of_shred said:
What's the issue with VMware? Cost? Or something else?
Yep - only cost. There is on point in paying for a hypervisor when it brings nothing else to the table in my situation.
-
@scottalanmiller said:
@coliver said:
You have a lot of Windows, it may be easier to manage if you maintain the same stack. Not saying XenServer is hard or anything, I actually find it easier, but Hyper-V is very capable and you already have the Windows Infrastructure in place to support it.
Hyper-V is the hardest to use regardless of stack, IMHO. Not sure when it would be chosen based on ease of use. If you are an all Windows shop and wanted ease of use, I think XenServer still wins.
Hyper-V is hard to use? News to me.
-
From a performance standpoint, KVM is the king here for an all Windows workload. XenServer is the winner for ease of use and community support. Hyper-V is good for some edge features and middle of the road windows performance.
Performance in the SMB is misleading as it just doesn't matter in the small numbers that these things differ.
-
@JaredBusch said:
@scottalanmiller said:
@coliver said:
You have a lot of Windows, it may be easier to manage if you maintain the same stack. Not saying XenServer is hard or anything, I actually find it easier, but Hyper-V is very capable and you already have the Windows Infrastructure in place to support it.
Hyper-V is the hardest to use regardless of stack, IMHO. Not sure when it would be chosen based on ease of use. If you are an all Windows shop and wanted ease of use, I think XenServer still wins.
Hyper-V is hard to use? News to me.
Only in comparison.
-
@Dashrender I would use Hyper-V for the 3rd party tools. XenServer if I had all the time in the world to do everything myself.
-
@JaredBusch said:
@Dashrender I would use Hyper-V for the 3rd party tools. XenServer if I had all the time in the world to do everything myself.
What kinds of things do you need to do yourself in XenServer? it has a great third party tooling ecosystem too. Just most of it is free rather than much of it being pay only.
-
Before I answer, what features are you currently lacking from VMware? Is there something that you're needing that you just can't get with VMware or is this cost justifiable?
-
@DustinB3403 said:
Before I answer, what features are you currently lacking from VMware? Is there something that you're needing that you just can't get with VMware or is this cost justifiable?
It generally boils down to cost justification.
-
@scottalanmiller said:
@coliver said:
You have a lot of Windows, it may be easier to manage if you maintain the same stack. Not saying XenServer is hard or anything, I actually find it easier, but Hyper-V is very capable and you already have the Windows Infrastructure in place to support it.
Hyper-V is the hardest to use regardless of stack, IMHO. Not sure when it would be chosen based on ease of use. If you are an all Windows shop and wanted ease of use, I think XenServer still wins.
I'm not sure about that. An all Windows shop and ease of use may go to Hyper-V. I haven't managed XenServer in production so I'm not sure but Hyper-V is super simple, almost as simple as XenServer, it does also have API hooks for software like Unitrends and Veeam if @Dashrender uses either of those applications.
-
@DustinB3403 said:
Before I answer, what features are you currently lacking from VMware? Is there something that you're needing that you just can't get with VMware or is this cost justifiable?
Is what cost justifiable?
If you're talking about the conversion cost (mostly in my time), then yes I'd say it's justifiable so I get away from bad investments, i.e. paying for updates to ESXi Essentials. (damn I forget the phrase that Scott always uses).
Beyond that - no I am lacking no features/functions that I want.
-
@dafyre but it doesn't cost to keep what he has. Assuming he drops all support from VMWare.
It does cost to tear down and rebuild the infrastructure though.
I'm a huge fan of Xen, so I would happily say, Yeah Xen absolutely, but was looking for a justification before jumping on it
-
@dafyre said:
@DustinB3403 said:
Before I answer, what features are you currently lacking from VMware? Is there something that you're needing that you just can't get with VMware or is this cost justifiable?
It generally boils down to cost justification.
Especially since essentially all features are available in Vmware... for a price. So even if you state that it is features, it would still be cost because with enough money you could have that feature with rare exception.
-
@Dashrender said:
@DustinB3403 said:
Before I answer, what features are you currently lacking from VMware? Is there something that you're needing that you just can't get with VMware or is this cost justifiable?
Is what cost justifiable?
If you're talking about the conversion cost (mostly in my time), then yes I'd say it's justifiable so I get away from bad investments, i.e. paying for updates to ESXi Essentials. (damn I forget the phrase that Scott always uses).
Beyond that - no I am lacking no features/functions that I want.
You're already invested in ESXi that's a sunk cost so you have to weigh the cost of migration and support of your new infrastructure against the ongoing maintenance and support licenses from VMWare. From what I've heard from people who have done the migration it saves money in the long term.
-
@Dashrender said:
@DustinB3403 said:
Before I answer, what features are you currently lacking from VMware? Is there something that you're needing that you just can't get with VMware or is this cost justifiable?
Is what cost justifiable?
If you're talking about the conversion cost (mostly in my time), then yes I'd say it's justifiable so I get away from bad investments, i.e. paying for updates to ESXi Essentials. (damn I forget the phrase that Scott always uses).
Beyond that - no I am lacking no features/functions that I want.
So yeah, paying for updates seems like it could be a huge rip off. If your time is worth the conversion I'd recommend Xen. (see all of my other topics)
Ton's a great, really very good performing options for things you're living without now.
Plus updates are free.
-
@coliver said:
@scottalanmiller said:
@coliver said:
You have a lot of Windows, it may be easier to manage if you maintain the same stack. Not saying XenServer is hard or anything, I actually find it easier, but Hyper-V is very capable and you already have the Windows Infrastructure in place to support it.
Hyper-V is the hardest to use regardless of stack, IMHO. Not sure when it would be chosen based on ease of use. If you are an all Windows shop and wanted ease of use, I think XenServer still wins.
I'm not sure about that. An all Windows shop and ease of use may go to Hyper-V. I haven't managed XenServer in production so I'm not sure but Hyper-V is super simple, almost as simple as XenServer, it does also have API hooks for software like Unitrends and Veeam if @Dashrender uses either of those applications.
Just the clarification around licensing alone and the misinformation in communities about Hyper-V alone is a lot more work. getting help is hard because there is so much confusion around it. And the management tools are not unlimited and free like on XS. That alone is more work that XS is total. It's not that it si hard, but how does using Windows make it any easier? That's where I'm always lost. There isn't anything about having used Windows that makes Hyper-V easier or harder to use. I've used it, it is generic as far as interface.
-
@coliver said:
@scottalanmiller said:
@coliver said:
You have a lot of Windows, it may be easier to manage if you maintain the same stack. Not saying XenServer is hard or anything, I actually find it easier, but Hyper-V is very capable and you already have the Windows Infrastructure in place to support it.
Hyper-V is the hardest to use regardless of stack, IMHO. Not sure when it would be chosen based on ease of use. If you are an all Windows shop and wanted ease of use, I think XenServer still wins.
I'm not sure about that. An all Windows shop and ease of use may go to Hyper-V. I haven't managed XenServer in production so I'm not sure but Hyper-V is super simple, almost as simple as XenServer, it does also have API hooks for software like Unitrends and Veeam if @Dashrender uses either of those applications.
XenServer has API for Unitrends too.
-
@coliver said:
@Dashrender said:
@DustinB3403 said:
Before I answer, what features are you currently lacking from VMware? Is there something that you're needing that you just can't get with VMware or is this cost justifiable?
Is what cost justifiable?
If you're talking about the conversion cost (mostly in my time), then yes I'd say it's justifiable so I get away from bad investments, i.e. paying for updates to ESXi Essentials. (damn I forget the phrase that Scott always uses).
Beyond that - no I am lacking no features/functions that I want.
You're already invested in ESXi that's a sunk cost so you have to weigh the cost of migration and support of your new infrastructure against the ongoing maintenance and support licenses from VMWare. From what I've heard from people who have done the migration it saves money in the long term.
Which saves them money in the long term? Migrating or not migrating?
-
@Dashrender Migrating saves them money in the long term, because they don't have to pay for updates. (or anything else if they chose not too)
