From owner-freebsd-emulation@FreeBSD.ORG Sat Feb 14 20:20:50 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 44A0332E for ; Sat, 14 Feb 2015 20:20:50 +0000 (UTC) Received: from mail1.isdefe.es (mail1.isdefe.es [194.15.213.239]) by mx1.freebsd.org (Postfix) with ESMTP id F308E12D for ; Sat, 14 Feb 2015 20:20:49 +0000 (UTC) Received: from turing.b2n.org (unknown [172.24.1.14]) by mail1.isdefe.es (Postfix) with ESMTP id 3678331A315 for ; Sat, 14 Feb 2015 21:19:28 +0100 (CET) Received: from tur1ng.pinlabs.b2n.org (localhost [127.0.0.1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by turing.b2n.org (Postfix) with ESMTPS id E74BB115F7C for ; Sat, 14 Feb 2015 21:20:47 +0100 (CET) Received: from ram-ws.pinlabs.b2n.org (ram-ws.pinlabs.b2n.org [10.10.10.15]) by turing.b2n.org (Horde Framework) with HTTP; Sat, 14 Feb 2015 21:20:47 +0100 Date: Sat, 14 Feb 2015 21:20:47 +0100 Message-ID: <20150214212047.Horde.yYcnQV20nC4yA66Iskx13Q9@turing.b2n.org> From: Raul To: freebsd-emulation@freebsd.org Subject: Re: problem after upgrading to 'virtualbox-ose-4.3.22' References: <20150214172038.Horde.M41WLY1KB2DrBugNTuhVfg1@turing.b2n.org> <54DF7AB4.5000809@abinet.ru> <54DF9DDF.4050900@FreeBSD.org> In-Reply-To: <54DF9DDF.4050900@FreeBSD.org> User-Agent: Horde Application Framework 5 Content-Type: text/plain; charset=UTF-8; format=flowed; DelSp=Yes MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 8bit 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: Sat, 14 Feb 2015 20:20:50 -0000 Jung-uk Kim escribió: >>> [....] % VBoxManage list vms Could not find VirtualBox >>> installation. Please reinstall. [....] > You should be in vboxusers group to run these commands. Thank you for your suggestion. The user that run VBoxManage is on vboxusers group. Portdowngrade didn't help me this time. No backup from portmaster, as the upgrade went fine. No clue from search engines. any help? :)