[SOLVED]: /sbin/mount.vboxsf mounting failed with the error protocol error ubuntu

1. It had never happened in recent past and every time I used to mount the share folder for the guest OS in virtual box it used to happen vide this command :

sudo mount.vboxsf sharedfolder /mnt/foldername

where sharedfolder is the new folder you have created inside guest OS home directory in virtual box ~ ie /home to be mounted with another folder from host OS as foldername here

but today it showed an error with the following message :

/sbin/mount.vboxsf mounting failed with the error protocol error

as seen below :

tried everything around with the commands but didn't get resolved before I attempted to do the more simpler thing of going to the pwd of the folder where I created it to be mounted and typed the same command without path

surprisingly it worked!!!!

FEDORA 17 & VIRTUAL BOX : Virtualbox Installs but won't load

1.   This particular problem kept me busy the whole day....and in fact I reached a point of frustration that I should switch back to Ubuntu that I was earlier using.......so the problem goes like when I install virtual box via the rps and yum commands ...I used to invariably get some odd message that mostly included the following :

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 reinstall the kernel module by executing

'/etc/init.d/vboxdrv setup'

2.    I would not actually lie about it...but i checked about so many forums that gave relatively the same solutions that you would have mostly found out by now...but to no avail...so the two command simple solution that would make you VB run like a horse without any issues goes like this :

yum install dkms binutils gcc make patch libgomp glibc-headers glibc-devel kernel-headers kernel-PAE-devel

/etc/init.d/vboxdrv setup

offcourse you have to run this as a su -

3.   Do let me know if u r stuck on this again...the sets of commands that I run since morning as root are produced below for info only.BUt I am sure the commands above would solve your problem.

   21  wget http://download.virtualbox.org/virtualbox/rpm/fedora/virtualbox.repo

   22  yum update

   23  rpm -qa kernel |sort |tail -n 1

   24  uname -r

   25  reboot

   26  rpm -Uvh http://dl.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm

   27  pwd

   28  cd /etc/init.d/

   29  ls

   30  cd vboxdrv

   31  /etc/init.d/vboxdrv setup

   32  cd /var/log/

   33  more vbox-install.log 

   34  cd /etc/yum.repos.d/

   35  wget http://download.virtualbox.org/virtualbox/rpm/fedora/virtualbox.repo

   36  yum update

   37  yum install binutils qt gcc make patch libgomp glibc-headers glibc-devel kernel-headers kernel-devel      

   dkms   

   38  yum install VirtualBox-4.2                                                                                  

   39  virtualbox                                                                                                  

   40  KERN_DIR=/usr/src/kernels/2.6.18-194.11.1.el5-x86_64                                                        

   41  export KERN_DIR                                                                                             

   42  yum update virtualbox-4.2                                                                                   

   43  aptitude update                                                                                             

   44  yum install dkms gcc                                                                                        

   45  yum install kernel-headers kernel-devel                                                                     

   46  /etc/init.d/vboxdrv setup                                                                                   

   47  more /var/log/vbox-install.log                                                                                                                                                                    

   49  wget http://download.virtualbox.org/virtualbox/rpm/fedora/virtualbox.repo                                   

   50  uname -r                                                                                                                                                                             

   53  rpm -qa kernel |sort |tail -n 1                                                                             

   54  uname -r

   55  service vboxdrv setup

   56  uname -r

   57  KERN_DIR=/usr/src/kernels/3.6.6-1.fc17.i686.PAE

   58  export KERN_DIR

   59  virtualbox

   60  usermod -a -G vboxusers duqu

   61  virtualbox

   62  apt-get install dkms

   63  wget install dkms

   64  uname -r

   65  rpm -q kernel-devel

   66  uname -r

   67  virtualbox

   68  /etc/init.d/vboxdrv setup

   69  more /var/log/vbox-install.log

   70  KERN_DIR=/usr/src/kernels/3.6.6-1.fc17.i686.PAE

   71  export KERN_DIR

   72  virtualbox

   73  /etc/init.d/vboxdrv setup

   74  uname -r

   75  yum install kernel-headers-3.6.6-1.fc17.i686.PAE

   76  exit

   77  yum install kernel-headers gcc

   78  /etc/init.d/vboxdrv setup

   79  exit

   81  yum install dkms binutils gcc make patch libgomp glibc-headers glibc-devel kernel-headers kernel-   

   PAE-devel

   82  /etc/init.d/vboxdrv setup

VIRTUAL BOX : SOLVED - FAILED TO OPEN HARD DISK ISSUE

