From owner-freebsd-ports-bugs@FreeBSD.ORG  Sat Jun 29 18:53:54 2013
Return-Path: <owner-freebsd-ports-bugs@FreeBSD.ORG>
Delivered-To: freebsd-ports-bugs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id F1E02ED0;
 Sat, 29 Jun 2013 18:53:53 +0000 (UTC)
 (envelope-from daemon@dx.burplex.com)
Received: from dx.burplex.com (dx.burplex.com [50.197.134.185])
 by mx1.freebsd.org (Postfix) with ESMTP id B12631093;
 Sat, 29 Jun 2013 18:53:53 +0000 (UTC)
Received: by dx.burplex.com (Postfix, from userid 1)
 id 87D2B36F499B; Sat, 29 Jun 2013 11:53:47 -0700 (PDT)
To: Grzegorz Blach <gblach@freebsd.org>
Subject: Re: ports/180086: VirtualBox - Can't select amount of RAM for virtual
 machine
From: Waitman Gobble <uzimac@da3m0n8t3r.com>
X-UUID-HOR: 441ae1b2-e0af-11e2-a0c8-902b34a86bc3
Message-Id: <20130629185347.87D2B36F499B@dx.burplex.com>
Date: Sat, 29 Jun 2013 11:53:47 -0700 (PDT)
Cc: freebsd-ports-bugs@freebsd.org, vbox@freebsd.org
X-BeenThere: freebsd-ports-bugs@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Ports bug reports <freebsd-ports-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports-bugs>
List-Post: <mailto:freebsd-ports-bugs@freebsd.org>
List-Help: <mailto:freebsd-ports-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jun 2013 18:53:54 -0000

On Sat, 29 Jun 2013 11:23:50 GMT, Grzegorz Blach <gblach@freebsd.org> wrote:

>
>
>After last update to 4.2.14 I'm only able to assign 0 MB of RAM to new
virtual machine, which is definitely too low. Also next button is unactive.
You can look on 'Memory size' window at http://files.roorback.net/vbox.jpg


I have noticed this problem on 10.0-Current, started about one month ago.
Hitting 'settings' in the gui for any existing machine causes it to 'hang'
indefinitely, and when creating a new machine there is no way to change the
RAM, and no way to move 'forward' in config wizard as Grzegorz Blach has
reported. There do not appear to be any error messages or warnings from
VirtualBox gui, it just sits there until the end of time.

However, using VBoxManage on command line works, allowing you to create and
edit machines. Launching machines from gui works too.

I attached gdb to the VirtualBox process, it looks like it's spinning around
in a pthread function when the problem happens. 
When I get some time I need to rebuild with debugging symbols to get a good
sense of what's going on. 


--
Waitman Gobble
San Jose California USA
+1.5108307875