Lesson finished
Up next: Type 1 and Type 2 Hypervisors with vSphere, VirtualBox and KVM Demos
Unlock all 37 lessons of Network Function Virtualization in 5GFull course ₹40,000 · paid
Server Virtualization Types: Full, Para, Hybrid and Containers vs VMs
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 2”
What will you learn in this free Network Function Virtualization in 5G lesson?
The instructor explains hardware virtualization as full, para and hybrid, covering x86 privilege rings, binary translation and hardware-assisted virtualization. The lesson then introduces operating system virtualization with containers and compares VMs and containers on kernel, boot time, size and isolation.
- Full, para and hybrid virtualization
- CPU rings and binary translation
- Hardware-assisted virtualization on Intel and AMD
- Container versus virtual machine differences
What comes after lesson 2?
The next free lesson is lesson 3, “Type 1 and Type 2 Hypervisors with vSphere, VirtualBox and KVM Demos” (28 min). 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 second session on Introduction to Virtualization. In this session, we will cover server virtualization. In the last session, we had gone through various components of a server, and now we will see how a server can be virtualized. So, let's start with server virtualization definition. So, server virtualization is the process of dividing a physical server into multiple unique and isolated virtual machines by means of a software called hypervisor. Each virtual machine can run its own operating system independently.
Virtualized server is called a compute. Now, key benefits of server virtualization are it provides a higher server ability, then cheaper operating cost, then it eliminates server complexity, then increased application performance, and it can deploy workload quicker. Okay. So, now we will go through various types of server virtualization. So, there are two types of server virtualization. So, first one is operating system virtualization, and second one is the hardware virtualization. So, so far, we have discussed hardware virtualization, wherein we have a hypervisor, which emulates the hardware resources into virtual resources, and virtual resources can be assigned to a VM.
And other virtualization technique is called operating system virtualization, or this is also called containerized virtualization, wherein we virtualize the operating system, not the hardware directly. So, same operating system kernel can be used by different containers. So, if we compare operating system virtualization, so if we compare operating system virtualization with hardware virtualization, so in hardware virtualization, if we have multiple VMs, each VM will have its own guest operating system, and it will have its own kernel. But in operating system virtualization, but in operating system virtualization, or it is also called cloud-native or containerized virtualization.
So, in this, containers will share the host kernel, and actually, that improves the performance. So, we will talk about operating system virtualization later in this session. Okay, so, let's start with hardware virtualization. So, we have got three types of hardware virtualization. First is full virtualization. So, in full virtualization, guest operating system is not aware that it is running on a virtualized platform. And in para-virtualization, guest operating system is aware that it is running on a virtualized platform. And then, the third one is hybrid virtualization. Which actually combines the advantages of both full virtualization and para-virtualization.
Then, full virtualization can be implemented in two ways. First one is hardware-assisted virtualization, which is also called virtualized technology. And second one is the software-assisted virtualization, which is called binary translation. And hardware-assisted virtualization can be implemented using type-1 hypervisor or type-2 hypervisor. And software-assisted virtualization can be implemented only using type-2 hypervisor. So, we will discuss various types of server virtualization in detail. Okay, so, let's start with full virtualization. So, in full virtualization, hypervisor simulates the hardware resources into the virtual resources for virtual machines to allow an unmodified guest operating system to run in isolation.
So, by unmodified guest operating system, it means that guest operating system runs in a same way as it runs on a physical server. So, it is not modified in any way to run on hypervisor or to run on a virtualized environment. So, virtual machines are unaware of the hardware simulation and communicates as they are directly accessing the hardware resources. Then, the hypervisor monitors the physical server's resources and keeps each virtual server independent. Then, we have some limitations of full virtualization. So, biggest limitation of using full virtualization is that a hypervisor has its own processing needs.
Then, this can slow down applications and impact server performance. Then, there are two ways to implement full virtualization. So, first one is software-assisted full virtualization. When hardware is not capable of doing the virtualization, then it is implemented by using the software. And it uses the technique called binary translation. Then, second way to implement full virtualization is to use hardware which is capable of doing virtualization. And we don't need any software assistant to do the virtualization. Okay. Now, we will see what is the software-assisted virtualization. So, before going to the software-assisted virtualization, let's try to understand various rings in the CPU.
So, x86 family of CPUs provide a range of production labels, also known as rings, in which code can execute. So, essentially, there are two rings, 0 and 3. So, a ring 0 has the highest level privilege and it is the ring where operating system kernel normally runs. And code executing in ring 1 runs in the kernel space or also it is called system space. And all other code, such as application running on the operating system, operates in a less privileged space, that is ring 3. So, we have a ring 0 where actually operating system runs and all the user applications run on ring 3.
And we will come to ring 1 as well. So, as we discussed in full virtualization, unmodified guest operating system is used. So, the term unmodified refers to operating system kernels which have not been altered to run on hypervisor. So, therefore, they still execute privileged operations as they are running directly on the physical server. So, in that case, operating system will always run in the ring 0. But even hypervisor requires privileged mode to run. So, in this case, additional privilege mode has been added on top of ring 0 and that is ring 1.
So, in ring 0, we will have a guest OS running. Then ring 1 hypervisor will run. And on ring 3, we will have user applications. Okay. So, it relies on binary translation to track and virtualize the execution of instruction sets. So, in binary translation, hypervisor uses the trap and emulate approach. So, hypervisor traps the instructions from the guest. So, if there is any instruction from the user application, it will come to the guest operating system. And guest operating system will send a trap to hypervisor. And now, hypervisor will emulate the behavior of these instructions.
That is why it is called trap and emulate. So, first hypervisor traps the instruction. Then it emulates the instruction. So, this method of emulation is called binary translation. Then it emulates the hardware using software instruction sets. Due to binary translation, it is often criticized for performance issues. Okay. Then examples of software-assisted virtualizations are VMware workstation, then virtual PC, then virtual box. So, next one is hardware-assisted virtualization. So, in hardware-assisted virtualization, interrupt is directly sent to the hardware. So, it directly interrupts with hardware using the virtualization technology, which has been integrated on x86 processors since 2005.
So, for Intel CPUs, it is called VPX. And for AMD processors, it is called AMD V. Guest operating system instructions might allow a virtual context execute privilege instructions directly on the processors, even though it is virtualized. So, all the instructions will actually directly be trapped using the hardware, that is a VPX or AMD V. Okay. So, examples of hardware-assisted virtualizations are VMware ESXi, then KVM, Hyper-V, and Xen. So, next virtualization kind is para-virtualization. So, in para-virtualization, virtual guests are aware that it is running on a virtualized platform.
So, unlike the full-virtualization, virtual guests are aware that it is running on a virtualized platform. Where guests, guest operating system are not aware that it is running on virtualized environment. So guest source codes are modified with sensitive information to communicate with the host. Then guest operating systems require extension to make API calls to the hypervisor. And in this case, so there will be some modification done on the guest operating system. So this typically involves replacing any privileged operation that might require to run in ring zero.
Then in full virtualization, guest will issue a hardware call. And in para-virtualization, guest will directly communicate with the host hypervisor using the drivers. So examples of para-virtualizations are Zen, then IBM, LPAR, then Oracle VM. Then we have these two types which are para-virtualized. Okay, so the third one is hybrid virtualization, which uses the advantages of both full and para-virtualization. So it is a combination of full and para-virtualization. The virtual machine uses para-virtualization for specific hardware drivers, where there is a bottleneck with full virtualization, especially with input-output and memory-intense workloads.
And the host uses full virtualization for other features. The following product supports hybrid virtualization, Oracle VM for x86, Zen, and VMware ASXI. Okay, so the next type of virtualization is operating system virtualization. And it is also called containerization, or it is also called cloud-native. And a host operating system allows multiple containers to share the host kernel. And there is a very little or no overhead since it uses the host operating system kernel for execution. So containers will not have its own kernel as we see that in case of hardware virtualization, the guest who is running on the virtual machine will have their own kernel.
Then example of operating system virtualization, Linux is CX, and the second one is Docker. Okay, so what is a container? So containers are isolated. However, they share the operating system kernel and appropriate bins, binary, and library. A Linux container lets you run a Linux system within another Linux system. Inside the container, it almost looks like a VM, but outside the container, it looks like normal processes running on the machine. It looks like a VM, but it is more efficient because it is very lightweight. So containers is equal to lightweight virtualization.
And containers do have their own network space. So containers will have their own IP addresses, and it will not share the IP address with the host. And containers will also have their own file system. Okay, so now let's try to identify the differences between a virtual machine and a container. So in hardware virtualization, we have server hardware, then on top of server hardware, we have hypervisor, then we have multiple virtual machines. And each virtual machine will have its own full-fledged operating system. This operating system will have its own kernel.
So for example, if you have three virtual machines on a given host, then all three virtual machines will have their own kernel. And that is why this is not efficient utilization of resources, because each VM will have its own guest OS, it will have its own binary and libraries, and it can run any application. So if we compare this stack with operating system virtualization, then we have server hardware. On top of server hardware, we'll have the host operating system. Now on top of operating system, we will not have hypervisor, but we will have container runtime, or it is also called container engine.
So one of the example of container engine is Docker. And so others are Rocket, then CRIO. So on top of operating system, we have container runtime or container engine. And on top of container engine, we have three containers. And these three containers will share the kernel from this host. So they are not going to have their independent kernel, unlike virtual machine. That is why these containers are very lightweight, because they don't have the full-fledged operating system. They will just have their own library and binary files, and they can run any application.
And also, one thing to notice here is, in hardware virtualization, this VM can be your Windows VM, this VM can be your Linux VM, this VM can be your Mac VM, because all are having their independent operating system, and there is no dependency. But if we look at operating system virtualization, so you can see that all the containers which are hosted on this hardware shares the host operating system kernel. So if this host is Linux, then all the containers which are hosted on this server should be based on Linux only.
So because we cannot run a Windows container here, because obviously it will not be compatible with the kernel on the Linux operating system. So whatever operating system we have on the host, same type of containers should be deployed on the host. Then only it will work, because all containers share kernel from the host operating system. Okay, now let's go through the differences between a VM and container. So VM belongs to hardware virtualization, and container belongs to operating system virtualization. And VM runs its own operating system and kernel, and container shares the host operating system.
Then hypervisor is required to virtualize the hardware, but for containers, we need a container runtime like Docker is required to virtualize the operating system. Then VM takes more time to boot. Then it takes in minutes, but containers, as they are very lightweight, they come up just in few seconds. Then VM size is large, as they have dedicated operating system, and containers are very lightweight. VMs are more secure, as they are isolated, and containers are less secure. Then examples of VM are KVM, Xen, then VMware, and examples of containers are Linux containers or containers by Docker.
So that's all in this session, and I will see you in the next one. Thank you.