Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 27 Jun 2013 13:33:45 GMT
From:      kaltheat <kaltheat@gmail.com>
To:        freebsd-gnats-submit@FreeBSD.org
Subject:   ports/180026: VirtualBox 4.2.14 GUI broken
Message-ID:  <201306271333.r5RDXjtg003607@oldred.freebsd.org>
Resent-Message-ID: <201306271340.r5RDe2up024501@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         180026
>Category:       ports
>Synopsis:       VirtualBox 4.2.14 GUI broken
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jun 27 13:40:02 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator:     kaltheat
>Release:        FreeBSD 9.1 RELEASE amd64
>Organization:
>Environment:
>Description:
After update of emulators/virtualbox-ose to latest version (4.2.14) 
virtualbox GUI is not able to set memory correctly. In GUI the maximum of 
choosable memory is 0MB. I tried it without the old settings and machine dirs 
~/.VirtualBox, ~/VirtalBox VMs and got the same result.

With VBoxManage however everything works fine:

$ VBoxManage createvm --name test --register
Virtual machine 'test' is created and registered.
UUID: 48382805-96e5-4954-899f-c05836a5ec6e
Settings file: '~/VirtualBox VMs/test/test.vbox'
$ VBoxManage modifyvm test --memory 1024
$

Nonetheless old vms seem to work.

Related mail-thread: http://lists.freebsd.org/pipermail/freebsd-emulation/2013-June/010651.html
>How-To-Repeat:
Try to modify system settings (memory) via VirtualBox-GUI ...
>Fix:
Not known, but first suspicion is a Qt-bug:
http://lists.freebsd.org/pipermail/freebsd-emulation/2013-June/010655.html

>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201306271333.r5RDXjtg003607>