Bug 175221 - emulators/virtualbox-ose: Cannot Resume VirtualBox VMs Via VBoxHeadless
Summary: emulators/virtualbox-ose: Cannot Resume VirtualBox VMs Via VBoxHeadless
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Virtualbox Team (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-11 20:50 UTC by Shawn Webb
Modified: 2018-02-20 13:57 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Shawn Webb 2013-01-11 20:50:00 UTC 
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
Comment 1 Edwin Groothuis freebsd_committer freebsd_triage 2013-01-20 01:49:01 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->vbox

Over to maintainer (via the GNATS Auto Assign Tool)
Comment 2 Bernhard Froehlich 2013-01-20 06:57:35 UTC 
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.
Comment 3 Shawn Webb 2013-01-21 19:17:33 UTC 
It used to work with the previous version when VNC was enabled. Not being
able to resume paused VMs is a regression.
Comment 4 Bernhard Froehlich 2013-01-21 20:26:18 UTC 
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öhlich <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.
Comment 5 Shawn Webb 2013-01-21 20:27:32 UTC 
Gotcha. So the VNC settings are persisted in the VM's config, then?
Comment 6 Walter Schwarzenfeld 2018-01-12 04:16:36 UTC 
Is this still relevant, or could it closed?
Comment 7 Walter Schwarzenfeld 2018-02-20 13:57:02 UTC 
It is overcome by time, versions has several changes. If there are still problems
with recent versions open a new PR.