Virtualbox doesn't work after cpu upgrade

  • Hi,


    I upgraded my A4-4000 to an A10-6800k and now I get this error:


    Code
    VirtualBox error: rc=0x80070005 The object functionality is limited (0x80070005)


    Details:

    Code
    Fehler #0:SoapFault exception: [SOAP-ENV:Client] VirtualBox error: rc=0x80070005 The object functionality is limited (0x80070005) in /usr/share/phpvirtualbox/endpoints/lib/vboxServiceWrappers.php:2728Stack trace:#0 /usr/share/phpvirtualbox/endpoints/lib/vboxServiceWrappers.php(2728): SoapClient->__soapCall('IMachine_getNam...', Array)#1 /usr/share/phpvirtualbox/endpoints/lib/vboxServiceWrappers.php(54): IMachine->getName()#2 /usr/share/openmediavault/engined/rpc/virtualbox.inc(141): VBox_ManagedObject->__get('name')#3 [internal function]: OMV\Engined\Rpc\VirtualBox->getMachines(Array, Array)#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array)#5 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('getMachines', Array, Array)#6 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('VirtualBox', 'getMachines', Array, Array, 1)#7 {main}


    Code
    sudo service virtualbox status
    ● virtualbox.service - LSB: VirtualBox Linux kernel module
       Loaded: loaded (/etc/init.d/virtualbox)
       Active: active (exited) since Sa 2017-10-28 14:35:41 CEST; 3min 3s ago
    
    
    
    
    Okt 28 14:35:41 Fileserver virtualbox[14079]: Loading VirtualBox kernel modules... vboxdrv vboxnetflt vboxnetadp vboxpci.
    Okt 28 14:35:41 Fileserver systemd[1]: Started LSB: VirtualBox Linux kernel module.


    Andy ideas?

  • regarding to cat /proc/cpuinfo svm is working and the kvm modprobe is loaded.


    Edit: I changed a HDD in my mergerfs-pool, too. Maybe this is the problem? The permissions should be correct (vbox and vboxusers). But even if I create a new shared folder I get this error.

  • Does the box work again when you put back your old CPU? Normally I would not expect a CPU change to cause this kind of issue unless the instruction set support was different between the CPUs.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!