Installing and configuring kvm ubuntu. Working with virtual machines KVM. Introduction. Creating virtual machines in GUI \
In this introductory article, I will briefly describe all the software tools used in the development of the service. More details about them will be discussed in the following articles.
Why ? This operating system is close and understandable to me, so when choosing a distribution kit, torment, torment and throwing was not tested. It has no particular advantages over Red Hat Enterprise Linux, but it was decided to work with a familiar system.
If you plan to independently deploy infrastructure using similar technologies, I would advise you to take RHEL: thanks to good documentation and well-written application programs, this will be, if not an order of magnitude, then certainly twice as simple, and thanks to a developed certification system, you can easily will find a certain number of specialists who are at the proper level of familiarity in this OS.
We, again, decided to use Debian Squeeze with a set of packages from Sid / Experimental and some packages backported and built with our patches.
There are plans to publish a repository with packages.
When choosing a virtualization technology, two options were considered - Xen and KVM.
The fact of the presence of a huge number of developers, hosters, commercial solutions based on Xen was also taken into account - the more interesting it was to implement a solution based on KVM.
The main reason why we decided to use KVM is the need to run virtual machines with FreeBSD and, in the future, MS Windows.
To manage virtual machines, it turned out to be extremely convenient to use products that use its API: virsh, virt-manager, virt-install, etc.
This is a system that stores the settings of virtual machines, manages them, keeps statistics on them, makes sure that the interface of the virtual machine rises at startup, connects devices to the machine - in general, it does a lot of useful work and a little more.
Of course, the solution is not perfect. The disadvantages include:
- Completely insane error messages.
- The inability to change part of the virtual machine configuration on the fly, although QMP (QEMU Monitor Protocol) does it quite well.
- Sometimes it is impossible to connect to libvirtd for some unknown reason - it stops responding to external events.
The main problem in the implementation of the service at the very beginning was the limitation of resources for virtual machines. In Xen, this problem was solved with the help of an internal scheduler that distributes resources between virtual machines - and, best of all, the ability to limit disk operations was implemented as well.
There was nothing like this in KVM before the advent of the kernel resource allocation mechanism. As usual in Linux, these functions were accessed through a dedicated filesystem. cgroup, in which, using the usual write () system calls, you could add a process to a group, assign it its weight in parrots, specify the kernel on which it will run, specify the disk bandwidth that this process can use, or, again, give him weight.
The profit is that all this is implemented inside the kernel, and you can use it not only for the server, but also for the desktop (which was used in the famous "The ~ 200 Line Linux Kernel Patch That Does Wonders"). And in my opinion, this is one of the most significant changes in the 2.6 branch, apart from the beloved # 12309, and not the next file system being filed. Well, maybe, except for POHMELFS (but purely because of the name).
My attitude to this utility library is very ambiguous.
On the one hand, it looks something like this:
And this thing is also damn hard to assemble from source, and even more so into a package: sometimes it seems to me that Linux From Scratch is somewhat easier to build from scratch.
On the other hand, it is a very powerful thing that allows you to create images for virtual machines, modify them, compress them, install grub, modify the partition table, manage configuration files, transfer hardware machines to a virtual environment, transfer virtual machines from one image to another, transfer virtual machines from the image to the hardware and, frankly, my fantasy lets me down a little. Oh, yes: you can also run a daemon inside a Linux virtual machine and access the virtual machine data live, and do all this in shell, python, perl, java, ocaml. This is a short and far from complete list of what you can do with.
Interestingly, most of the code is generated at the time of assembly, as well as the documentation for the project. Ocaml, perl are widely used. The code itself is written in C, which is then wrapped in OCaml, and the repetitive pieces of code are generated by themselves. Working with images is carried out by launching a special service image (supermin appliance), to which commands are sent inside it through a channel. This image contains some rescue set of utilities such as parted, mkfs, and other useful sysadmins in the household.
Recently, I even began to use it at home when I was picking out the data I needed from the nandroid image. But it requires a kernel with yaffs support.
Other
Below are some more interesting links to the description of the software tools used - read and study on your own, if interested. For example,
KVM (Kernel-based Virtual Machine) is free and open source virtualization software. You can create multiple virtual machines (VMs), each virtual machine has its own virtual hardware such as disk, processor, RAM, etc. It was included in the bulk of the Linux kernel in version 2.6.20 of the kernel.
If you are looking for an alternative VirtualBox, we highly recommend using KVM. We also personally use this amazing virtualization software.
Installing KVM Ubuntu 17.04
To install KVM, you must have the following presets.
- Enable virtualization in the system BIOS.
- Check the system CPU if it supports virtualization. Run the below command.
egrep - c ‘(vmx | svm)’ / proc / cpuinfo
When you get the output from the above command to be either 1 or more, it means the processor supports virtualization, otherwise 0 or less means it does not.
3. Check the architecture Ubuntu 16.04 LTS by executing one command i.e
X86_64 is a 64-bit kernel.
The i386, i486, i586, or i686 is a 32-bit kernel.
32-bit OS is limited to 2 GB of RAM maximum for a given virtual machine.
A 32-bit kernel will only host a 32-bit guest kernel, whereas a 64-bit kernel can have both 32-bit and 64-bit O.S.
Follow the steps to install KVM on Ubuntu
In this section, we will write down the steps for installing KVM. In our previous post, we learned. You may also be interested in this.
1. Installing KVM Ubuntu 17.04 and other dependent packages
On Ubuntu 17.04 LTS, you can use the command apt or apt-get both. There will be no difference in packages installed with apt or apt-get command, so you are good here.
sudo apt update
sudo apt install qemu - kvm libvirt - bin bridge - utils
2. Learn about new users and group for KVM software
After installing the packages, some additions will occur in the number of users and groups.
(A) Two users are created.
- libvirt-qemu
- libvirt-dnsmasq
[email protected]: ~ $ tail - 2 / etc / passwd
libvirt - qemu: x: 64055: 129: Libvirt Qemu,: / var / lib / libvirt: / bin / false
libvirt - dnsmasq: x: 121: 130: Libvirt Dnsmasq,: / var / lib / libvirt / dnsmasq: / bin / false
s [email protected] :~ $
B) two groups will be created.
- kvm
- libvirtd
[email protected]: ~ $ tail - 2 / etc / group
kvm: x: 129:
libvirtd: x: 130: sharad
[email protected] :~ $
You may have noticed that the so-called "charade" used is a member of the "libvirtd" group. This means that this user can use KVM.
3. Check your KVM installation
It's quite easy to check your KVM installation. Run the command -
virsh - c qemu: /// system list
The first time it will show an error.
error: failed to connect to the hypervisor
error: Failed to connect socket to '/ Var / run / libvirt / libvirt-sock': Permission denied
[email protected] :~ $
To fix this problem, you must log out and log back in from your desktop. Indicates that the current user should log in again.
After logging in, rerun the command. This time, you should get the result as shown below. It is empty because no virtual machine is being created.
[email protected]: ~ $ virsh - c qemu: /// system list
Id Name State
—————————————————-
[email protected] :~ $
4. Install Virtual Machine Manager
Here we are using Virtual Machine Manager which is a desktop application for managing KVM virtual machines via libvirt.
Run this command to install Virtual Machine Manager.
sudo apt install virt - manager
You can open Virtual Machine Manager by entering it into Dash Home, click the icon, it will open the application.
To open Virtual Machine Manager through the command line, type -
virt - manager
Earlier, when we installed KVM on Ubuntu 14.04 LTS Desktop, we ran into a problem when creating the first virtual machine, but we solved it very easily. In Ubuntu 16.04 LTS Desktop, we did not find such an issue.
If you have any questions on the topic "Installing KVM Ubuntu 17.04" - write them to us in the comment form. We will help you sort out your question much faster.
If you find an error, please select a piece of text and press Ctrl + Enter.
I previously wrote about the installation Qemu-KVM in Debian... But, in my opinion, the information is incomplete. Plus, I didn't take into account some of the nuances. Therefore, I bring to your attention an updated article on installing the Qemu-KVM virtual machine. Of course, I will delete the old article.
I think to explain what is virtual machine, not worth it. You probably know this (since you are reading this article). If not - . We will dwell directly on the subject. Qemu-KVM is a project to combine two wonderful (in my opinion) technologies of full virtualization. Qemu is a kind of "computer emulator" that supports a great variety of hardware architectures. In it, you can run almost any OS for any device (for example, I ran old versions Mac OS X which for PowerPC). The disadvantage of Qemu is its slowness due to the lack of hardware acceleration. And then another project comes to the rescue - KVM... Or Kernel Virtual Machine. KVM is a Linux kernel technology that enables hardware acceleration while fully virtualized. The disadvantage of KVM is that it only supports x86 architecture
Why Qemu-KVM? For Linux, this is the most recommended virtualization project. It works faster than VirtualBox and VMware Player(according to my tests), KVM is a technology native to Linux. Plus, if you own a good gaming computer with two video cards, you can install in Qemu-KVM Windows, throw one of the video cards into it, and forget about rebooting into another OS. If you wanted to play, you launched a virtual machine with Windows and play. Performance will be 95% of the performance installed on Windows hardware. But this is just gorgeous, in my opinion. I will write a separate article about this. It will be interesting:)
And now I will describe our plan of action. Firstly, I will carry out the installation using the example Debian 8.2 GNOME 64 bit though, there won't be much difference in other graphical environments. Secondly, I will describe working with KVM only in graphical mode (we will not install it on the server). Therefore, no terminals, scripts, and so on, as is usually done in the case of server virtualization. Thirdly, I advise you to additionally read the documentation for Qemu and KVM (I will give links at the end of the article). This will come in very handy if you want to make the most of the full potential of this bundle. Well, our plan of action is clear. Now the steps of action:
- installing qemu-kvm;
- installation of a graphical manager and additional utilities;
- configuring a network bridge;
- creating storage for virtual machines;
- installation of the guest system.
egrep "(vmx | svm)" / proc / cpuinfo
The command output must contain either vmx or svm... If they are not there, check if virtualization is enabled in BIOS (look for items Intel VT-i or similar for AMD). If there is nothing, then no luck.
We install the necessary components:
sudo apt install qemu-kvm bridge-utils libvirt-bin virt-manager
Add ourselves to the libvirt group:
sudo adduser $ USER libvirt
Now let's set up the network. In order for all virtual machines to go online and communicate with each other, you need to create a network bridge and virtual network cards for each virtual machine ( tap devices). Since we will install virtual machines from the graphical interface, we do not need to create tapes manually. Virt Manager will do it for us every time we start. We only need to set up the bridge. First, let's enable routing in the kernel:
sudo nano /etc/sysctl.conf
We are looking for the line net.ipv4_forward = 0 and change its value to 1 ... We save and:
sudo sysctl -p
Further, I will assume the following: 1) your computer has one network card that receives an ip-address from the router. 2) you access the Internet via a 3G modem, and your network card is free. This option involves more manual work, but it has been tested many times (at the very same on one of the machines). So, open the interfaces file:
sudo nano / etc / network / interfaces
Its default content is:
auto lo
iface lo inet loopback
We change its contents. For the first option:
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet manual
auto br0
iface br0 inet static
address 192.168.0.2
gateway 192.168.0.1
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255
bridge_ports eth0
bridge_stp off
bridge_maxwait 0
bridge_fd 0
For the second option:
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
auto ppp0
iface ppp0 inet wvdial
auto eth0
iface eth0 inet manual
auto br0
iface br0 inet static
address 192.168.0.2
gateway 192.168.0.1
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255
bridge_ports eth0
bridge_stp off
bridge_maxwait 0
bridge_fd 0
up route del default br0
Note: if you do not need automatic Internet connection via a modem after starting the system, remove the auto ppp0 lines from the config and
iface ppp0 inet wvdial. Otherwise, make sure the modem is plugged into the USB port when starting the system.
We save. Now for the option with a modem, you need to install the dialer wvdial:
sudo apt install wvdial
Editing the config (note: a 3G modem is used as an example Beeline... You can easily find examples of configs for other modems on the Internet):
sudo nano /etc/wvdial.conf
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0 = 0 & C1 & D2 + FCLASS = 0
Init3 = AT + CGDCONT = 1, "IP", "home.beeline.ru"
Stupid Mode = 1
ISDN = 0
Modem Type = USB Modem
New PPPD = yes
Phone = * 99 #
Modem = / dev / ttyACM0
Username = beeline
Password = beeline
Baud = 9600
Country = Russia
Auto Reconnect = on
Auto DNS = off
Idle Seconds = 0
We save. Now the modem will turn on immediately after the system boots. The up route del default br0 line removes the default route across the bridge. If you do not do this, you will not be able to connect to the Internet, since the traffic will go over the bridge, and not through the 3G modem.
The last step we need to say firewall so that it passes traffic from our virtual machines to the network and vice versa. To do this, you can go in two ways: write a script with several rules for iptables, which will be launched together with the system, or enter these rules manually and save them. I will use the first option. For the second, you will need to install the package iptables-persistent and just enter the rules one at a time (using sudo). So. create a script (in any text editor). Paste the following content there:
#! / bin / sh
# Determine the output interface for which address replacement (NAT) will be applied
iptables -v -t nat -A POSTROUTING -o ppp0 -j MASQUERADE
# We forward all packets that came to the modem from the global network (0.0.0.0/0) to the local network (192.168.0.0/24)
iptables -v -A FORWARD -i ppp0 -o br0 -s 0.0.0.0/0 -d 192.168.0.0/24 -j ACCEPT
# Forwarding all packets from the local network (192.168.0.0/24) to the global (0.0.0.0/0)
iptables -v -A FORWARD -i br0 -o ppp0 -s 192.168.0.0/24 -d 0.0.0.0/0 -j ACCEPT
We save it as gateway.sh and grant execution rights (either in the file properties or in the terminal with the command chmod + x gateway.sh). Now you can either start it manually after the system has booted, or add it to startup. To do this, move the script to ~ / .config / autostart(in the file manager, enable the display of hidden files, and you will see the directory .config in your home directory).
Everything is now ready to install the virtual machine. From the application menu, launch Virt Manager (virtual machine manager):
Right-click on the line localhost and choose Details... Go to the tab Storage... We need to specify the directory (or disk / disk partition) to store the virtual machines.
In the lower left corner, click on the plus sign ( Add pool), indicate the type of storage and the path to it.
In the tab Network interfaces, you can check if everything works.
Now press File - New virtual machine... We indicate the path to the disk image, the type of virtual machine. Next, we indicate the amount of RAM for it and the number of processor cores. Next, we indicate our storage and click New volume... We indicate the name, we leave the type qcow2, and size. This will be a virtual hard drive. If you plan to install a system with a graphical shell and a bunch of programs, give more space (50 gigs). On the last tab, put a check mark on Change settings before launch, we check that our bridge is selected as the network device, write any name for the virtual machine and click To complete... You will see a window with the parameters of this virtual machine.
Go to the tab CPU, and put a tick on Copy host system processor settings.
Next to the tab Network(next), and also indicate vitio... In the tab Display indicate Spice, and on the tab Video - QXL... Usually this bundle provides the best graphics rendering performance, but you can experiment if you want. Please note that for Windows guest systems, a separate installation of the QXL driver is required (in Windows itself).
Now that everything is ready, in the upper left corner, click Start installation... And we install the system as usual, with one exception: as soon as the installer starts to automatically configure the network, click Cancellation, and select Configure the network manually... Specify the desired IP address for the virtual machine (in our case 192.168.0.3
), subnet mask ( 255.255.255.0
), gateway (the gateway will be the host address, that is 192.168.0.2
) and DNS server (just specify Google 8.8.8.8
). And that's all. You don't need to do anything further. Install the system and configure. In general, that's it. The steps described are a way to replace, say, VirtualBox with a better alternative. After reading the documentation, you will understand how powerful Qemu-KVM is. I deliberately did not describe here additional console parameters and methods for launching virtual machines through the terminal, since this is far from always necessary on a home machine. I will write a separate article about this on setting up a home multifunctional server (which can also act as a virtual machine server). For those who, for some reason, did not understand what was written, or there were incomprehensible moments - I suggest watching the video, in which I will not describe, but will show you how to install and configure all this stuff. If you have any suggestions or additions to the article - write in the comments.
KVM or Kernel Virtual Module is a virtualization module for the Linux kernel that allows you to turn your computer into a hypervisor for managing virtual machines. This module operates at the kernel level and supports hardware acceleration technologies such as Intel VT and AMD SVM.
By itself, KVM software does not virtualize anything in user space. Instead, it uses the / dev / kvm file to set up virtual address spaces for the guest machine in the kernel. Each guest machine will have its own video card, network and sound card, hard drive and other equipment.
Also, the guest system will not have access to the components of the real operating system. The virtual machine runs in a completely isolated space. You can use kvm on both a GUI system and servers. In this article, we will look at how the kvm Ubuntu 16.04 installation is performed
Before proceeding with the KVM installation itself, you need to check if your processor supports hardware accelerated virtualization from Intel-VT or AMD-V. To do this, run the following command:
egrep -c "(vmx | svm)" / proc / cpuinfo
If the result is 0 - then your processor does not support hardware virtualization, if 1 or more - then you can use KVM on your machine.
Now we can move on to installing KVM, a set of programs can be obtained directly from the official repositories:
sudo apt install qemu-kvm libvirt-bin bridge-utils virt-manager cpu-checker
We installed not only the kvm utility, but also the libvirt library and the virtual machine manager. After the installation is complete, you need to add your user to the libvirtd group, because only root and users in this group can use KVM virtual machines:
sudo gpasswd -a USER libvirtd
After running this command, log out and log back in. Next, let's check if everything was installed correctly. To do this, use the kvm-ok command:
INFO: / dev / kvm exists
KVM acceleration can be used
If everything was done correctly, you will see the same message.
Using KVM on Ubuntu 16.04
You have completed the task of installing kvm on Ubuntu, but you cannot use this virtualization environment yet, but it still needs to be configured. Next, we'll take a look at how kvm Ubuntu is configured. First you need to set up your network. We need to create a bridge through which the virtual machine will connect to the computer's network.
Configuring a Bridge in NetworkManager
This can be done in several ways, for example, you can use the NetworkManager network configuration program.
Click on the NetworkManager icon in the toolbar, then select change connections, then press the button Add:
Then select the connection type Bridge and press Create:
In the window that opens, click the button Add, to link our bridge to the internet connection:
Select from the list Ethernet and press Create:
In the next window, select in the field device, the network interface to which our bridge should bind:
Now you will see your bridge in the list of network connections. It remains to reboot the network to fully apply the changes, to do this, run:
Manual bridge setup
First you need to install the bridge-utils suite of utilities if you haven't already:
sudo apt install bridge-utils
Then, using the brctl program, we can create the bridge we need. To do this, use the following commands:
sudo brctl addbr bridge0
$ sudo ip addr show
$ sudo addif bridge0 eth0
The first command adds the bridge device br0, with the help of the second you need to determine which network interface is the main connection to the external network, in my case it is eth0. And with the last command, we link the bridge from br0 to eth0.
Now you need to add a few lines to the network settings so that everything rises automatically after the system starts. To do this, open the file / etc / network / interfaces and add the following lines there:
sudo gedit / etc / network / interfaces
loopback
auto lo bridge0
iface lo inet loopback
iface bridge0 inet dhcp
bridge_ports eth0
When the settings are added, restart the network:
sudo systemctl restart networking
Now the installation and configuration of KVM is complete and you can create your first virtual machine. After that, you can see the available bridges using the command:
Creating KVM virtual machines
The KVM Ubuntu setup is complete and we can now move on to using it. First, let's go through the list of already existing virtual machines:
virsh -c qemu: /// system list
It is empty. You can create a virtual machine through the terminal or in the graphical interface. Use virt-install to create via terminal. First, let's go to the libvirt folder:
cd / var / lib / libvirt / boot /
To install CentOS, the command will look like this:
sudo virt-install \
--virt-type = kvm \
--name centos7 \
--ram 2048 \
--vcpus = 2 \
--os-variant = rhel7 \
--hvm \
--cdrom = / var / lib / libvirt / boot / CentOS-7-x86_64-DVD-1511.iso \
--network = bridge = br0, model = virtio \
--graphics vnc \
--disk path = / var / lib / libvirt / images / centos7.qcow2, size = 40, bus = virtio, format = qcow2
Let's take a closer look at what the parameters of this command mean:
- virt-type- type of virtualization, in our case kvm;
- name- the name of the new car;
- ram- the amount of memory in megabytes;
- vcpus- the number of processor cores;
- os-variant- type of operating system;
- cdrom- installation image of the system;
- network-bridge- the network bridge that we configured earlier;
- graphics- the way to get access to the graphical interface;
- diskpath- the address of the new hard disk for this virtual machine;
After the installation of the virtual machine is complete, you can find out the VNC connection parameters using the command:
sudo virsh vncdisplay centos7
Now you can enter the received data into your VNC client and connect to the virtual machine even remotely. For Debian, the command will be slightly different, but it looks the same:
Go to the folder for images:
cd / var / lib / libvirt / boot /
You can download the installation image from the Internet if necessary:
sudo wget https://mirrors.kernel.org/debian-cd/current/amd64/iso-dvd/debian-8.5.0-amd64-DVD-1.iso
Then let's create a virtual machine:
sudo virt-install \
--virt-type = kvm \
--name = debina8 \
--ram = 2048 \
--vcpus = 2 \
--os-variant = debian8 \
--hvm \
--cdrom = / var / lib / libvirt / boot / debian-8.5.0-amd64-DVD-1.iso \
--network = bridge = bridge0, model = virtio \
--graphics vnc \
--disk path = / var / lib / libvirt / images / debian8.qcow2, size = 40, bus = virtio, format = qcow2
Now let's look at the list of available machines again:
virsh -c qemu: /// system list
To start the virtual machine, you can use the command:
sudo virsh start machine_name
To stop:
sudo virsh shutdown hostname
To put into sleep mode:
sudo virsh suspend machine_name
To reboot:
sudo virsh reboot machine_name
sudo virsh reset machine_name
To completely remove a virtual machine:
sudo virsh destroy machine_name
Creating virtual machines in GUI \
If you have access to the graphical interface, then there is no need to use the terminal, you can use the full-fledged graphical interface of the virtual machine manager Virtual Manager. The program can be started from the main menu:
To create a new car, click on the icon with the monitor icon. Next, you will need to select the ISO image of your system. You can also use a real CD / DVD drive:
On the next screen, select the amount of memory that will be available for the virtual machine, as well as the number of processor cores:
On this screen, you need to select the hard disk size that will be available in your machine:
At the last step of the wizard, you have to check the correctness of the machine settings, as well as enter its name. You also need to specify the network bridge through which the machine will connect to the network:
The machine will then be ready for use and will appear in the list. You can launch it using the green triangle on the manager toolbar.
conclusions
In this article, we looked at how to install KVM Ubuntu 16.04, discussed how to fully prepare this environment for work, as well as how to create virtual machines and use them. If you have any questions, ask in the comments!
To conclude, a lecture from Yandex about what virtualization is in Linux:
The release of WordPress 5.3 improves and expands the block editor introduced in WordPress 5.0 with a new block, more intuitive interactions, and improved accessibility. New features in the editor [...]
After nine months of development, the FFmpeg 4.2 multimedia package is available, which includes a set of applications and a collection of libraries for operations on various multimedia formats (recording, converting and [...]
Linux Mint 19.2 is a Long Term Support release that will be supported until 2023. It comes with updated software and contains improvements and many new [...]
The release of the Linux Mint 19.2 distribution kit, the second update of the Linux Mint 19.x branch, formed on the Ubuntu 18.04 LTS package base and supported until 2023, is presented. The distribution is fully compatible [...]
New BIND service releases are available that include bug fixes and feature enhancements. New releases can be downloaded from the downloads page on the developer's site: [...]
Exim is a message transfer agent (MTA) developed at the University of Cambridge for use on Unix systems connected to the Internet. It is freely available in accordance with [...]
After nearly two years of development, ZFS on Linux 0.8.0 has been released, an implementation of the ZFS file system packaged as a module for the Linux kernel. The module has been tested with Linux kernels 2.6.32 to [...]
The Internet Engineering Task Force (IETF), which is developing Internet protocols and architecture, has completed the formation of an RFC for the Automatic Certificate Management Environment (ACME) protocol [...]
The non-profit certification center Let’s Encrypt, controlled by the community and providing certificates for free to everyone, summed up the results of the past year and spoke about plans for 2019. […]
A new version of Libreoffice has been released - Libreoffice 6.2