Install and use CentOS 7 or RHEL 7 as KVM virtualization host

CentOS 前端之家
前端之家收集整理的这篇文章主要介绍了Install and use CentOS 7 or RHEL 7 as KVM virtualization host，前端之家小编觉得挺不错的，现在分享给大家，也给大家做个参考。


When thinking about virtualization,everybody immediately thinks about VMWare. And it must be said,the product they offer is very decent but also comes with a “decent” price. As an alternative,it’s worth looking into KVM for your virtualization. As with the VMWare product range,KVM offers full virtualization and it can compete with VMWare regarding stability and performance.

Virtualization-terminology

To prevent things getting confused I would first like to clear out some terminology used for virtualization. For somebody working on a daily basis in virtual environments,these might be clear but can be rather confusing for others.

Host: the machine that hosts other system,KVM will be installed on this machine
Guest: the system running on the host,also referred to as VM,Virtual Machine or domain.
Hypervisor: the piece of software that enables virtualization on the host. For example: KVM,ESXi,Xen,…

Part1: KVM installation and preparation

KVM hypervisor and VM-extensions

As mentioned earlier,KVM offers,as VMWare,full virtualization. This means that a full system,which looks like a real physical system to the guest-OS,will be offered. Besides full virtualization,there is also such a thing as paravirtualization,as Xen can offer. Paravirtualization givesyou higher performance but needs a modified guest-OS and is basically limited to *nix-systems. Full virtualization enables you to run unmodified guest-systems and thus also most proprietary systems as Windows. In order to be able to use full virtualization,you either need some virtualization-extensions on your cpu or use emulation.

First thing to do is to check if the host-machinesupports VM-extensions. On the x86 platofrom,those are either AMD-V or Intel’s VT-X. In order to check if the installed cpu’s support those extensions,we need to check if the vmx (for VT-X) or svm (for AMD-V) flag exists in the cpuinfo-output:

When the output is 0,meaning that neither vmx or svm is found in the flags,it probably means that yourcpu doesn’t support those extensions and there is little you can do. When the extensions are listed,be sure to check if they are enabled in the systems BIOS since that would cause problems later on. In case your cpu doesn’t support VM-extensions,you are limited to QEMU-emulation in combination with KVM,which delivers a much worse performance in comparison. For this tutorial,I’ll assume that the VM-extensions are supported and enabled in the BIOS of the host-system.

KVM installation

The first step in the KVM installation is installing the necessary packages. Package virt-manager,xauth and dejavu-lgc-sans-fonts are also needed if you want to manage KVM with the graphical interface in combination withX11 forwarding. (for more information,checkthis previous post about X11 forwarding)

To install the required packages

Networking

For the networking part,our KVM-host will act as a router for its guests and wewill need to create a bridge interface to allow the guest to communicate out of the host. Guests will use NAT on the host to connect to the real network. To allow such type of setup it’s neededto allow ip forwarding in the kernel parameters.

After allowing the host to do ip forwarding,we need to change the network configuration. Basically we will keep our original physical interface as it is but will assign its IP-address to the brige. In the example host-machinethere is one real interface called eno16777736 and the script in/etc/sysconfig/network-scripts/ifcfg-eno16777736 looks like this:

The first thing to change here,is to comment out everything that is IP-related and tell the interface which interface will be the bridge. Resulting in /etc/sysconfig/network-scripts/ifcfg-eno16777736 to look like this:

8
DEVICE "eno16777736"
ONBOOT =yes
#IPADDR "192.168.202.111"
#NETMASK "255.255.255.0"
#GATEWAY "192.168.202.2"
HWADDR "00:0c:29:32:d0:4c"
#DNS1 "192.168.202.2"
BRIDGE =virbr0

Next,we can create the config-script for the bridge interface virbr0 in/etc/sysconfig/network-scripts/ifcfg-virbr0. Most details can be copied from the original script foreno16777736:

DEVICE "virbr0"
TYPE =BRIDGE
ONBOOT =yes
BOOTPROTO =static
IPADDR "192.168.202.111"
NETMASK "255.255.255.0"
GATEWAY "192.168.202.2"
DNS1 Finish and check the KVM installation

Basically all components are now ok but before KVM can be used it’s a good idea to perform a reboot in order to load the kvm-modules and to relaod the new network settings.

After the reboot,we should check if the necessary kernel modules are loaded,which means that KVM successfully can handle the VM-extensions of our cpu:

Check if the bridge is installed and in an up-state:

Last thing to check is if we can connect to KVM by asking for a simple list of systems:

If it returns something else,then you should go trough the earlier steps to check where something went wrong.

Part 2: Using KVM with the CLI

After completing the KVM installation,it’s time to start using the host. First thing we need to do is to create a new domain or VM.

Adding a new VM

To create a new virtual machine using the CLI,we need to know which template we will use to install the system. To get a list of templates that are known in our KVM installation,you can do the following:

Virtual disk images for the KVM-guests can be placed in /var/lib/libvirt by default. In case you prefer to use another location to store the disk images,SELinux will,by default,prevent access and the security context of that location needs to be changed in order to use it for KVM. To change the SELinux context when storing the images in another location (/vm for example):

Now,to add a new VM,we can use virt-install.

Example to add a windows-guest:

Explanation of the arguments that were given to virt-install:

After launching the above command,you should be able to connect with VNC to the host and get on the console-display of the VM. The console displays what would normally,on a physical machine,appear on the attached monitor.

By default,VNC will use the first availablescreen on port 5900. To be sure which screen is used,we can use virsh to show the attached console-screens for VNC:

:0 means the first screen and real port 5900 as you can also see when checking with netstat which ports are currently listening:

From this point,we can complete the windows installation as if it would be a normal physical system:

After completing the installation with VNC,we end up with a Windows-VM that is running on our KVM-host:

As for the networking part,we use the earlier created bridge (virbr0) to do NAT. This means that the KVM-host NAT’s all our connections to the real network connected to the KVM-host. If DHCP is active on that network,it can be used in the VM. Otherwise you will have to configure a static IP in the same subnet.

Example to add a Linux-guest:

To add a Linux guest,next to the already added Windows-guest is quite similar:

As with the Windows-VM,after launching this command,you should be able to connect with VNC to the host and get on the console of the VM to complete theDebian installation.

To know which VNC-display number (and port) is used for a certain VM,the same command as used earlier should do:

Above command gives :1 as result,meaning that the guest vmdeb7 can be contacted with VNC on port 5901:

After finishing the installation,weend up with a Linux guest running on top of our KVM-host. Which Linux distro we are using doesn’t matter since we’re doing full virtualization.

Considering network,the same as with the Windows VM applies here. Our connections are NATted trough the KVM-host and we can use the DHCP-server of our real network.

More KVM actions

Besides creating VM’s,it’s a good thing to know some basic operations regarding VM-managent.

List the active virtual machines:

Get more information about a guest:

Stop a running guest:

To stop a running VM in a clean way (as you would press the power button to start the shutdown sequence):

This triggers a normal,clean,shutdown on the guest:

To force stop a running VM that doesn’t want to shutdown in a clean way:

Start aguest:

Delete aguest:

First we need to make sure that the guest is stopped before it can be deleted. In case you don’t want the virtual disk image anymore either,you’ll have to delete it manually after undefining the guest.

After removing a disk-image,it’s a good thing to refresh the storage pool of KVM:

Automatically let a guest start when the host starts

When rebooting your host,you probably want some or all the guests that are defined on thathost to start at the same time. By default,the guest are not automatically started.

Part 3: Using KVM with the virt-manager GUI

Starting the GUI

Managing KVM with the CLI is not so difficult and it can be very handy to script certain day-to-day tasks. Sometimes,you just need to keep an overview and require a little more user-friendliness. For that,you can use virt-manager,which is a graphical interface for libvirt and is mainly built for KVM. When you want to manage your guest with virt-manager,you can either do it on the host itself,by starting an X-server locally or use X11 forwarding on a headless server (more informationhere).

Make sure that you have enough permissions to use virt-manager and simply execute virt-manager from the command line:

If all goes well,you should be presented with the virt-manager GUI:

Basic actions

From the initial start-up screen,you can immediately see a list of configured guests on this host and take actions on them like: Run,Pause,Shutdown,Reboot,Force off,…

When selecting a guest,you can also click on Open to display the console as we did earlier using VNC:

Advanced actions

Other possibilities using the virt-manager interface:

Connect to another host-system to manage the VM’s running there,using File -> Add connection (like using the –connect on the CLI)

Migrate a VM to another KVM-host: right click on the VM and choose Migrate…

Clone a VM to the same or another KVM-host: right click on the VM and choose Clone…

As you can see,the virt-manager interface is not very complicated and most of the basic tasks don’t need any explanation.

After completing all of the above steps,basic installation and using KVM shouldn’t have any secrets anymore for you. The next thing to do is experiment and test a little more with KVM and hopefully start to use it in your production environment.

url---http://jensd.be/207/linux/install-and-use-centos-7-as-kvm-virtualization-host

原文链接：https://www.f2er.com/centos/381295.html

猜你在找的CentOS相关文章

Centos7离线安装gcc4.8
有时候CentOS工作在无互联网的环境下，需要在离线环境下安装一些组件，这次实现的是模拟在...
CentOS7离线安装devtoolset-9并编译redis6.0.5
首先参照https://www.cnblogs.com/wdw984/p/13330074.html，来进行如何安装Centos和离线下...
使用Nginx在80端口上代理多个.NET CORE网站
有两个.NET CORE3.1网站部署在CentOS7上（内网IP是192.168.2.32），现在想实现访问http://...
CentOS7中配置vsftpd
1、yum -y install vsftpd 安装vsftpd 2、配置vsftpd的配置文件（/etc/vsftpd/vsftpd.conf...
CentOS7离线安装Mysql8.0
首先去mysql官网下载mysql的离线rpm安装包（https://downloads.mysql.com/archives/commun...
CentOS中增加网络连接数的方法
CentOS默认对外访问，发起的TCP链接总数小于28232个。 可以通过以下命令的结果计算出来 $ ...
VMware安装Centos7虚拟机
首先安装虚拟机很简单，所以呢，具体的安装过程就引用别人的博客，这篇文字很详细，引用之...
[Linux] 解决CentOS下Requires: libjson-c.so错误
当安装某些rpm包的时候 , 会爆出这个错误 Requires: libjson-c.so json-c是c语言下的json库...
阿里云centos7安装mysql8数据库
linux系统安装mysql8
centos安装mysql
一、安装 二、修改密码 三、修改远程连接权限(为了使用navicat)
LinuxWindowsCentOSUbuntuNginxWebServiceScalaMemcacheApacheRedisDockerBashAzureTomcatLNMPShell数据结构服务器运维网络安全
xebugnodemondocker-copydcoselasticsearcwindows-contdocker-windodocker-awsamazon-cloudenvoyproxyhashicorp-vaswisscomdevkafka-pythonzscalerphoton-osdocker-swarmkamongoogle-cloudconcoursewso2-ampersistent-vapi-managerprocess-manamanjarojenkins-workhypriotremoteapikeystonejsbitcoindbitcoin-test