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 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.
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.
I noticed somehow an error in VirtualBox working on Linux Ubuntu Desktop 16.04:
Kernel driver not installed (rc=-1908)
The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please install virtualbox-dkms package and load the kernel module by executing
as root. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.
where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) – The support driver is not installed. On linux, open returned ENOENT.
To solve the problem it was necessary to disable the secure boot in the BIOS, in my case “Windows UEFI” was selected, changed to “Other OS”.
Then, after running the system, executed the command from the root user:
In Ubuntu, you can switch to root as follows:
Done, the error is solved.
After running the virtual system in VirtualBox, I noticed the following error:
This kernel requires the following features not present on the CPU:
Unable to boot – please use a kernel appropriate for your CPU.
The error can be solved in several ways:
Method 1) When you turn on the computer, go into the BIOS and enable the virtualization in the processor settings (if the processor supports it).
Method 2) After opening VirtualBox, we will go into the settings of the virtual system created, namely “Settings” – “System” – “CPU” and put a tick near “Additional Options: Enable PAE/NX“. Click “OK” to save changes.
Done, this error should not be displayed.