Date: Sat, 29 Jun 2013 11:53:47 -0700 (PDT) From: Waitman Gobble <uzimac@da3m0n8t3r.com> To: Grzegorz Blach <gblach@freebsd.org> Cc: freebsd-ports-bugs@freebsd.org, vbox@freebsd.org Subject: Re: ports/180086: VirtualBox - Can't select amount of RAM for virtual machine Message-ID: <20130629185347.87D2B36F499B@dx.burplex.com>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130629185347.87D2B36F499B>