VirtualBox --startvm should notify about a new ext-pack after upgrade

[Daniel Rocher]

Since last update (virtualbox (4.3.10-dfsg-1ubuntu5, 4.3.34-dfsg-1+deb8u1ubuntu1.14.04.1) Mis à niveau à 17:57),
Impossible to start VM's :

$/usr/lib/virtualbox/VirtualBox --startvm "cbf10a46-a9c5-428f-be75-6a9de87cb16a"
Erreur de segmentation

[Gianfranco Costamagna (costamagnagianfranco)]

mmm can you please try a gdb and to provide a stack trace?

also running apport-collect 1520656 can help,

thanks!

[Daniel Rocher (daniel-rocher)]

This is no longer possible for me, because :

step 1: I have upgraded to virtualbox version 5: works perfectly
step 2: I've downgraded to the version provided by Ubuntu (4.3.34) : works perfectly too ...

Sorry

[Gianfranco Costamagna (costamagnagianfranco)]

so maybe it was due to some sort of configuration issue, maybe a missing reboot?

[Daniel Rocher (daniel-rocher)]

reboot was done. Also tested :
sudo apt-get purge virtualbox virtualbox-dkms virtualbox-qt
sudo apt-get install virtualbox virtualbox-dkms virtualbox-qt && sudo reboot

I found this thread : http://askubuntu.com/questions/640308/after-upgrading-to-2015-04-virtualbox-crashes-at-windows-vm-start-nothing-in-l
     "To solve the problem and use your VM with USB2.0,
      what I did is to update the Oracle VM Virtualbox ExtensionPack
      to the same version: 4.3.34r104062"

Indeed, I had installed Virtualbox ExtensionPack to the same version: 4.3.34r104062 when I had downgraded Virtualbox (version 5.0 to 4.3.34).

Oddly :
 - version 5 of virtualbox informed me that the version 4.3.26 of the extensionPack was not correct -> I install extensionPack version 5
 - After downgraded, version 4.3.34 of virtualbox informed me that the version 5 of the extensionPack was not correct -> I Install ExtensionPack to the same version
 - But initially, when I had upgraded from 4.3.26 to 4.3.34, VirtualBox didn’t inform me that the Extension Pack 4.3.26 version is not correct. VM's Start ... and crash ...

I do not know if this bug should be closed. Perhaps this could happen to other people.
Thanks

[Robertspil (rcglider)]

I had a similar problem on a Xubuntu 14.04
- software update replaces VirtualBox with version 4.3.34 and all my VM machines crash
- reboot change nothing,when I reboot with 13.10 the VM machines run .

With Synaptic I see that the package virtualbox is at level 4.3.34 ( virtualbox, virtualbox-qt, virtalbox-dkms) but the guest-additions-iso is remained at 4.3.10.
If I start a VM machine with a guest-additions-iso 4.3.34...there is a crash. The crash report is sent.

Can I do something ?

Thanks

[Robertspil (rcglider)]

Continuation and problem solved:
- I searched the website of virtualbox for a extensionPack 4.3.34. I install this (he give the information that I have to replace a older package)
-the VM machines are now starting

For me the bug is closed , but it is evident that the procedure for th update to 4.3.34 is NOT correct. It has to replace the extensionPack.

Thaks (un grand merci !) daniel rocher

[Gianfranco Costamagna (costamagnagianfranco)]

the problem actually is that you don't run the graphical virtualbox (that asks to to update the ext-pack addon), but you run it from cmdline.

[Daniel Rocher (daniel-rocher)]

Hi,

I also launched the graphical virtualbox, and I had the same problem.

[Humphrey van Polanen Petel (hpvpp)]

How the upgrade is effected is irrelevant.

VirtualBox needs to validate itself and when it find a mismatch between its base and its extension, it should report that and terminate.

[Gianfranco Costamagna (costamagnagianfranco)]

True. Upstream is aware of the issue

[Gianfranco Costamagna (costamagnagianfranco)]

fixed in xenial upcoming 5.0.14