From nobody@FreeBSD.org  Fri Jan 11 20:49:41 2013
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1])
	by hub.freebsd.org (Postfix) with ESMTP id 97DF452A
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 11 Jan 2013 20:49:41 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22])
	by mx1.freebsd.org (Postfix) with ESMTP id 8875BC7
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 11 Jan 2013 20:49:41 +0000 (UTC)
Received: from red.freebsd.org (localhost [127.0.0.1])
	by red.freebsd.org (8.14.5/8.14.5) with ESMTP id r0BKnfRJ094292
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 11 Jan 2013 20:49:41 GMT
	(envelope-from nobody@red.freebsd.org)
Received: (from nobody@localhost)
	by red.freebsd.org (8.14.5/8.14.5/Submit) id r0BKnfdI094291;
	Fri, 11 Jan 2013 20:49:41 GMT
	(envelope-from nobody)
Message-Id: <201301112049.r0BKnfdI094291@red.freebsd.org>
Date: Fri, 11 Jan 2013 20:49:41 GMT
From: Shawn Webb <lattera@gmail.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: Cannot Resume VirtualBox VMs Via VBoxHeadless
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         175221
>Category:       ports
>Synopsis:       emulators/virtualbox-ose: Cannot Resume VirtualBox VMs Via VBoxHeadless
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    vbox
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jan 11 20:50:00 UTC 2013
>Closed-Date:    
>Last-Modified:  Tue Apr 22 05:33:09 UTC 2014
>Originator:     Shawn Webb
>Release:        10-current
>Organization:
>Environment:
FreeBSD shawn-vm-host 10.0-CURRENT FreeBSD 10.0-CURRENT #8 r245297+a03dd2b-dirty: Fri Jan 11 11:13:56 EST 2013     shawn@shawn-vm-host:/usr/obj/usr/src/sys/SEC  amd64
>Description:
After pausing a VM by using `VBoxManage controlvm [VM name] savestate`, I cannot resume the VM by using `VBoxHeadless -s [VM name] [VNC options]`. I get the following error:

$ VBoxHeadless -s 'Debian x64' -e TCP/Address=0.0.0.0 -e TCP/Ports=5091 -e VNCPass=password
VBoxManage: error: Cannot resume the machine as it is not paused (machine state: Saved)
VBoxManage: error: Details: code VBOX_E_INVALID_VM_STATE (0x80bb0002), component Console, interface IConsole, callee nsISupports
VBoxManage: error: Context: "Resume()" at line 120 of file VBoxManageControlVM.cpp
>How-To-Repeat:
1) Start a VM by using VBoxHeadless: VBoxHeadless -s 'Debian x64' -e TCP/Address=0.0.0.0 -e TCP/Ports=5091 -e VNCPass=password
2) Pause VM by using VBoxManage: VBoxManage controlvm 'Debian x64' savestate
3) Resume VM by using VBoxHeadless: VBoxHeadless -s 'Debian x64' -e TCP/Address=0.0.0.0 -e TCP/Ports=5091 -e VNCPass=password
>Fix:


>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-ports-bugs->vbox 
Responsible-Changed-By: edwin 
Responsible-Changed-When: Sun Jan 20 01:49:01 UTC 2013 
Responsible-Changed-Why:  
Over to maintainer (via the GNATS Auto Assign Tool) 

http://www.freebsd.org/cgi/query-pr.cgi?pr=175221 

From: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= <decke@bluelife.at>
To: bug-followup@FreeBSD.org, lattera@gmail.com
Cc:  
Subject: Re: ports/175221: emulators/virtualbox-ose: Cannot Resume VirtualBox
 VMs Via VBoxHeadless
Date: Sun, 20 Jan 2013 07:57:35 +0100

 --e89a8fb1ffc4fe4f8b04d3b2dba2
 Content-Type: text/plain; charset=ISO-8859-1
 
 I guess you are doing that with vbox 4.2.6 where VNC support is now
 implemented as VRDE extpack. So this cannot work and you need to set the
 vnc config with vboxmanage and shutdown the vm.
 
 --e89a8fb1ffc4fe4f8b04d3b2dba2--

From: Shawn Webb <lattera@gmail.com>
To: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= <decke@bluelife.at>
Cc: bug-followup@freebsd.org
Subject: Re: ports/175221: emulators/virtualbox-ose: Cannot Resume VirtualBox
 VMs Via VBoxHeadless
Date: Mon, 21 Jan 2013 14:17:33 -0500

 --20cf3079bb0a3072c504d3d150d2
 Content-Type: text/plain; charset=ISO-8859-1
 Content-Transfer-Encoding: quoted-printable
 
 It used to work with the previous version when VNC was enabled. Not being
 able to resume paused VMs is a regression.
 
 --20cf3079bb0a3072c504d3d150d2--

From: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= <decke@bluelife.at>
To: lattera@gmail.com
Cc: bug-followup@freebsd.org
Subject: Re: ports/175221: emulators/virtualbox-ose: Cannot Resume VirtualBox
 VMs Via VBoxHeadless
Date: Mon, 21 Jan 2013 21:26:18 +0100

 --14dae939914d090f7c04d3d24664
 Content-Type: text/plain; charset=ISO-8859-1
 Content-Transfer-Encoding: quoted-printable
 
 Am 21.01.2013 20:17 schrieb "Shawn Webb" <lattera@gmail.com>:
 >
 > It used to work with the previous version when VNC was enabled. Not being
 able to resume paused VMs is a regression.
 >
 >
 > On Sun, Jan 20, 2013 at 1:57 AM, Bernhard Fr=F6hlich <decke@bluelife.at>
 wrote:
 >>
 >> I guess you are doing that with vbox 4.2.6 where VNC support is now
 implemented as VRDE extpack. So this cannot work and you need to set the
 vnc config with vboxmanage and shutdown the vm.
 
 I'm not sure if you got me right. The vnc support was hacked into vbox up
 to 4.1.x and was implemented as a proper extension pack in 4.2. As a
 consequence the configuration has changed in a non compatible way. So you
 need to forcibly stop the vm once and switch your vnc config to vboxmanage
 properties. Starting it with proper vm config should also allow you to
 properly stop and pause it again.
 
 --14dae939914d090f7c04d3d24664--

From: Shawn Webb <lattera@gmail.com>
To: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= <decke@bluelife.at>
Cc: bug-followup@freebsd.org
Subject: Re: ports/175221: emulators/virtualbox-ose: Cannot Resume VirtualBox
 VMs Via VBoxHeadless
Date: Mon, 21 Jan 2013 15:27:32 -0500

 --14dae9cdc32b7b898904d3d24a68
 Content-Type: text/plain; charset=ISO-8859-1
 Content-Transfer-Encoding: quoted-printable
 
 Gotcha. So the VNC settings are persisted in the VM's config, then?
 
 --14dae9cdc32b7b898904d3d24a68--
>Unformatted:
