Virtual Box Problem

[elder73]

Recently I installed a Virtual Box on my Kubuntu 14.04 so that I can use Windows for a couple of programmes. This means that I have to install Windows XP as an extension pack. That is where the problem comes in, Windows shows up but I can't open it and It tells me that I need to install a DKMS package, followed by running etc/init.d/vboxdrv setup. So I did the following:

william78@william78:~$ sudo apt-get install dkms
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.

I've tried a number of dpkg commands all of which did not work. Any help would be appreciate.

[SteveRiley]

What's the output of

dpkg -l | grep -v ^ii

[elder73]

What's the output of

dpkg -l | grep -v ^ii

william78@william78:~$ dpkg -l | grep -v ^ii
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                                        Version                               Architecture Description
+++-===========================================-=====================================-============-===============================================================================
it  desktop-file-utils                          0.22-1ubuntu1                         amd64        Utilities for .desktop files
rc  gconf2                                      3.2.6-0ubuntu2                        amd64        GNOME configuration database system (support tools)
it  hicolor-icon-theme                          0.13-1                                all          default fallback theme for FreeDesktop.org icon themes
rc  libgnome2-0:amd64                           2.32.1-4ubuntu1                       amd64        The GNOME library - runtime files
rc  libgnome2-common                            2.32.1-4ubuntu1                       all          The GNOME library - common files
rc  libgnomevfs2-0:amd64                        1:2.24.4-1ubuntu6                     amd64        GNOME Virtual File System (runtime libraries)
rc  libgnomevfs2-common                         1:2.24.4-1ubuntu6                     amd64        GNOME Virtual File System (common files)
it  mime-support                                3.54ubuntu1                           all          MIME files 'mime.types' & 'mailcap', and support programs
it  shared-mime-info                            1.2-0ubuntu3                          amd64        FreeDesktop.org shared MIME database and spec
it  ureadahead                                  0.100.0-16                            amd64        Read required files in advance
iW  virtualbox-4.3                              4.3.20-96996~Ubuntu~raring            i386         Oracle VM VirtualBox
william78@william78:~$

Above is a copy on what I received. Thank you.

[SteveRiley]

There could be any number of reasons why you're having problems getting VirtualBox installed. Your output does show a few useful thigs, so let's get started.

Packages can be in one of five states and can have one of eight statuses. The first two characters in each row indicate the state and status of every package on the system. Fully installed packages are indicated as ii: installed state and installed status.

You have a few packages marked rc: they've been removed (state Remove) but some configuration files remain (status Conf-files). These aren't causing problems, but we might as well clean them off since we're here. This command will purge the left-over config files:

sudo apt-get purge $(dpkg -l | awk '/^rc/ {print $2}')

There are some other things we could do, but first: did you run the suggsted command, sudo dpkg --configure -a?

[kubicle]

One thing that leaps out is that you have downloaded and installed virtualbox deb for i386 machines, and you seem to be using an amd64 kernel.

That probably won't work causing virtualbox to be only "partially installed". I'd suggest removing virtualbox and getting the amd64 version.

[SteveRiley]

One thing that leaps out is that you have downloaded and installed virtualbox deb for i386 machines, and you seem to be using an amd64 kernel.

That probably won't work causing virtualbox to be only "partially installed". I'd suggest removing virtualbox and getting the amd64 version.

Good catch! I didn't even look at that column in the output, heh.

[elder73]

Good catch! I didn't even look at that column in the output, heh.

I wondered about all the amd64 notations as I thought my machine (a refurb) was Intel from the label on the front.
Having said that, is there a way of removing the Virtual Box that I have installed? Thank you.

[ronw]

The 'amd' in 'amd64' is just a label.

I'm guessing you grabbed the wrong deb file from the Virtualbox site since you have 4.3.20 installed (partially) and the Ubuntu repos are still at 4.3.18.

