From owner-freebsd-emulation@FreeBSD.ORG Fri Mar 27 14:59:01 2015 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4B0E3FDF for ; Fri, 27 Mar 2015 14:59:01 +0000 (UTC) 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 EB3D4FAC for ; Fri, 27 Mar 2015 14:59:00 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.9/8.14.9) with ESMTP id t2REwvdE080365 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 27 Mar 2015 08:58:58 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.9/8.14.9/Submit) with ESMTP id t2REwvDf080362; Fri, 27 Mar 2015 08:58:57 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Fri, 27 Mar 2015 08:58:57 -0600 (MDT) From: Warren Block To: Ivo Karabojkov Subject: Re: Troubles with VirtualBox 4.3.26 In-Reply-To: <55150605.9030202@kit.bg> Message-ID: References: <20150326140429.77be3c5f@Papi> <55150605.9030202@kit.bg> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Fri, 27 Mar 2015 08:58:58 -0600 (MDT) Cc: freebsd-emulation@freebsd.org X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.18-1 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: Fri, 27 Mar 2015 14:59:01 -0000 On Fri, 27 Mar 2015, Ivo Karabojkov wrote: > I usually use VirtualBox with VNC and webservice on headless servers. > I noticed that after any update if the VMs are not turned off but with > saved state the new version of VirtualBox is unable to start them and > the process terminates with an error. To start the VMs you should > discard their states by running (as vboxusers if this is the user who > runs VirtualBox services): > > VBoxManage discardstate > > This is always necesarry in my case after almost any update of VirtualBox My VMs were all shut down before the upgrade. At this point, I have tried multiple versions of the operating system, rebuilding everything VirtualBox depends on, removing CPUTYPE from make.conf, and twm rather than xfce. The problem has not changed, though.