Today I have tried to Install Virtualbox 5.0.x on my Newly Installed Fedora 24. I expected it to run smoothly as expected but It failed in kernel module compilation with following error
(modprobe vboxdrv failed. Please use 'dmesg' to find out why)
Then After I tried to reload module again with command sudo modprobe vboxdrv and failed again with following error
modprobe: ERROR: could not insert 'vboxdrv': Required key not available
Second try hinted me that there is nothing wrong in VirtualBox but something related to “key”, So I tried to search for a solution and landed to Official VirtualBox ticket which confirmed the same https://www.virtualbox.org/ticket/11577
Now I have tried find the way to Sign the key and received many links and started following Red Hat link to sign Module, Never thought it would be this much easy, Only Few steps and You are done.
- You will need root access or root equivalent access to follow this.
- First you will have to generate keys for the module with following command
[root@tejasbarot ~]# openssl req -new -x509 -newkey rsa:2048 -keyout tejasbarot.keyout -outform DER -out tejasbarot.der -nodes -days 36500 -subj "/CN=TejasBarot/"
Notes: CN=<Common-Name>, You can write your own name too, Cool ?
MOK stands for Module Owned Key
- Now Time to Import module in MOKManager of UEFI with Following Command:
[root@tejasbarot ~]# mokutil --import tejasbarot.der
Note: It will prompt you password, Make sure you remember password you enter here, You will need to enter the same password at time importing module on reboot.
- Now Reboot / Restsart your Fedora 24 Box.
- It will display MOK Screen, Press any key within TEN SECONDS else It will boot without MOK Module.
- Select “Enroll MOK”
- Click on “View Key 0″ to View Key Information, Click on “Continue” to proceed.
- In Next Screen, Click on “Next” to Enroll Keys.
- In next screen, It will ask you for a password which you have entered at time of importing MOK (In step 3)
- Now Click on OK to reboot.
- Now time to sign VirtualBox Modules with key generated in Step 2. Execute Following commands
[root@tejasbarot ~]# /usr/src/kernels/$(uname -r)/scripts/sign-file sha256 ./tejasbarot.keyout ./tejasbarot.der $(modinfo -n vboxdrv)
[root@tejasbarot ~]# /usr/src/kernels/$(uname -r)/scripts/sign-file sha256 ./tejasbarot.keyout ./tejasbarot.der $(modinfo -n vboxnetflt)
[root@tejasbarot ~]# /usr/src/kernels/$(uname -r)/scripts/sign-file sha256 ./tejasbarot.keyout ./tejasbarot.der $(modinfo -n vboxnetadp)
[root@tejasbarot ~]# /usr/src/kernels/$(uname -r)/scripts/sign-file sha256 ./tejasbarot.keyout ./tejasbarot.der $(modinfo -n vboxpci)
1. To make it work Properly, You will have to sign all modules of VirtualBox with generated keys.
2. Everytime you run “/sbin/rcvboxdrv setup” after following step 3, Signed Modules will be removed and You will again need to follow Step 11 and 12 , Only step 11 and 12 not from beginning. (This was not the case in Fedora 18 to 21)
- Restart vboxdrv service with following command
[root@tejasbarot ~]# systemctl restart vboxdrv
[root@tejasbarot ~]# systemctl status vboxdrv
NOTE: If you find this line “Starting VirtualBox kernel modules [ OK ]”, You are done, Start launching Virtual Machines.
REPEATING ONCE AGAIN, DO NOT EXECUTE “sudo /etc/init.d/vboxdrv setup” or “/sbin/rcvboxdrv setup” otherwise you will have to follow repeat Step No 11. and 12
DISABLE MOK Validation using following command
[root@tejasbarot ~]# mokutil --disable-validation
Switch to Legacy Mode from UEFI by Disabling SecureBoot from BIOS
References taken from :
Like and Share All Linux User’s Blog Facebook Page: https://www.FaceBook.com/AllLinuxUsersBlog
I have written article and posts on Linux Fundamentals as well as Many articles on different different Linux Tools, Linux Services, Linux flavors. Time has now come to move to Advance tools, This is an era of Infrastructure automation, DevOps.
I will continue to write on Linux, Now Next Target is to write on DevOps tools like
Jenkins – Continuous Integration (CI) and Continuous Delivery (CD)
Ansible, Chef, Puppet – Infrastructure Automation
GIT, SVN – Source Code Management
Docker – Automates the deployment of applications inside software containers
OpenStack – Cloud Software
Amazon Web Services – Public Cloud
Subscribe yourself for Blog updates here: http://eepurl.com/basgDz
I would request you to keep visiting blog for this upcoming posts, Hope this will help you in future.
Note: All logos, trademarks and registered trademarks are the property of their respective owners.
As you all know, It is very easy to change Time Zone using Graphical Interface but this article will help you change TimeZone Using command line.
I have tested these steps on CentOS / RHEL and Ubuntu, Please comment down below if doesn’t work for you.
Please follow these steps as root or with root equivalent sudo rights:
- Check Time Zone using following command
[root@tejas-barot-linux-ahmedabad ~]# date
- First Remove symbolic link of current time zone
[root@tejas-barot-linux-ahmedabad ~]# rm /etc/localtime
- Let’s Change the Time Zone from Command line
[root@tejas-barot-linux-ahmedabad ~]# ln -sf /usr/share/zoneinfo/Asia/Kolkata /etc/localtime
Note : You can find your time zone under /usr/share/zoneinfo/
First of all extremely sorry for not being active as I was busy with some work, Now back to the blogging.
This article will show you how to disable rsyslog rate-limiting, But You can also use rate-limiting according to your requirement.
This article is tested with rsyslog 5.7.1 on Fedora 13. It will not work with version of rsyslog prior to 5.7.1.
In rsyslog 5.7.1 we introduced rate limiting. This is a option for the Unix Socket Input module called imuxsock. In short, this option limits the amount of messages written into logfiles by a process, if the process tries to write huge amounts of messages in a short period of time.
To Read more Visit : http://www.rsyslog.com/tag/rate-limiting/
If you are receiving error messages like below in /var/log/messages
imuxsock begins to drop messages from pid 5923 due to rate-limiting
Please following below method to stop / disable rate-limiting in rsyslog in version 5.
Note: rsyslog version 7 has this disabled by default but rsyslog version 5 has this enabled.
To disable it, add following parameters to your /etc/rsyslog.conf , You need to add with root user or root equivalent user.
Execute following command to restart rsyslog services
service rsyslog restart
Fedora 22 released few days back and now available for download, Sorry for delay in posting of download links, You can download using following Links.
Note: Fedora 22 will be using now DNF instead of YUM, YUM IS DEAD !
Fedora 22 Download
Download Fedora 22 Workstation 64-Bit Live Image (x86_64): http://download.fedoraproject.org/pub/fedora/linux/releases/22/Workstation/x86_64/iso/Fedora-Live-Workstation-x86_64-22-3.iso
Download Fedora 22 Workstation 32-Bit Live Image (i386): http://download.fedoraproject.org/pub/fedora/linux/releases/22/Workstation/i386/iso/Fedora-Live-Workstation-i686-22-3.iso
Download Fedora 22 Server 64-Bit Installation Image (x86_64): http://download.fedoraproject.org/pub/fedora/linux/releases/22/Server/x86_64/iso/Fedora-Server-DVD-x86_64-22.iso
Download Fedora 22 Server 32-Bit Installation Image (x86_64): http://download.fedoraproject.org/pub/fedora/linux/releases/22/Server/i386/iso/Fedora-Server-DVD-i386-22.iso
Download Fedora 22 Cloud Images : https://getfedora.org/en/cloud/download/
As systemd is already implemented in CentOS 7 and RHEL 7, Method has been changed to change runlevel in Red Hat Enterprise Linux and CentOS 7. So sharing method to change runlevel in CentOS and RHEL 7
CentOS / RHEL 7
Please perform following simple steps to change runlevel from GUI to NON-GUI and NON-GUI to GUI.
1. Execute following command to check current runlevel settings.
[root@tejasbarot ~]# systemctl get-default
1.1 If current setting is graphical.target then Linux will boot in GUI Mode.
1.2 If current setting is multi-user.target then Linux will boot in NON-GUI Mode.
2. Execute following command to Change from GUI to NON-GUI Mode.
[root@tejasbarot ~]# systemctl set-default multi-user.target
[root@tejasbarot ~]# reboot
3. Execute following command to Change from NON-GUI to GUI Mode.
[root@tejasbarot ~]# systemctl set-default graphical.target
[root@tejasbarot ~]# reboot
Hope it will helps you.
Enjoy Linux 🙂 Enjoy Open Source 🙂
If you like this then Please Click Google +1 Button and Show Your Support. Your Support will encourage me to write more articles.
Please Keep in Touch with Social Networking :-
Facebook Page :- https://www.facebook.com/AllLinuxUsersBlog