From owner-freebsd-emulation@FreeBSD.ORG Fri Mar 27 15:18:17 2015 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 48D7A870 for ; Fri, 27 Mar 2015 15:18:17 +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 EA875258 for ; Fri, 27 Mar 2015 15:18:16 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.9/8.14.9) with ESMTP id t2RFIF4b085113 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 27 Mar 2015 09:18:15 -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 t2RFIFdj085110; Fri, 27 Mar 2015 09:18:15 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Fri, 27 Mar 2015 09:18:15 -0600 (MDT) From: Warren Block To: Ivo Karabojkov Subject: Re: Troubles with VirtualBox 4.3.26 In-Reply-To: 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; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Fri, 27 Mar 2015 09:18:15 -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 15:18:17 -0000 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 >> >> 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.