1. I had been an avid follower of VMWARE until recently wherein I have shifted my loyalties to VIRTUAL BOX....simple,easy....and the best part is that it is OPENSOURCE.One problem that I often used to face was that when I copied a VDI file from one place to another...it used to give me a message as shown in the screen shot below that said something like " Failed to open the hardddisk F:\....\.....vdi.So I used to keep trying ways and means but that remained unsolved.But there is a single command line solution to this that goes like this...(also shown in the screen shot).Goto the command prompt first as administrator.

Goto the folder C:\Program Files\Oracle\VirtualBox by typing

c:\>cd C:\Program Files\Oracle\VirtualBox

and then type

C:\Program Files\Oracle\VirtualBox>VBoxManage.exe internalcommands sethduuid "h:\path to the vdi folder\yourvdifilename.vdi"

and this should give a message similar to this 

UUID changed to: 3cfa288c-9e91-42e2-acdc-9821ab9d4aab

(CLICK ON IMAGE TO ENLARGE)

thats it...now open...u should not get the message!!!

Installing Guest Additions in Virtual Box : RHEL 5

1.  In variably I have been using various window OS trials for experimenting in Virtual Box....and yes it is easy to use....but try it out with an RHEL 5.....it became a small fight for me at least.....how i solved it goes like this...

(a) First tried with this :

./VBoxLinuxAdditions-x86.run 

and i was given this error message :

bash: ./VBoxLinuxAdditions-x86.run: /bin/sh: bad interpreter: Permission denied

(b)....the answer is actually this :

sh VBoxLinuxAdditions-x86.run 
or 
bash VBoxLinuxAdditions-x86.run

and the output looks something like this

[root@localhost VBoxGuestAdditions_4.1.8_75467]# ./VBoxLinuxAdditions.run
Verifying archive integrity... All good.
Uncompressing VirtualBox 4.1.8 Guest Additions for Linux.........
VirtualBox Guest Additions installer
Removing installed version 4.1.6 of VirtualBox Guest Additions...
Removing existing VirtualBox DKMS kernel modules           [  OK  ]
Removing existing VirtualBox non-DKMS kernel modules       [  OK  ]
Building the VirtualBox Guest Additions kernel modules
Building the main Guest Additions module                   [  OK  ]
Building the shared folder support module                  [  OK  ]
Building the OpenGL support module                         [  OK  ]
Doing non-kernel setup of the Guest Additions              [  OK  ]
You may need to restart the hal service and the Window system
Installing the Window System drivers
Installing X.Org Server 1.11 modules                       [  OK  ]
Setting up the Window System to use the Guest Additions    [  OK  ]
You may need to restart the hal service and the Window System (or just restart
the guest system) to enable the Guest Additions.
Installing graphics libraries and desktop services componen[  OK  ]

...thats it!!!!!!!!!!!!!

CHROME INSTALLATION ISSUES IN UBUNTU : SOLVED

1. Recently tried installing Chrome browser in Ubuntu 11.10....so I downloaded the .deb file and tried installing it from the terminal via this command

sudo dpkg -i './Downloads/google-chrome-stable_current_i386.deb'

...which showed some error in between installation and came out on the terminal prompt....

2. So googled and found this solution that involves prior installing of few library files as follows :

sudo apt-get install libnspr4-0d libnss3-1d libxss1 libcurl3

this command will install the missing lib files and then on it is the repeat of the earlier command ie

sudo dpkg -i './Downloads/google-chrome-stable_current_i386.deb'

3.   Should solve...let me know if u have any thing unsolved!!!

Intel® Core™ i3 Processor & Server 2003

1. Strange are the ways sometimes when we get troubled by the PC.In an attempt to upgrade one of the PCs to Intel® Core™ i3 Processor,I found a problem I never thought of.

2. Now just to give u a small brief,I have a small office complex with about 15 computers on Server 2003 which was running fine till one day when i just decided to upgrade my server machine to Intel® Core™ i3 Processor.I bought the combo pack of this processor with its motherboard for about 11k,i assembled it and started with the setup of server 2003.....started nicely but this would never install completly in my 'N' number of attempts and would hang halfways.....then i thought like Murphy is acting fine with me and their is some problem with the processor motherboard hardware...so replaced the same pack with a new one..but the problem persisted....i contacted the local dealer,surprised with the problem he himself attempted the same but met with the same end.....

3. I changed my installation CDs ,still met with the same problem...finally I could arrive that there may be some compatibility issue between server 2003 & Intel® Core™ i3 Processor.........and reverted back to core 2 duo,the earlier one.

4. I would request readers to augment their comments, if any, with such a problem being faced anywhere else.