Troubles with VirtualBox 4.3.26
Warren Block
wblock at wonkity.com
Fri Mar 27 15:18:17 UTC 2015
On Fri, 27 Mar 2015, Warren Block wrote:
> 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.
A diff between the truss output of a failed session of 'VBoxManage list
vms' and a working one shows that the problems start here:
connect(5,{ AF_UNIX "/tmp/.vbox-wblock-ipc/ipcd" },106) ERR#61 'Connection refused'
When the command works:
connect(5,{ AF_UNIX "/tmp/.vbox-wblock-ipc/ipcd" },106) = 0 (0x0)
In a new terminal window, 'VBoxManage list vms' fails the first three
times, then works. After that, it usually works again in that same
terminal. It still can't start a VM.
More information about the freebsd-emulation
mailing list