Installing Guest Additions for VirtualBox on a Ubuntu node

-


When working with VirutalBox it is quite helpful to have the VirtualBox guest additions installed.

The main reason for us to have this would be to blow up the VM we are working on to full screen.


Assuming that you have already launched the VirtualBox and firedup the VM we going to work on


1. Open a terminal on the VM.
2. Just so that everything is uptodate

sudo apt-get update

3. Followed by

sudo apt-get install build-essential module-assistant

4. To Configure the system for building kernel modules 

sudo m-a prepare

5. On the VirutalBox menu Click on Devices  >> Install Guest Additions which is at the bottom of the menu.

6. We switch over to the CD.
cd /media

7. Using "ls" find the contents of the CD and swtich to it.
cd VOBXADDITIONS_4.3.6...

8. finally running 

sudo ./VBoxLinuxAdditions.run

You would need to restart the VM to get these changes effective sometimes. 

shutdown -r now


And now we can see that on Full Screen, the VM blows up fully!


Popular posts from this blog

Ansible - Error - stderr: E: There are problems and -y was used without --force-yes

-
Image
In case your tasks is to install some packages and it errors out as below - name: Install linux-headers apt: pkg={{item}} state=installed install_recommends=yes update_cache=yes with_items: - linux-headers-generic - dkms sudo: yes failed: [parallelsUbuntu] => (item=linux-headers-generic,dkms) => {"failed": true, "item": "linux-headers-generic,dkms"} stderr: E: There are problems and -y was used without --force-yes stdout: Reading package lists... Building dependency tree... Reading state information... The following extra packages will be installed:   cpp fakeroot gcc libfakeroot linux-headers-3.13.0-63   linux-headers-3.13.0-63-generic patch Suggested packages:   cpp-doc dpkg-dev debhelper gcc-multilib manpages-dev autoconf automake1.9   libtool flex bison gdb gcc-doc diffutils-doc The following NEW packages will be installed:   cpp dkms fakeroot gcc libfakeroot linux-headers-3
Read more

Error: SMTPIN_ADDED_BROKEN@mx.google.com

-
Some times we see the below in the email header information. SMTPIN_ADDED_BROKEN@mx.google.com The cause of the "...SMTPIN_ADDED_BROKEN@mx.google.com" is because of the 'https://' in the original Message-ID, which is not allowed. There could be some dodo systems which might be doing this and they would need to be tweaked to now allow message-id (see my earlier posts on what it means) and to have https!
Read more