Skip to main content

CPU Virtualization Deep Drive

Understand CPU Virtualization:

At this time most modern CPU architectures support different levels of privilege, called rings. Ring 0 has the highest privilege; processes running in this ring are referred to as running in supervisor or kernel mode. Processes running in higher rings are referred to as running in user mode. The higher the number of the ring, the less privilege a process running in this ring has. An x86-based CPU supports four levels of privilege, but in practice only rings 0 and 3 are used. In Linux and Windows, the operating system kernel and hardware drivers run in Ring 0, and user processes run in Ring 3. Only processes in Ring 0 can access hardware. If a process in a higher ring needs to access hardware, such as the hard disk, it has to use the APIs of the kernel.

Here is the demonstration of CPU Rings with Native Operating System:

When we will use Xen, the Xen Hypervisor runs in Ring 0, and the operating system kernel is moved to Ring 1. This is the reason why the operating system has to be modified to run para-virtualized—the kernel has to “know” that it is running in Ring 1 instead of Ring 0. 

Here is the demonstration of CPU Rings with Xen Hypervisor:
When we will have "VT-enabled hardware" allows the Hypervisor to emulate a Ring 0 for the operating system kernel, allowing it to run unmodified:

Here is the damonstration of CPU Rings and VT-Enabled Hardware:
That is done about CPU Virtualization: 


Comments

Post a Comment

Popular posts from this blog

Docker Container Management from Cockpit

Cockpit can manage containers via docker. This functionality is present in the Cockpit docker package. Cockpit communicates with docker via its API via the /var/run/docker.sock unix socket. The docker API is root equivalent, and on a properly configured system, only root can access the docker API. If the currently logged in user is not root then Cockpit will try to escalate the user’s privileges via Polkit or sudo before connecting to the socket. Alternatively, we can create a docker Unix group. Anyone in that docker group can then access the docker API, and gain root privileges on the system. [root@rhel8 ~] #  yum install cockpit-docker    -y  Once the package installed then "containers" section would be added in the dashboard and we can manage the containers and images from the console. We can search or pull an image from docker hub just by searching with the keyword like nginx centos.   Once the Image download...
Post a Comment
Read more

Remote Systems Management With Cockpit

The cockpit is a Red Hat Enterprise Linux web-based interface designed for managing and monitoring your local system, as well as Linux servers located in your network environment. In RHEL 8 Cockpit is the default installation candidate we can just start the service and then can start the management of machines. For RHEL7 or Fedora based machines we can follow steps to install and configure the cockpit.  Following are the few features of cockpit.  Managing services Managing user accounts Managing and monitoring system services Configuring network interfaces and firewall Reviewing system logs Managing virtual machines Creating diagnostic reports Setting kernel dump configuration Configuring SELinux Updating software Managing system subscriptions Installation of cockpit package.  [root@rhel8 ~] #  dnf   install cockpit cockpit-dashboard  -y  We need to enable the socket.  [root@rhel8 ~] #  systemctl enable --n...
Post a Comment
Read more

Add The Group Information IN Yum Repository in simple Two steps

= Yum groups and repositories = Yum supports the group commands   * grouplist   * groupinfo   * groupinstall   * groupremove   * groupupdate Groups are read from the "group" xml metadata that is optionally available from each repository. If yum has no repositories which support groups then none of  the group operations will work.  #yum grouplist    This will list the installed and available groups for your system in two    separate lists. If you pass the optional 'hidden' argument then all of     the groups which are set to 'no' in the group xml tag.   yum groupinfo groupname     This will give you detailed information for each group including:   description, mandatory, default and optional packages.       #yum groupinstall groupname      #yum groupupdate groupname   Despite their differing names both of these commands perform the same   func...
Post a Comment
Read more