From owner-freebsd-emulation@freebsd.org Sun Jul 24 10:45:55 2016 Return-Path: Delivered-To: freebsd-emulation@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 021C7BA17E2 for ; Sun, 24 Jul 2016 10:45:55 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C4DB11ADC for ; Sun, 24 Jul 2016 10:45:54 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1bRGuu-000Frq-As; Sun, 24 Jul 2016 11:45:52 +0100 Date: Sun, 24 Jul 2016 11:45:52 +0100 From: Gary Palmer To: Warren Block Cc: freebsd-emulation@FreeBSD.org Subject: Re: Upgrading to VirtualBox 5 Message-ID: <20160724104552.GD70150@in-addr.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jul 2016 10:45:55 -0000 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 > 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. > After getting the new kernel module loaded, update the Guest Additions > in the VMs. Thanks, Gary