5 hours 8 minutes
how does virtualization work? So if you're completely new to this technology,
it would help you to take a few minutes to become grounded in a few kind of basic concepts of virtual ization before diving in type of it. Not having a basic idea of hyper these operated operation, it can lead to a few kind of conceptual hurdles. If you kind of follow what I'm saying,
that can prevent kind of
the ability for you to implement and operated correctly. Eso we'll begin with like a familiar computer. So you guys all know what this is. Effectively, you start with the hardware. That's kind of the idea with it. This is made of kind of the motherboard, the CPU, the memory,
the hard drive on the monitor. You know, you've got all these physical equipment
on operating system is the very first layer that gets installed in terms of software. So this is the kind of the
the kind of the way that it talks to software. That's what the operating system allows it to do. The primary job of the operating system is to kind of get all that hardware and kind of corral it together. If you will on ensures that all the bits go where they need to go, and they're talking to what they need to talk to
get it working. It obviously is very simplistic, but this is a
fundamentals course. I don't know too much into it. Most people, I would hope, would understand a basic level very basically off how computes in general would operate. But part of its function is accepting input from devices such as the keyboard and mouse. Onda related Job is directing input, two
screens, printers and other devices. So when you tell the computer to do something,
you expect something to pop up on the screen. And that's kind of how it how it progresses,
whether you know it or no virtual ization is actually occurring in this diagram on your screen. Virtual ization. I say it with air quotes is really just another word for abstraction. So if any of you have ever heard of the hardware abstraction layer,
that's kind of along the lines of virtual ization, it's built in systems.
Abstraction is just a basic function of an operating system. You haven't got the time to learn how to send a binary command on dhe data to the CPU. In order to kind of make your printer producer report, you don't wanna have to code, so you just wanna click a button and then that does it for you. That's an abstraction. It's a virtual ization off
in a button that's effectively how it works. So the operating system presents to you an abstraction of the printer that you can send print jobs, too. That's the idea behind there, and the print job that you built was created inside another program
that provides an abstraction off the document. So there's virtual ization layers going on, even in an operating system
on many people, just you just don't see them. They just work. Like I said before, many people don't realize that they're using virtual ization on a daily basis.
Three icons and the mouse cursor, everything like that that you use on your screen. Those are abstractions. That's that's how virtualization works now. Ah, hyper visor takes this abstraction up. Another level s O. This is reflected in the
origin of the actual words. So in earlier times, what we now call an operating system
used to be called in the old days. If any of you are, they sold touch wood. I'm not quite that old yet, but I do know the systems. They used to be called supervisors now in common kind of
Western vernacular, if you will, the prefix hyper has come to mean above super,
so the term hyper visor was coined to indicate that a supervisor it's a supervisor over supervisor. It's a hyper visor. That's where the word hyper came from in terms of hyper V. So you're like Who polices the police? Who supervises the supervisors?
That's where it comes from.
On conceptually, it looks a little bit like this on the screen. If I just shift that to one side,
that's what you're looking at
in terms of a hyper visor. So we still have all the same obstructions that are going on. But now hyper V presents another layer between the operating system that you're used to,
and the hardware on this additional layer allows from multiple operating systems to run on the same hardware, and you can see on the screen there you've got. The management operating system would have been the original operating system before the virtual ization
it takes all the input, and then the hyper visor sits between the actual hardware and the software before the actual operating system touches the hardware. This is why it's classified as a type one. Hyper V. That's kind of how it works. It means that the management operating system
doesn't need to worry about all those virtual machines that you're running. If I've got four, of'em is running on my Windows client.
The operating system could just do its thing. You know, if it needs resource, is it? I'll ask for it. The hyper visor even controls the management operating system. That's why it's called a type one. There's no second layer. It's just one layer straight to the hardware. That's effectively what it's referring to in those kind of slights.
So, uh, hyper V terminology. Now,
as with any major technology group virtualization has come along, come with a long list off technical terms. Many of them are easy to understand. I've just thrown up a few on the screen for you here on dhe, when, when they were encountered in context, they're easy to understand, but that some can be a bit confusing,
especially when not everyone uses them the same way, which happens more often than you might think.
So here. I've provided a few of the most common ones on each of them on like use of each of them in the same fashion as you would find in Microsoft documentation. I think that's important, because if you're gonna be looking up things regarding hyper V, you need to use the same vernacular and terminology that Microsoft would use. Otherwise,
you could end up doing something very, very seriously wrong and
cause some sort of catastrophic failure if you get the wrong thing installed or configured.
in the interest of brevity, know all the terms
will be hugely explained here. You could literally I could make us an hour and 1/2 session just on the terminology. These are the ones that you'll find most often s. So I wanted to kind of put those on the screen on, show you those s so that we can kind of get them through. But later material will explore all of these concepts in depth
on dhe. Yes, So it's, uh
so you've got hit secret hyper V. That's obviously the general product name hope of the server. This is that free edition that I told you about. There's no interface. You can't be switched to a graphical interface mode on. It's basically the most basic features of Windows server mixed with hyper V.
Then you got Windows Server with hyper V slight different naming convention that this is all complete copies of Windows Server that allowing you to enable hyper V is a role You can't convert them to core afterwards. If you wanted to call being the equivalent type of the server,
but you could do other rolls off the system as well. If any of you are really good with power shell or you're looking into going into power shell,
look into Windows Server core as well the host. So this is the physical computer system running hyper V, and then you got the guest. Many people call it of'em. The actual terminology is guest on. It refers to an operating system that is virtualized on the host machine effectively,
so you can usually guess from the context when you're saying, Oh, that guest machine is running on this host, you kind of figure out if you've never heard of it before, so it does kind of sit, sit quite well there.
And then we have finally hyper V corps. So this is This is non terminology.
Don't ever listen to anyone that tells you to use hyper V call. It doesn't exist. It's a nonsense term. You shouldn't use it. It's not clear from the term whether or no hyper V server or Windows server in call mode is being referenced.
Anyone who says hyper V Corps just needs to rethink what they're saying because you can have hyper V Server, which runs in the core environment. Or you can have Windows Server with hyper V that is either a graphical user interface or Windows server core.
It's a little confusing, but once you get the concept of core, which is effectively just a command prompt,
it becomes a lot more easy to understand. Eso hyper v corps.
It won't actually tell you what you're actually using, so don't try not to use that terminology, and that's probably the only one I would say. That is a definite is it. But don't use it at all effectively.
So we come up to the 1st 1 here. We're gonna just quickly recap so throughout this, we've been talking about understanding hyper V in professional, personal and certification environments. We've got a basic understanding of virtual ization in general. I say basic,
there was this fairly in debt, but I think it's important
Grasp the foundations of virtual ization in general. Andi kind of explains to you the savings that come with it and the benefits of it. And also, hopefully you've got a general knowledge of some of the terminology around hyper V as well on virtual machines and how they interact with an operating system and hardware that kind of thing as well.
So that's the introduction session. It's a fairly hefty introduction. I know. But bear with me. I promise you, there's a lot more, a lot more in engagement coming on, and we're gonna be actually looking at through the We're gonna be doing demonstrations as well, various points like that as well.
we're gonna move into requirements with this next flight. So what we're gonna be talking about here, we're gonna be going into what hyper V needs. We're gonna understand what the hardware requirements are
for installing hyper V on both service and clients. So whether or not. You're working in a professional environment or just working from home. What do you want to do? We're gonna be understanding the software requirements for installing hyper V on both of them as well. So hardware and software effectively, those are our two.