Lesson finished
Unlock all 37 lessons of Network Function Virtualization in 5GFull course ₹40,000 · paid
Type 1 and Type 2 Hypervisors with vSphere, VirtualBox and KVM Demos
A free lesson from Skill-Lync's Network Function Virtualization in 5G course, on Grow by Skill-Lync · Last updated 16 Nov 2026 · Session: “Week 1 Session 3”
What will you learn in this free Network Function Virtualization in 5G lesson?
The instructor distinguishes type 1 and type 2 hypervisors and explains why KVM counts as type 1. The lesson demonstrates the VMware vSphere client in a hands-on lab, creates an Ubuntu VM in Oracle VirtualBox, and lists Linux commands for checking compute resources.
- Type 1 versus type 2 hypervisors
- VMware ESXi and vSphere hands-on lab
- Creating an Ubuntu VM in VirtualBox
- Checking vCPU, memory, disk and interfaces
What comes after lesson 3?
Later in Skill-Lync's Network Function Virtualization in 5G course (paid): lesson 4, Week 2 Session 1; lesson 5, Week 2 Session 2 Part 1; lesson 6, Week 2 Session 2 Part 2. The full course has 37 lessons (18 h 55 min of video); see the course overview or its price and syllabus.
Lesson transcript
Machine transcript of the lesson audio (lightly cleaned). Technical terms may contain errors; the video is the reference.
Hello and welcome to the session on Network Function Virtualization in 5G. This is week one and the third session on Introduction to Virtualization. In this session, we will cover different types of hypervisors. So hypervisors emulate the physical resources into virtual resources so that guest virtual machine can use them. Hypervisors provide access to the virtual resources to the VMs. VMs think that the actual physical hardware is at its disposal. VMs don't know that they are sharing the available computer resources. So on right hand side, we can see we have the physical resources. So CPU is based on x86 architecture.
Then on top of that, we have virtualization layer that is the hypervisor which emulates these physical resources to the virtual resources. And these virtual resources are then assigned to the respective virtual machines. So the virtual resources are virtual CPU, virtual memory, virtual NIC and virtual disk. And hypervisor also provides strong isolation between virtual machines. So next one is the types of hypervisors. So there are two types of hypervisors. Type 1 hypervisor and type 2 hypervisor. So type 1 hypervisor is called bare metal hypervisor or native hypervisor.
And type 2 hypervisor is also called hosted hypervisor. So there are two definitions for type 1 hypervisor. So it should run on a bare metal and both the conditions can be true. Or even if one condition is true, still that hypervisor will be called as type 1 hypervisor. So first condition is hypervisor should run on the bare metal. And second condition is it should run in the kernel space. So for example, KVM is type 1 hypervisor, but it is actually deployed along with the Linux operating system.
So it runs along with Linux operating system. So it does not run directly on bare metal, but it runs on Linux. But as it operates in the kernel space, it is called type 1 hypervisor. So we have the hardware, then if it is a bare metal hypervisor, then hypervisor will directly run on the hardware. And then VMs will be deployed on top of hypervisor. So this is for the first condition. So when hypervisor runs directly on the bare metal, but for some of the hypervisors like ESXi and KVM, they run along with their operating system.
But as they operate in the kernel space, they are still called a type 1 hypervisor. Then type 2 hypervisor, it runs on operating system. That is the first condition. And second condition is it runs in the user space. So same is true for type 2 hypervisor as well. Either both the conditions have to be true or even if one condition is true, still hypervisor will call it as type 2 hypervisor. So in type 2 hypervisor, we will have hardware and on top of hardware, there will be an operating system.
And on top of operating system, there will be the hypervisor and then VMs will be deployed. So for the second condition, we have a quick emulator hypervisor that is KEMU, which runs in the user space. So that is why KEMU is the type 2 hypervisor and other type 2 hypervisors are VMware workstation, which runs on top of operating system. Then we have CERN virtual box. So type 1 hypervisor. So a bare metal hypervisor or type 1 hypervisor is a layer of software that is installed directly on top of a physical server and its underlying hardware.
There is no software or any operating system in between, hence the name bare metal hypervisor. Type 1 hypervisor runs in the kernel space to get the direct access to the hardware. Then type 1 hypervisor is proven in providing excellent performance and stability since it does not run inside any operating system. Then type 1 hypervisors are an operating system themselves, a very basic one on top of which they can run virtual machines. So for example, KVM. KVM comes with operating system Linux. So now we will discuss some of the type 1 hypervisor vendors.
So to start with, it is a VMware ESXi. So it is a product of VMware. Then it is management functionality is built into the VM kernel. So VM kernel is the operating system with which ESXi works. Then supports live migration of VMs. Then very secure against threats. Then supports auto load balancing. And it also supports advanced backup and restore of virtual machines. So once you boot a server with ESXi, this is how it looks like. So VMware ESXi hypervisor is screened after the server boots up.
So ESXi can be actually directly installed on the host and it can be managed directly from the ESXi. Also, it can be managed by vCenter and vCenter can actually manage multiple clusters. So actually to practice vSphere and to have a hands-on on ESXi, we can go to the VMware site and there are some free labs. So actually we can just create an account on VMware site and we can access to the labs. So let's go ahead and try to access a vSphere lab. Okay, so you need to go to the VMware.com and try hands-on labs.
So you can see there are N number of labs and you can go to the vSphere and you can practice. So let's do that. So this is the one vSphere getting started. So you can click on the start lab and you can create an account. And once you have created an account, you can actually start the lab. So I have already created an account and let's directly go through it. So once you create an account, you will see something like this. So I will click return to your lab and we will get into the lab.
Okay, so console is loading. Okay, so this is the console or the jump host from where we can log into vSphere and we can go through the ESXi. So on this, you have a lab guide as well. You can click on the lab guide and you can learn more about the lab. So now once you are in the console, just go to the web browser. So this is Chrome and you can see that it already has the link to access vSphere. So this is a VMware vSphere and even actually credentials are auto populated.
So we can directly go ahead and log into the vSphere and we will see the multiple clusters. So just click on this and you can log in. Okay, so this is how vSphere client looks like. And so on the first tab, we can see host and cluster. So let me just zoom in a bit. Okay, so the first tab is host and cluster. Then the second tab is a VMs and templates. Then third one is the storage and fourth one is the networking. So let's go ahead and try to explore this a bit.
So the first tab, which is host and cluster. So this is the first cluster and this is the second cluster. So it has got two clusters and let's see what is there in the first cluster. So in the first cluster, we have a region A01 and then again we have A01 compute 01. So the first compute 01 region has got two ESXi hosts. So these are the ESXi hosts which are deployed on any server. So let's click on the first ESXi host and let's go through the summary.
So we will see what is the spec of the first ESXi host. So once you are here. Okay, so just let me bring this down. So this is the ESXi host one. And if you want to see the hardware properties, these are the hardware properties. So it has got two V CPUs. Then it has got six GB of memory and it has got a flash disk of 3.75 GB. And it is using a networking as well. So there are five networks attached to this. resources, there are two physical adapters.
... And there is one DataStore. So this is the ESXi 1. Then if you can go through the ESXi 2 as well. So even it has got the similar specs. So these are the ESXi hosts and rest these four are the VMs. In ESXi host itself, you can go and click VMs. So you will see which all VMs are hosted on that ESXi host. So it has got a VM called CoreA. And if you want to see all the VMs that belongs to this cluster, you can actually go and click. So this is the first VM, App01A. And if you want to log in to this VM, you can actually go to the console as well. So just click on the console and you should able to log in using the credentials.
So let's go back and see some other things as well. So yeah, so this is the summary. Then you can go through other things as well. So this is the monitor tab, then configure, then you have permissions, then you have data store. So there is one data store which belongs to this region, then you have networks. So there is one network. So this is the distributed switch. And you can go to the ports. So these are the ports. So these are the ports which are assigned to the network and host. So it is hosted on these two ESXi hosts. So these networks are present on these two ESXi hosts.
Okay, so now let's go back to this. And similarly, you can actually go through the other VMs which are deployed on this region. And this is the second cluster. And again, second cluster has got region B01. And inside that you have again two ESXi hosts. And in this cluster, total you have five VMs. So this is one way to go through all these components from the first tab that is host and cluster. But if you directly want to go through the VM, you can just click the second tab. And these are the VMs in each cluster.
So you can click on core A and summary will give you the summary of the VM. So it is currently VM is in a powered off state. And similarly, you can go through the other VMs as well. And third tab is the storage tab. So cluster one has got one storage. So this is the storage. And you can see the summary of this storage. And so what are files are available on this storage. So these are the files. And similarly, even the second cluster has got one storage. And last one is the networking tab. So you can access all the networks, which are present in respective cluster. So cluster one has got total five networks. And you can also see so these five networks are attached to both the ESXi.
And also you can see which all VMs these networks are connected to. So you can explore more on vSphere. And you can actually learn more about this. Let's see what is the next hypervisor vendor. So the other most popular hypervisor is KVM. So kernel based virtual machine. So KVM is an open source hypervisor that contains all the features of Linux with the addition of many other functionalities and runs in the kernel space and has direct access to hardware. So whenever we deploy OpenStack, so OpenStack uses KVM. So we will see that in the next sessions.
Then other hypervisor is Microsoft Hyper-V. So it is from Microsoft and alternative to VMware ASXI in terms of features. So other type one hypervisors are Oracle VM. So this hypervisor has open source Zen at its core and it is free. So Oracle virtual box can be deployed in the laptop. And advanced features are available only in the pet versions. The next one is the Citrix hypervisor that is Zen server. So this server virtualization platform by Citrix is the best suited for the enterprise environment. Then it can handle all types of workloads and provides features for the most demanding tasks.
Okay, so now we will see type two hypervisors. So this type of hypervisor runs inside an operating system of a physical host machine like an application and type two hypervisor runs in the user space. It does not run in the kernel space because it does not have directly access to the hardware resources. There is no need to install separate software on another machine to create and maintain your virtual environment. And type two hypervisors are typically found in environment with a small number of servers. Okay, so next we will see some of the type two hypervisors.
So first one is Oracle VM virtual box. So a free but stable product with enough features for personal use and a good solution for both desktop and server virtualization. Then second one is from VMware that is VMware Workstation Pro or VM Fusion supports advanced features and has seamless integration with vSphere and VMware Workstation Pro is for Windows OS and VM Fusion is for Mac OS. So you can deploy Oracle virtual box. So you can deploy Oracle virtual box in your laptop. It is free and this is how it looks like if it is deployed on the laptop.
So let's quickly go through this and let's see how it looks like. Okay, so you can directly go to Google and you can type download Oracle virtual box and you can go through this link. And you can download virtual box depending on your laptop configuration. If it is Windows, then you need to download this. If it is Mac, you can download or if it is Linux, you get the Linux version as well. So once you install it in your laptop, this is how it will look like.
So once you install Oracle virtual box in your laptop, this is how it will look like. So there is one VM already created and you can see this VM is currently in the aborted state. Okay, so let's remove this and let's try to create a new one. Okay, so you can click on new and you can name Ubuntu VM. So it will automatically take the type. So type is Linux and Ubuntu. Then you can continue. So you can assign the one GB that is the recommended memory to this VM.
Then create a virtual hard disk. Now you can keep the default selection. And then you need to select a virtual box, a disk image. Continue. And you can keep dynamically allocated for the storage on physical hard disk. And you can keep this path or you can change this path. And so by default it is assigning 10 GB space. Okay, so now it has been created. And it is spawned off. So next is you need to download Ubuntu image and you need to boot this VM using Ubuntu image.
So now if you want to change any of the settings. So now all the settings that we have configured is available here to view. So it is a name is Ubuntu VM. Type is Ubuntu. Then system base memory is 1 GB. Then you have boot order is floppy, optical and hard disk. Then you have the acceleration. So this is a KVM para virtualization. Then display is video memory is 16 MB. Then these are the graphics controller. Then storage is controller SATA. So this is the storage that we have selected 10 GB.
Ubuntu VM.VDI. Then we have audio. Then one network adapter has been selected. Then there is no USB available. So USB drives available. So you can see zero active. Yeah. So now once your VM has been created and you want to change any of the settings. So now you can go to settings. So now this is the name and the type. Then you can go to the system. You can reduce the memory or increase the memory. Then display. Then display. Here also you can increase or reduce the memory.
Then storage. You can go here and you can change the port. Then this is audio. And this is network. You can add more number of adapters if you need. And likewise. So if you want to do any changes, it can be done here. Yeah. So this was the quick overview of Oracle VirtualBox. And I do recommend to download this and install this in your laptop. So that actually you can create a VMs and you can manage those VMs using Oracle VirtualBox. Okay. So next is. So next is.
Now we have seen how we can manage the virtual machines using a type one and type two hypervisors. Now for any production deployment, if we are using OpenStack and hypervisor is KVM, then what are the commands to operate or to manage the virtual machines? So now we will see that. So server running KVM or hypervisor. So virtualized server is called compute. So once you have virtualized a server was hypervisor is installed and you are logging into the virtualized environment. So that will be compute. So to see the virtual machines instances, you can use a worst list.
So first you need to log into the compute. Then you can type a worst list. So this compute is running two servers. So these are the virtual machines. So it is running. These are instances. These are the virtual machines. And to verify virtual CPU and memory, you can run a version node info command. So you can see this server is based on CPU x86 64. Then total number of CPUs are 36. So these are all virtual resources. So these are the virtual CPUs. Then CPU frequency is 2400 megahertz.
Then CPU socket is one. Then cores per socket is 18. Then thread per socket per core is one. It means hyper threading is disabled. So we are not using hyper threading here. So thread per core is one. And NUMA cell is two. So we will discuss this in the later sessions. NUMA stands for non-uniform memory access. Then the memory size. So this is how you can verify a virtual CPU and virtual memory resources on the compute. So we have listed down all the usual commands to verify different resources on compute.
So commands for KVM hypervisor. So if you want to display the hypervisor info, you can run a version node info list all the VMs. You can run a version list dash dash all. Then to start a VM, you can use a version start then VM name to shut down a VM. Then to power off, you can use a version destroy and the VM name. To suspend, version suspend. To resume, version resume and the VM name. So to save VM to a file, you can use version save and the VM name.
Then to restore a VM from a file, you can use version restore and VM name. Then to get the VM info, a version DOM info can be used. Okay. So similarly, if you want to verify the virtual vCPUs. So even a LSCPU command can be used. And it will also provide the similar information that we had seen in the earlier slides. So LSCPU, it will provide you the architecture. Then it will provide you the number of CPUs. Then number of online CPUs. Then thread per core, core per socket.
So all this information you can actually get in LSCPU as well. Then similarly, verifying the VM resources. So to verify the memory, you can use a free dash M. It will give you the total memory, then memory used and the memory which is free. Then for disk, DF minus H can be used to get to know what is the current usage of the disk in percentage. So size used available and use percentage. And also the mount path. Okay. So now next one is the virtual NIC on the interfaces.
So in the earlier session, we had discussed about various ports on the Cisco UCS server. So if you recall, we had discussed LOM ports, MLOM ports and PCI. So now if the same server is virtualized and then if you log into the compute, so you will get to see all those interfaces which are virtualized. So from the virtual machine, if you do IP link show, then these two interfaces, ENP6S0, ENP7S0. These two interfaces are MLOM port. MLOM port 1, MLOM port 2. Then ENO1, ENO2, these are LOM port.
LAN on motherboard. These are modular LAN on motherboard. So ENO1 and ENO2 are LOM port 1 and LOM port 2. And other ENP10, S0, F0, F1, then ENP133, S0, F0 and F1. So these four ports are the PCI ports. So if there is a requirement to have more ports, so these additional ports can be used. So these are how these ports are mapped. So 10, S0, F0 is mapped to PCI slot 1 port 2. And then F0 is mapped to PCI slot 1 port 1. And second one is port 2.
And 133, S0, F0 belongs to slot 4 port 1. And F1 belongs to slot 4 port 2. Okay, so we have already covered all the topics for the week one. So let's summarize whatever we have studied so far. So in this session, we familiarized ourselves with motivation behind virtualization. Then we have gone through what is virtualization and the different types of virtualization. Then physical servers that are commonly used in the industry. Then we had seen all the components of physical servers. Then we gone through server virtualization.
Then we have seen different types of hypervisors. Okay, so next is some challenges for you. So this is the lab challenge for your hands-on. So you need to deploy Oracle VirtualBox in your laptop. And then inside the Oracle VirtualBox, you need to deploy an Ubuntu VM. And once you deploy Ubuntu VM, you need to log into the VM. And you need to verify the virtual interfaces, then disk size, then memory, and virtual vCPU count. And challenge two is to judge your or understand your learning from week one.
So first one is try to answer these questions. What is a virtual machine manager? Then what is the difference between rack mount and blade servers? Then what is the difference between type one and type two hypervisors? Then why KVM is a type one hypervisor? Then what is the difference between LOM and MLOM NICs? So with this, we have concluded week one. And I will see you in the week two. Thank you. Take care. Wait, I'm just going to try to step if you move on. Hey!
Either you can change your mind. Thank you.