You can "$ sudo apt remove virtualbox-4.3", then either install from the Ubuntu repos, grab the 64-bit deb from Virtualbox, or follow the instructions on the Virtualbox downloads page to add their repo (that's what I do).

[SteveRiley]

follow the instructions on the Virtualbox downloads page to add their repo (that's what I do).

Same here. VirtualBox's repository is more up to date than Ubuntu's.

[elder73]

The 'amd' in 'amd64' is just a label.

I'm guessing you grabbed the wrong deb file from the Virtualbox site since you have 4.3.20 installed (partially) and the Ubuntu repos are still at 4.3.18.

You can "$ sudo apt remove virtualbox-4.3", then either install from the Ubuntu repos, grab the 64-bit deb from Virtualbox, or follow the instructions on the Virtualbox downloads page to add their repo (that's what I do).

Thank you for this and I have installed and uninstalled so many times I'm dizzy and I have no idea where I am or how to get out. Following is a synopsis:

Virtual Box:
file:///home/william78/Downloads/virtualbox-4.3_4.3.20-96996~Ubuntu~raring_amd64.deb

Windows XP:
file:///home/william78/Downloads/Windows_XP_Professional_SP3_Nov_2013_Incl_SATA_Dri vers.iso

william78@william78:~$ dpkg -l | grep -v ^ii
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===========================================-=====================================-============-================================================== =============================
rc gconf2 3.2.6-0ubuntu2 amd64 GNOME configuration database system (support tools)
rc libgnome2-0:amd64 2.32.1-4ubuntu1 amd64 The GNOME library - runtime files
rc libgnome2-common 2.32.1-4ubuntu1 all The GNOME library - common files
rc libgnomevfs2-0:amd64 1:2.24.4-1ubuntu6 amd64 GNOME Virtual File System (runtime libraries)
rc libgnomevfs2-common 1:2.24.4-1ubuntu6 amd64 GNOME Virtual File System (common files)
william78@william78:~$

Next:

william78@william78:~$ sudo apt-get install dkms
Reading package lists... Done
Building dependency tree
Reading state information... Done
dkms is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 419 not upgraded.

Next:

$ /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel modules ...done.
Uninstalling old VirtualBox DKMS kernel modules/etc/init.d/vboxdrv: 302: /etc/init.d/vboxdrv: cannot create /var/log/vbox-install.log: Permission denied
...done.
Removing old VirtualBox pci kernel module ...done.
Removing old VirtualBox netadp kernel module ...done.
Removing old VirtualBox netflt kernel module ...done.
Removing old VirtualBox kernel module ...done.
Trying to register the VirtualBox kernel modules using DKMS/etc/init.d/vboxdrv: 327: /etc/init.d/vboxdrv: cannot create /var/log/vbox-install.log: Permission denied
...failed!
(Failed, trying without DKMS)
Recompiling VirtualBox kernel modules/etc/init.d/vboxdrv: 334: /etc/init.d/vboxdrv: cannot create /var/log/vbox-install.log: Permission denied
...failed!
(Look at /var/log/vbox-install.log to find out what went wrong)

I opened the above log but it is one large page that I could make no sense of.

[anika200]

Try running the last command with sudo

$ sudo /etc/init.d/vboxdrv setup

You should not have to keep installing or un-installing anythings else at this point.
Also, please add yourself to the vboxusers group.

Something like

# sudo useradd -G vboxusers yourusernamehere

[ronw]

0 upgraded, 0 newly installed, 0 to remove and 419 not upgraded.

419 not upgraded?

You probably want to address this, then return to getting Virtualbox installed. I don't think I've ever seen that many packages needing an upgrade.

[elder73]

Try running the last command with sudo

$ sudo /etc/init.d/vboxdrv setup

You should not have to keep installing or un-installing anythings else at this point.
Also, please add yourself to the vboxusers group.

Something like

# sudo useradd -G vboxusers yourusernamehere

Did both of the above. The result on the firs one is:

$ sudo /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel modules ...done.
Uninstalling old VirtualBox DKMS kernel modules ...done.
Trying to register the VirtualBox kernel modules using DKMS ...done.
Starting VirtualBox kernel modules ...done.

Then I ran the Virtual Box again and got the following.

Attempting to load an x64 operating system, however this CPU is not compatible with x64 mode. Please install a 32-bit X86 operating system. Set up cannot continue. Press any key to exit.

Thank you.

[elder73]

419 not upgraded?

You probably want to address this, then return to getting Virtualbox installed. I don't think I've ever seen that many packages needing an upgrade.

What do I upgrade the Linux system?

[SteveRiley]

Hm. You're posting in the Trusty (11.04) forum, but the file name of the VirtualBox download includes "raring," which leads me to believe either it may be too old or your computer may not be running Trusty. We can help you get to your desired end state, but let's check a few things first. What's the output of:

lsb_release -a

uname -a

Also, those left-over config files are for 64-bit packages, sparking Kubicle's observation in post #5 that you have a 64-bit system and shouldn't be installing 32-bit binaries. However, the error message in your post #13 appears to indicate that you don't have a 64-bit system. So things look somewhat confusing for us at the moment.