From owner-freebsd-emulation@freebsd.org Sun Jul 24 11:20:27 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 013A0BA32A8 for ; Sun, 24 Jul 2016 11:20:27 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C7A33199A; Sun, 24 Jul 2016 11:20:26 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.15.2/8.15.2) with ESMTPS id u6OBKP5w065144 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 24 Jul 2016 05:20:25 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id u6OBKPe6065141; Sun, 24 Jul 2016 05:20:25 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sun, 24 Jul 2016 05:20:25 -0600 (MDT) From: Warren Block To: Gary Palmer cc: freebsd-emulation@FreeBSD.org Subject: Re: Upgrading to VirtualBox 5 In-Reply-To: <20160724104552.GD70150@in-addr.com> Message-ID: References: <20160724104552.GD70150@in-addr.com> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sun, 24 Jul 2016 05:20:25 -0600 (MDT) 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 11:20:27 -0000 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 >