On Ubuntu/Debian, VirtualBox is installed with the following command:Continue reading “Installing VirtualBox on Ubuntu”
When starting the virtual machine in VirtualBox, I noticed an error of the following content:Continue reading “VirtualBox Error Solution “Unable to load R3 module””
Sometimes I experiment on virtual machines with Linux Ubuntu Server and in order to be able to connect to them by IP address, open VirtualBox, select the desired machine, open “Configure” – “Network” and see that in the “Adapter 1″ tab there is a standard tick on ” Enable network adapter “and” Connection type: NAT “is selected. It is necessary for the Internet to work on the virtual machine.
You can change to “Network Bridge” and the virtual machine will try to get IP in the same network as the physical computer, for example from a router, and will also be visible on the network.
I will describe the procedure for adding the Hyper-V role to Windows Server:Continue reading “Install Hyper-V”
I noticed somehow on one installed VirtualBox that when adding a workstation, you can select the type of system only 32-bit.
To solve this problem, first of all you need to restart your computer and go into the BIOS when you turn it on (most often by pressing the DEL or F8 key), there you can activate the “Intel (R) Virtualization Technology” function (the name may differ slightly usually located in the Advanced section and the CPU), in my case it was turned off, and on many computers I noticed that it was disabled as standard.
To enable, change from Disable to Enable, save the settings and exit the BIOS (by selecting Save & Exit or similar).
After that, VirtualBox has the opportunity to choose the type of 64-bit systems.
It may also be necessary in the “Control Panel” to open the “Uninstall a program” button on the left “Enable or disable Windows components” and uncheck the “Hyper-V” box if it is installed.
Docker CE – a software platform for deploying applications, packaging applications into a container, adding libraries and all the necessary dependencies to run the application, which allows you to quickly launch the code in almost any environment. There is a free version of Docker Community Edition (CE) and Enterprise Edition (EE).
For an example I’ll install the Docker CE in Ubuntu 16.04 LTS (Xenial).
Remove the old versions of Docker, if they are installed:
sudo apt-get remove docker docker-engine docker.io
Add the official GPG key Docker and make sure that the last command will show 9DC8 5822 9FC7 DD38 854A E2D8 8D81 803C 0EBF CD88:
sudo apt-get update sudo apt-get install apt-transport-https ca-certificates curl software-properties-common curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add - sudo apt-key fingerprint 0EBFCD88
Now you need to add a stable Docker repository:
sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
And run the installation from it:
sudo apt-get update sudo apt-get install docker-ce
If you need to install a specific version, you can specify:
apt-cache madison docker-ce sudo apt-get install docker-ce=18.03.0.ce
But when the system is updated, the update to the latest will be performed.
After installation, Docker will be automatically started, we will be convinced of it:
sudo docker run hello-world
To uninstall Docker CE with all data, you must:
sudo apt-get purge docker-ce sudo rm -rf /var/lib/docker
oVirt — virtualization management system.
On the test, I will install oVirt in CentOS 7.
First of all, let’s add an official repository:
yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release42.rpm
Update the packages:
It is desirable to reboot the system if the kernel was updated:
Install the oVirt Engine and all dependencies:
yum install ovirt-engine
This completes the installation of the oVirt Engine and you can proceed to setup by following the on-screen instructions:
By the end of the configuration, access information will be displayed and the oVirt panel can be opened in the browser https://example.com/ovirt-engine.
Proxmox – an open source virtualization system based on the Debian operating system.
On the test, I will install Proxmox in Debian 9.
Switch to the root user:
Open the /etc/hosts file in a text editor:
Suppose the server has one network card and in network connections it can be seen as “Ethernet”, but after adding the Hyper-V role, a virtual switch vEthernet (…) is created.
Virtual machines can be seen from other computers but can not be seen from the local.
Therefore, for virtual machines to be accessible from the local machine, you must disable the DHCP client to Ethernet, or assign an IP address manually, then the virtual switch vEthernet (…) will receive IP instead of Ethernet because they have the same The MAC address.
I noticed once in VirtualBox when starting a virtual machine the following error:
Interface (‘VirtualBox Host-Only Ethernet Adapter’) is not a Host-Only Adapter interface (VERR_INTERNAL_ERROR).
As it turned out in the device manager of the system and in network connections for some reason, the network interface disappeared “VirtualBox Host-Only Network”
For this, the easiest and fastest solution to an error will be to update or reinstall VirtualBox, virtual machines and settings will remain thereafter.
And also in the virtual machine, at which start there was an error, nano to specify the same network parameters.