Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 27 Mar 2015 08:58:57 -0600 (MDT)
From:      Warren Block <wblock@wonkity.com>
To:        Ivo Karabojkov <karabojkov@kit.bg>
Cc:        freebsd-emulation@freebsd.org
Subject:   Re: Troubles with VirtualBox 4.3.26
Message-ID:  <alpine.BSF.2.20.1503270849300.75841@wonkity.com>
In-Reply-To: <55150605.9030202@kit.bg>
References:  <alpine.BSF.2.20.1503260925520.29894@wonkity.com> <20150326140429.77be3c5f@Papi> <55150605.9030202@kit.bg>

next in thread | previous in thread | raw e-mail | index | archive | help
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 <vmname>
>
> 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.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1503270849300.75841>