Sign up ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I'm running VirtualBox 4.2 and it keeps telling me that 4.3 is available for update. However when I do apt-get update and the apt-get upgrade I don't get any updates.

My sources.list contains deb oneiric contrib. I can't remember why it has oneiric instead of wheezy, but changing that doesn't make any difference.

share|improve this question

1 Answer 1

up vote 1 down vote accepted

The repository efectivelly has the 4.3 version (download) but has another name of package, namely virtualbox-4.3. So what to do to "upgrade":

sudo apt-get remove virtualbox-4.2 virtualbox
sudo apt-get install virtualbox-4.3

Done. Also, you must remember that virtualbox is built with different libraries for both distribuitions, so they are not quite the same packages, as you can see:

Package: virtualbox-4.3
Version: 4.3.4-91027~Ubuntu~quantal
Filename: pool/contrib/v/virtualbox-4.3/virtualbox-4.3_4.3.4-91027~Ubuntu~quantal_amd64.deb
Size: 68442970
SHA256: a2e48468e258d0ae8d66438b8ee1a7f7f6d517f582960546ab26f952da8ceb85
SHA1: 86c7a9fc299cc5439b5a1728ac7398bb464b8ce6
MD5sum: e84b87f9db7f72e01d8904b835772e35
Python-Version: 2.7
Package: virtualbox-4.3
Version: 4.3.4-91027~Debian~wheezy
Filename: pool/contrib/v/virtualbox-4.3/virtualbox-4.3_4.3.4-91027~Debian~wheezy_amd64.deb
Size: 69487026
SHA256: e0780dca1c2a2f6b58703c4684b55c72ea08ea12574d7025b726d44233c35a88
SHA1: 7c5816d13fdf1215c2718cf2c347b0123ad08440
MD5sum: 2f422df0c8dd9105342d7a335ebe0109
Python-Version: 2.6, 2.7
share|improve this answer
This may seem like a dumb question, but is it safe to remove 4.2 and then install 4.3? I mean, I have quite few virtual machines each with different config and It would be a pain to recreate that manually :) – SiliconMind Dec 13 '13 at 20:52
@SiliconMind Depends what VB has done between 4.2 and 4.3, but there should be no problem. – Braiam Dec 13 '13 at 21:28
Damn! After upgrade to 4.3 the bridged network stopped working :( – SiliconMind Jan 8 '14 at 9:45
This is weird ifconfig eth1 down and then ifconfig eth1 up in one of the guest systems solved the issue... for all other guests! – SiliconMind Jan 8 '14 at 11:20

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.