You are not logged in.
Pages: 1
Failed to start the virtual machine WindowsXP
The VirtualBox support driver which is running is from a different version of VirtualBox. You can correct this by stopping all running instances of VirtualBox and reinstalling the software..
VBox status code: -1912 (VERR_VM_DRIVER_VERSION_MISMATCH).
Result Code:
0x80004005
Component:
Console
Interface:
IConsole {d5a1cbda-f5d7-4824-9afe-d640c94c7dcf}i try to do what it says. offcourse with backing up all the Virtualbox folder before. i did pacman -R virtualbox-ose virtualbox-modules virtualbox-additions
and then i went to /var/cache/pacman/pkg/ and install the previous installation first 1.5.6-1 and then did the same with the newest one. nothing.
what must i do to get this thing work?
thank you in advanced
Offline
Might want to try grabbing the virtualbox-modules ABS package build and just rebuilding the package yourself that way it will build against your current kernel.
Offline
Might want to try grabbing the virtualbox-modules ABS package build and just rebuilding the package yourself that way it will build against your current kernel.
how do you suggest to do that?
Offline
Read this... http://wiki.archlinux.org/index.php/ABS
then copy the virtualbox-modules dir to somewhere you have write permissions, run makepkg on it and pacman -U the resulting package.
Offline
lol....this is funny sometimes... yes ok it was my fault... but i thought that it didnt need to... i just restart the pc and now (after adding again the user to virtualboxusers) it works gr8. ty for the fast support. Q: y did this had to happened?
Offline
I think the issue was that the vboxdrv module that was loaded in ram was from the previous version. Then when you upgraded Virtualbox and tried to run it.. there was a version mismatch because the old kernel module was still loaded. A reboot would have solved this issue, as it did.
to avoid the restart you could have also done
rmmod vboxdrv
modprobe vboxdrv
Offline
I think the issue was that the vboxdrv module that was loaded in ram was from the previous version. Then when you upgraded Virtualbox and tried to run it.. there was a version mismatch because the old kernel module was still loaded. A reboot would have solved this issue, as it did.
to avoid the restart you could have also done
rmmod vboxdrv
modprobe vboxdrv
ok ty for your time and the info.
Offline
Pages: 1