On Sun, 24 Jul 2016, Gary Palmer wrote:
On Sun, Jul 24, 2016 at 04:12:08AM -0600, Warren Block wrote:
Before upgrading to the new VirtualBox 5 port, check UPDATING and back
up existing VMs.
Generic advice or has something been added? I just checked and
could not find any virtualbox 5 related news
Just generic. The post started out as a request for help with a list of
what had been tried, then I realized the issue and thought it might be
helpful to others.
Attempting to run an old VM without unloading the old VirtualBox kernel
module (vboxdrv) and loading the new version produces this error:
RTR3InitEx failed with rc=-1912(rc=-1912)
where: supR3HardenedMainInitRuntime what: 4
VERR_VM_DRIVER_VERSION_MISMATCH (-1912) - The installed
support driver doesn't match the version of the user.
'kldunload vboxdrv && kldload vboxdrv' *should* work, but the error
might prevent that and require a reboot to load the new version.
Before doing the upgrade it would probably be best to run
service vboxheadless stop ; service vboxnet stop ; service vboxwatchdog stop ;
service vboxwebsrv stop
That should unload the vbox 4 kernel modules. Check with kldstat and try
to manually unload any remaining modules prior to trying vbox 5.
Agreed.
After getting the new kernel module loaded, update the Guest Additions
in the VMs.
Thanks,
Gary
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "[email protected]"
