XenServer vs ESXi
-
I can only assumed that they sold us the licensing for it, as they are pretty good with keeping microsoft at bay (I've never heard of any licensing issues with regards to that)
But the implementation is just ass backwards. Export the DC02 functions if you must (build a new VM really) and perform a clean install is how it should've been done.
-
@Carnival-Boy said:
I'm not following you, I'm afraid. I assume the OP has the correct licences? I thought that when you install HyperV it kind of inserts the hypervisor underneath the existing Windows installation, so you end with a hypervisor and the existing Windows install running as a VM? So the physical DC becomes a virtual DC? Is that not how it works?
Well yes and no. You are totally correct at the technology level. You install HyperV (role) and it inserts HyperV underneath the running OS as a shim (it actually reboots before this takes effect, for obvious reasons.) So it reboots to running HyperV on the bare metal and the previously bare metal OS of Windows because a VM known as the "host" VM or Microsoft confusing calls it the Physical VM (um what?!?)
You can two licenses of Windows with each Windows 2012 Standard install. Two VMs on the same box, that is, plus one "physical" license for the host VM. The Host VM only qualifies for this license if it runs nothing except the HyperV management, any use of it for anything like DC, IIS, SQL Server, File Server, Spiceworks or any other application or role violates the licenses.
So you have two choices when using it this way. Either you move the services off of the Host VM and put them on one of the two Guest VMs. Or you consume one of your Guest VM licenses to make the running of services on the Host VM allowed.
At the end of the day, you get no freebies from using HyperV compared to other hypervisors but you get no penalties either. Because it needs Windows to manage it, they give you a special management only license for that one use case.
So there is a way to do what you are describing but it doesn't work out super well for you (but works) but generally people mess it up and end up not being properly licensed and overusing what they have.
-
Trust me, I really hate the MS terminology on this stuff because it is designed to be confusing in a weird way with a weird hope that it would make the system "easy" for non-technical people. Sadly, you can't do that with virtualization and they made it so confusing that even IT Pros can't navigate the licensing.
-
@DustinB3403 said:
I can only assumed that they sold us the licensing for it, as they are pretty good with keeping microsoft at bay (I've never heard of any licensing issues with regards to that)
Nothing like double selling licensing.... be a little lazy, do less work, make extra money off of the customer for no effort. Slick.
-
That they are the ones selling you the licenses explains the behaviour. I'm assuming that they are the ones selling the ESXi too. Which explains pretty much all of the behaviour.
-
Don't know if anything in here helps, but it might:
http://mangolassi.it/topic/5272/somethings-you-need-to-know-about-hyperv
-
So back to the case at hand:
XenServer has many advantages...
- You already know it.
- It is incredibly easy to use.
- It is very performant and this has been shown.
- The devil that you know.
- Zero cost for everything, totally zero.
- Full Paravirtualization Option for Linux workloads.
- Updates are also free.
- No overhead cost for license management.
- No salesman providing guidance.
- Backups are possible for free.
- Far greater feature set than any possible VMware option.
- HA is free
- vMotion is free
- Storage vMotion is free
- Many more free features
- No scale limitations (within reason)
- Local support available
- Minimal technical debt incurred.
-
@Carnival-Boy if you are using Windows Server Datacenter licensing then you are completely free to utilize the physical VM for anything that you want as you have licensed the entire machine. There is no overuse possible in that case. But in the case where you have the DC license, there is no incentive to trying to use the Physical / Host VM for anything extra since you can always make another VM for whatever workload you were thinking of running there.
-
@DustinB3403 said:
The trouble as far as I can tell with the Hyper-V setup is that our MSP sold it just to sell it, rather than "Oh hey spend X and build a proper Hypervisor, we'll just use your secondary DC to run these machines"
Which "OK" it works but one of these VM's runs a CPU intensive process, and in only able to use 4CPU's because of the limitations of the host hardware.
If I moved this to "my" (and I use my liberally) XenServer I could allocate 12 cores to it, and 32GB of memory (if we bought more to add into the host) and the team that uses it would never have a complaint.
Its the poor proposals after another that are getting to me. It's just not my place to start looking for another MSP... even though I've considered it.
It is your place to point out poor decision making and poor proposals of the MSP though. If this were happening to my company I would bring this up to my boss (and his boss) almost immediately. Especially if they are going to spend money on a product that has no intrinsic benefit over what you are currently using. Especially since you already have that solution running and proven in house.
-
@DustinB3403 said:
Nope. . . Hyper-V was installed directly into the existing DC02, and VM's setup while the system was functioning.
Talk about red flags... not only does this VAR/MSP not understand how Hyper-V, a product they had proposed, works but they don't understand the licensing limitation/expectation of it...
-
@scottalanmiller said:
@DustinB3403 said:
Its the poor proposals after another that are getting to me. It's just not my place to start looking for another MSP... even though I've considered it.
Here is the big question... is it your job to care about the company or not to care? It's an honest question. Lots of companies would say that it is not your job to be involved. Others would be furious to find out that you knew an MSP was screwing them over and that a manager was letting it happen and not even pushing back for reasonable solutions and you didn't go up the chain to let someone know. Figuring out what your role in is key.
Boy this is something I feel completely undefined on.
-
@Dashrender said:
Boy this is something I feel completely undefined on.
It sounds pretty obvious, right? But when you actually stop and ask the question, often it isn't really clear if you are supposed to care or not! It's one of those places where everyone thinks that they would have a clear answer until really pushed on it. And in reality, lots of companies don't want you to care. It's actually quite common.
-
@coliver said:
@DustinB3403 said:
Nope. . . Hyper-V was installed directly into the existing DC02, and VM's setup while the system was functioning.
Talk about red flags... not only does this VAR/MSP not understand how Hyper-V, a product they had proposed, works but they don't understand the licensing limitation/expectation of it...
Or worse, they DO understand the licensing! Which is worse, being clueless on the basics or being aware of what they were doing and still doing it?
-
@coliver said:
It is your place to point out poor decision making and poor proposals of the MSP though.
That's the question. Is it?
-
@scottalanmiller said:
So back to the case at hand:
XenServer has many advantages...
- You already know it.
- It is incredibly easy to use.
- It is very performant and this has been shown.
- The devil that you know.
- Zero cost for everything, totally zero.
- Full Paravirtualization Option for Linux workloads.
- Updates are also free.
- No overhead cost for license management.
- No salesman providing guidance.
- Backups are possible for free.
- Far greater feature set than any possible VMware option.
- HA is free
- vMotion is free
- Storage vMotion is free
- Many more free features
- No scale limitations (within reason)
- Local support available
- Minimal technical debt incurred.
This is a great list. Covers pretty much all the main bases.
-
I care... I'll always care... Especially if I like my job... I was at my last job about 3 years too long...but I hung around because I cared... I'd bring this up to my boss in a heart beat... With a big ? hanging over my head, like "Why?" ... and he can either tell me the reason and give me a chance to shoot holes in his reasons, or tell me not to worry about it... At which point, I still care about it, but my duty is done.
-
@dafyre said:
I care... I'll always care... Especially if I like my job... I was at my last job about 3 years too long...but I hung around because I cared... I'd bring this up to my boss in a heart beat... With a big ? hanging over my head, like "Why?" ... and he can either tell me the reason and give me a chance to shoot holes in his reasons, or tell me not to worry about it... At which point, I still care about it, but my duty is done.
I suffer the same problem! I do care.
-
@scottalanmiller said:
@coliver said:
@DustinB3403 said:
Nope. . . Hyper-V was installed directly into the existing DC02, and VM's setup while the system was functioning.
Talk about red flags... not only does this VAR/MSP not understand how Hyper-V, a product they had proposed, works but they don't understand the licensing limitation/expectation of it...
Or worse, they DO understand the licensing! Which is worse, being clueless on the basics or being aware of what they were doing and still doing it?
The former gives them the benefit of the doubt the latter seems almost malicious although this is another case of, "Does it matter?" While the latter is worse then the former they both equally demonstrate how inadequate this VAR is.
-
@scottalanmiller said:
So there is a way to do what you are describing but it doesn't work out super well for you (but works) but generally people mess it up and end up not being properly licensed and overusing what they have.
I think I've got you. So the I'm guessing the correct approach would be something like:
Demote the DC
Remove the DC from the domain
Do a fresh, clean install of Windows on the host
Install HyperV
Install a fresh, clean VM of Windows and setup as new DCWhich, IIRC, is exactly what we did with ESXi, except that we installed the hypervisor directly and then install VCenter appliance to manage it.
-
@Carnival-Boy said:
@scottalanmiller said:
So there is a way to do what you are describing but it doesn't work out super well for you (but works) but generally people mess it up and end up not being properly licensed and overusing what they have.
I think I've got you. So the I'm guessing the correct approach would be something like:
Demote the DC
Remove the DC from the domain
Install HyperV Server 2012R2
Install a fresh, clean VM of Windows and setup as new DCWhich, IIRC, is exactly what we did with ESXi, except that we installed the hypervisor directly and then install VCenter appliance to manage it.
You don't really need a full version of Windows Server for your hypervisor in this case... Hyper-V Server 2012R2 is exactly the same thing just with all the extras cut out of it.
