What would your recommendation be for a Type 1 Hypervisor - including backup and restoration options
-
@dyasny said in What would your recommendation be for a Type 1 Hypervisor - including backup and restoration options:
@DustinB3403 said in What would your recommendation be for a Type 1 Hypervisor - including backup and restoration options:
So the issue with "Windows on the hardware" is that is it creates licensing restrictions that make moving your VM's around difficult among other issues.
So Windows should never be on the hardware. Just install Hyper-V and create your VM's with your licensing.
The question here is about SMBs, where you don't always have a say in what they've got, you simply have to deal with the existing stuff, under a very tight budget. If you have the option to plan and do things right, then of course there's plenty of best practice out there to follow.
And for Hyper-V to be an option, you do need Windows on the hardware. There is no such thing as "baremetal hypervisor" - every hypervisor needs an OS to be able to work, even if it's a small stripped down OS like the Xen kernel.
The benefit of "added licensing" is universal, regardless of what hypervisor you use. With Server Standard X you always get the right to create 2 Virtual Machines. Always.
Last time I checked with an MS licensing specialist, that was the case for the DC edition, and even then MS weren't too happy to activate your machines unless you also got a site license, a VLK or a select-6 pack. For SMBs, even if you do technically have the option to activate windows servers on non-MS virtual hardware, the procedure of doing that will hurt.
My information is a bit dated though, they might have improved things since 2010-2012-ish.
If you have the option to actually do things right and you are able to activate your windows vms without problems, KVM is a great choice, especially since if you have to scale, you can deploy oVirt
all of this is basically wrong.
-
@DustinB3403 said in What would your recommendation be for a Type 1 Hypervisor - including backup and restoration options:
What does this have to do with doing things in a correct fashion if you're starting new? FFS
Are you always starting from scratch?
No you don't. FFS Hyper-V is 100% free. Just login and download it. https://www.microsoft.com/en-gb/evalcenter/evaluate-hyper-v-server-2016
FFS, at least take care to post a working link.
Server Standard Licensing has at least for as long as I can remember given you the right to install twice on the same hardware with-which the license is activated. Datacenter isn't Standard.
Your information is just wrong.
Then that is something I'll be giving my MS contact shit for.
-
@dyasny said in What would your recommendation be for a Type 1 Hypervisor - including backup and restoration options:
@DustinB3403 said in What would your recommendation be for a Type 1 Hypervisor - including backup and restoration options:
What does this have to do with doing things in a correct fashion if you're starting new? FFS
Are you always starting from scratch?
No you don't. FFS Hyper-V is 100% free. Just login and download it. https://www.microsoft.com/en-gb/evalcenter/evaluate-hyper-v-server-2016
FFS, at least take care to post a working link.
Server Standard Licensing has at least for as long as I can remember given you the right to install twice on the same hardware with-which the license is activated. Datacenter isn't Standard.
Your information is just wrong.
Then that is something I'll be giving my MS contact shit for.
https://www.microsoft.com/en-us/evalcenter/evaluate-hyper-v-server-2016
-
@dyasny said in What would your recommendation be for a Type 1 Hypervisor - including backup and restoration options:
The question here is about SMBs, where you don't always have a say in what they've got, you simply have to deal with the existing stuff, under a very tight budget. If you have the option to plan and do things right, then of course there's plenty of best practice out there to follow.
I think that is more greenfield vs. brownfield. Even in the SMB you can normally fix things when in charge, and whoever is in charge is who the guidance is aimed at.
SMBs had to make the decisions incorrectly in the first place. We'd have the same issue in the enterprise if we made the same assumptions - that someone else is making the decisions and made them and we are just supporting what they put in place. Which is true everywhere. But the implied point of the thread is what to do when you are in the position of making the decisions, if that makes sense.
-
@dyasny said in What would your recommendation be for a Type 1 Hypervisor - including backup and restoration options:
@DustinB3403 said in What would your recommendation be for a Type 1 Hypervisor - including backup and restoration options:
What does this have to do with doing things in a correct fashion if you're starting new? FFS
Are you always starting from scratch?
The conversation is about starting from scratch.
No you don't. FFS Hyper-V is 100% free. Just login and download it. https://www.microsoft.com/en-gb/evalcenter/evaluate-hyper-v-server-2016
FFS, at least take care to post a working link.
Works just fine for me
Server Standard Licensing has at least for as long as I can remember given you the right to install twice on the same hardware with-which the license is activated. Datacenter isn't Standard.
Your information is just wrong.
Then that is something I'll be giving my MS contact shit for.
Rarely do the sales f***s know the difference and oversell you because they can make more money.
-
@scottalanmiller I've had the misfortune of doing SMB work for quite a few years, and it's always been "just fix this now" and "we've no budget for that, we're an accounting firm and not an IT shop". So when I see SMB mentioned, I go into power saving mode
-
@dyasny said in What would your recommendation be for a Type 1 Hypervisor - including backup and restoration options:
And for Hyper-V to be an option, you do need Windows on the hardware. There is no such thing as "baremetal hypervisor" - every hypervisor needs an OS to be able to work, even if it's a small stripped down OS like the Xen kernel.
This is incorrect. Type 1 hypervisors never (by definition) have an OS under them, that's a Type 2 (VirtualBox, for example.) The Xen kernel is a hypervisor kernel, not an OS in any way.
Hyper-V needs Windows in some fashion to work, but it is not a product called Windows and is absolutely not on the bare metal. The Hyper-V hypervisor is what sits on the bare metal, always. There is no way to have Hyper-V on top of any OS, not even Windows.
Xen, KVM, ESXi, Hyper-V... they are all bare metal hypervisors, all of them have their hypervisor kernel touching the bare metal. Xen and Hyper-V use a special VM with an OS in it to handle some functions, but that's in a VM, not on the bare metal.
-
@dyasny said in What would your recommendation be for a Type 1 Hypervisor - including backup and restoration options:
@scottalanmiller I've had the misfortune of doing SMB work for quite a few years, and it's always been "just fix this now" and "we've no budget for that, we're an accounting firm and not an IT shop". So when I see SMB mentioned, I go into power saving mode
That's generally true, but you are looking at it from a partial perspective when you look at it that way. The question and/or advice would have been for the person designing the environment. Not for someone "just fixing something." At some point that SMB had all of the same opportunity and need to do things well, and therefore needed the advice and will need it again sometime.
-
@dyasny said in What would your recommendation be for a Type 1 Hypervisor - including backup and restoration options:
@scottalanmiller I've had the misfortune of doing SMB work for quite a few years, and it's always been "just fix this now" and "we've no budget for that, we're an accounting firm and not an IT shop". So when I see SMB mentioned, I go into power saving mode
both hyper-v and KVM fit the no budget budget.
-
@dyasny said in What would your recommendation be for a Type 1 Hypervisor - including backup and restoration options:
Last time I checked with an MS licensing specialist, that was the case for the DC edition, and even then MS weren't too happy to activate your machines unless you also got a site license, a VLK or a select-6 pack. For SMBs, even if you do technically have the option to activate windows servers on non-MS virtual hardware, the procedure of doing that will hurt.
My information is a bit dated though, they might have improved things since 2010-2012-ish.
If you have the option to actually do things right and you are able to activate your windows vms without problems, KVM is a great choice, especially since if you have to scale, you can deploy oVirt
It's dead simple and universal now. Everyone with Windows does this, essentially. I've not seen a deployment not taking advantage of all the extra standard licenses in a decade. It's "just how Windows is", now. You get two VMs for every Standard license you buy, and that's how all capacity planning is done.
-
@Donahue said in What would your recommendation be for a Type 1 Hypervisor - including backup and restoration options:
@dyasny said in What would your recommendation be for a Type 1 Hypervisor - including backup and restoration options:
@scottalanmiller I've had the misfortune of doing SMB work for quite a few years, and it's always been "just fix this now" and "we've no budget for that, we're an accounting firm and not an IT shop". So when I see SMB mentioned, I go into power saving mode
both hyper-v and KVM fit the no budget budget.
And the Xen family, too.
-
@scottalanmiller Actually, what you say is both correct and incorrect. A hypervisor is simply the driver for the VT/SVM CPU extensions, nothing else. In that sense, it does work with the hardware directly, obviously. But it does not work in a vacuum - a driver is only part of a set of drivers of which a kernel consists. The kernel also contains other software like schedulers, and with a bit of utilities added, you get a barebones OS. It might be extremely stripped down, but it is still an OS.
Having said that, when people say "hypervisor" they mean a means of getting a VM to run, that usually means the drivers, a kernel to utilize the drivers, a set of utilities to manage the VM and emulate virtual hardware. So really, there is no "baremetal", unless you have a box that doesn't even boot up
-
@dyasny said in What would your recommendation be for a Type 1 Hypervisor - including backup and restoration options:
@scottalanmiller Actually, what you say is both correct and incorrect. A hypervisor is simply the driver for the VT/SVM CPU extensions, nothing else. In that sense, it does work with the hardware directly, obviously. But it does not work in a vacuum - a driver is only part of a set of drivers of which a kernel consists. The kernel also contains other software like schedulers, and with a bit of utilities added, you get a barebones OS. It might be extremely stripped down, but it is still an OS.
Not an OS. An OS has a definition, and true hypervisors don't meet it. It's like an OS, yes. But it's different. KVM/Linux is unique in that depending on configuration it can be either or both.
But remember, Linux isn't an OS, it's not enough on its own. It's only a kernel. It's a kernel meant for an OS, but that doesn't make it an OS.
But Xen, Hyper-V, and ESXi don't contain kernels even meant for an OS.
A hypervisor is never a driver. To be a hypervisor, you must be a kernel. If it is only a driver, it's not a hypervisor. Or not a type 1, at least.
A type 2 hypervisor has a driver, but must be more than a driver to be the hypervisor.
-
@dyasny said in What would your recommendation be for a Type 1 Hypervisor - including backup and restoration options:
Having said that, when people say "hypervisor" they mean a means of getting a VM to run, that usually means the drivers, a kernel to utilize the drivers, a set of utilities to manage the VM and emulate virtual hardware. So really, there is no "baremetal", unless you have a box that doesn't even boot up
Except that all of those things go on the bare metal in type 1 systems. Hence why they are called bare metal hypervisors. (Except the utilities portion.)
And keep in mind that bare metal virtualization exists even without the hardware pieces you mentioned. Some of us come from the virtualization world prior to that stuff existing. In the SMB world these days, those tend to be considered foregone conclusions, but in the bigger sense, they are not. Xen, for example, predates that stuff by quite a bit, as does ESX.
Most virtualization systems only provide an API on the bare metal, and put the management utilities for end users elsewhere. But that's not the hypervisor.
But the hypervisor... including the kernel, any drivers, and the hardware emulation sit on bare metal with all bare metal hypervisors.
-
@scottalanmiller said in What would your recommendation be for a Type 1 Hypervisor - including backup and restoration options:
Not an OS. An OS has a definition, and true hypervisors don't meet it. It's like an OS, yes. But it's different. KVM/Linux is unique in that depending on configuration it can be either or both.
But remember, Linux isn't an OS, it's not enough on its own. It's only a kernel. It's a kernel meant for an OS, but that doesn't make it an OS.
But Xen, Hyper-V, and ESXi don't contain kernels even meant for an OS.
That's semantics. A kernel and a set of tools to perform a function, comprise an OS, maybe not a generic universal OS that can do anything, but an OS nonetheless. An RTOS that guides a rocket is tiny and very narrow in it's use, but it's an OS nonetheless. Like I said - semantics.
A hypervisor is never a driver. To be a hypervisor, you must be a kernel. If it is only a driver, it's not a hypervisor. Or not a type 1, at least.
Actually, a hypervisor in it's cleanest form is exactly that - a driver made to address the extra CPU features that allow for proper virtualization instead of tricks with optimized emulation, like VMWare did before VT. But nobody uses that word in that sense, because if we did - the only actual hypervisor out there would be KVM, all others are a stack of driver plus emulators, plus hardware drivers, schedulers and userspace tools.
A type 2 hypervisor has a driver, but must be more than a driver to be the hypervisor.
Hypervisor types have been made moot by KVM's emergence 12 years ago.
-
@dyasny said in What would your recommendation be for a Type 1 Hypervisor - including backup and restoration options:
@scottalanmiller said in What would your recommendation be for a Type 1 Hypervisor - including backup and restoration options:
Not an OS. An OS has a definition, and true hypervisors don't meet it. It's like an OS, yes. But it's different. KVM/Linux is unique in that depending on configuration it can be either or both.
But remember, Linux isn't an OS, it's not enough on its own. It's only a kernel. It's a kernel meant for an OS, but that doesn't make it an OS.
But Xen, Hyper-V, and ESXi don't contain kernels even meant for an OS.
That's semantics. A kernel and a set of tools to perform a function, comprise an OS, maybe not a generic universal OS that can do anything, but an OS nonetheless. An RTOS that guides a rocket is tiny and very narrow in it's use, but it's an OS nonetheless. Like I said - semantics.
It's all semantics. Semantics is just another term for accuracy. A kernel plus tools for a function has never been the description of an OS. An OS has to be a specific general purpose platform for applications. If you narrow the use, it has to stop being an OS.
If we weren't worried about semantics, we'd just call it a "kitten" and that would be correct.
-
@scottalanmiller said in What would your recommendation be for a Type 1 Hypervisor - including backup and restoration options:
Except that all of those things go on the bare metal in type 1 systems. Hence why they are called bare metal hypervisors. (Except the utilities portion.)
Nothing is on bare metal. It is all software loaded into memory by a kernel loaded after POST. The drivers work with the "baremetal" directly, everything else works through a driver, or is emulated in software. Does the VNC console to a Xen VM work on baremetal?
And keep in mind that bare metal virtualization exists even without the hardware pieces you mentioned. Some of us come from the virtualization world prior to that stuff existing. In the SMB world these days, those tend to be considered foregone conclusions, but in the bigger sense, they are not. Xen, for example, predates that stuff by quite a bit, as does ESX.
The only real baremetal VMs were on mainframes (and I suppose there might be some exotic FPGA implementations), but we're not discussing those right now.
Most virtualization systems only provide an API on the bare metal, and put the management utilities for end users elsewhere. But that's not the hypervisor.
API on the baremetal. Really. Can you show me the chip that API is implemented in?
But the hypervisor... including the kernel, any drivers, and the hardware emulation sit on bare metal with all bare metal hypervisors.
the hypervisor is part of the kernel, like all other hardware drivers. It IS a driver, for the CPU extensions. Exactly what I've been saying. Only the kernel isn't on baremetal, it's software that gets loaded by the BIOS and is the lowest level talking to the hardware.
-
@dyasny said in What would your recommendation be for a Type 1 Hypervisor - including backup and restoration options:
Actually, a hypervisor in it's cleanest form is exactly that - a driver made to address the extra CPU features that allow for proper virtualization instead of tricks with optimized emulation, like VMWare did before VT. But nobody uses that word in that sense, because if we did - the only actual hypervisor out there would be KVM, all others are a stack of driver plus emulators, plus hardware drivers, schedulers and userspace tools.
Not at all. Hypervisors pre-date those features. It's redefining hypervisor after the fact that makes that seem plausible. But it's not. Hypervisors are not drivers, and hypervisors don't require CPU extensions. That's a very recent thing considering we've had hypervisors for many decades, but the extensions only for about fifteen years.
If you were in the virtualization and hypervisor world before that stuff existed, it would make it obvious how silly it is to say that hypervisors require something that is decades younger than they are.
-
@scottalanmiller said in What would your recommendation be for a Type 1 Hypervisor - including backup and restoration options:
It's all semantics. Semantics is just another term for accuracy. A kernel plus tools for a function has never been the description of an OS. An OS has to be a specific general purpose platform for applications. If you narrow the use, it has to stop being an OS.
That is extremely arguable. Actually, my wife, a VHDL/VLSI/FPGA developer, would laugh if she heard that
-
@dyasny said in What would your recommendation be for a Type 1 Hypervisor - including backup and restoration options:
API on the baremetal. Really. Can you show me the chip that API is implemented in?
Ah, I think the issue is that you don't know how bare metal is used in IT terms. Bare metal never means running on in the chip, it's the code that is run directly on the chip rather than being virtualized a layer up. If you were thinking that bare metal means in the chip's code itself, that would explain the misunderstanding of how hypervisors work.
That term does not mean that. There are things that run on the chip. And there are hypervisors that run in the hardware. Those are called hardware, not bare metal.
