VirtualBox

Ticket #4768 (closed defect: obsolete)

Opened 5 years ago

Last modified 5 months ago

VBOX_E_INVALID_SESSION_STATE - can't resume any guest

Reported by: user4711 Owned by:
Priority: major Component: other
Version: VirtualBox 3.0.4 Keywords:
Cc: Guest type: Windows
Host type: Linux

Description (last modified by frank) (diff)

I can't resume a previous saved guest with VBoxManage. Every time this error occurs: ERROR: The machine 'test1' does not have an open session Details: code VBOX_E_INVALID_SESSION_STATE (0x80bb000b), component Machine, interface IMachine, callee nsISupports Context: "OpenExistingSession (a->session, uuid)" at line 584 of file VBoxManage.cpp

With VirtualBox (GUI) it ist possible to resume this guest.

I tested this with different guests an updated the complete server (CentOS 5.3), reinstalled VirtualBox, dropped the configuration (xml) - nothing works. Any hint?

Attachments

VBox.log Download (55.0 KB) - added by miggel13 4 years ago.

Change History

comment:1 in reply to: ↑ description Changed 4 years ago by miggel13

Replying to user4711:

Hello everybody, i've the same problem. I can save a virtual machine but i can't resume the machine. It' doesn't matter if i want to resume a machine locally or over a ssh-connection. Both of them doesn't work.

Any ideas?

I can't resume a previous saved guest with VBoxManage. Every time this error occurs: ERROR: The machine 'test1' does not have an open session Details: code VBOX_E_INVALID_SESSION_STATE (0x80bb000b), component Machine, interface IMachine, callee nsISupports Context: "OpenExistingSession (a->session, uuid)" at line 584 of file VBoxManage.cpp

With VirtualBox (GUI) it ist possible to resume this guest.

I tested this with different guests an updated the complete server (CentOS 5.3), reinstalled VirtualBox, dropped the configuration (xml) - nothing works. Any hint?

comment:2 Changed 4 years ago by klaus

It's really interesting to see that 2 users claim to have the same problem, without having a halfway complete problem description.

What are you doing exactly? Full command lines please. Are you trying to resume a VM which was originally started by the VirtualBox GUI with a different frontend (such as VBoxHeadless)? It's wasting time having to guess such things.

Also, what's missing is VBox.log (if possible both for the original run in the GUI and for the failed restore). That would also answer a lot of questions.

comment:3 Changed 4 years ago by miggel13

OK: Here are some more information about MY problem. My host system is an ubuntu 9.10, 64 Bit. I'm working with an AMD-Processor, AMD Phenom 9550 i think, 8 GB of Ram and a 80 GB harddisk. If you need more information, you can contact me an i will post more information!

I can not start a virtual machine which is installed with the graphical user interface of Sun (Sun Virtual Box GUI) over a ssh-connection without any X-Services (graphical services).

If i want to start a vm over the ssh-connection, i get the following text (the machine is off, not saved):

christian@wien:~$ VBoxManage controlvm sv1 startvm
VirtualBox Command Line Management Interface Version 3.1.2
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.

ERROR: The machine 'sv1' does not have an open session
Details: code VBOX_E_INVALID_SESSION_STATE (0x80bb000b), component Machine, interface IMachine, callee nsISupports
Context: "OpenExistingSession(a->session, machineuuid)" at line 94 of file VBoxManageControlVM.cpp

When i want to start a machine, which is saved with the graphical user interface (the originally VirtualBox-gui) i get the same error:

christian@wien:/var/log$ VBoxManage controlvm sv2 resume
VirtualBox Command Line Management Interface Version 3.1.2
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.

ERROR: The machine 'sv2' does not have an open session
Details: code VBOX_E_INVALID_SESSION_STATE (0x80bb000b), component Machine, interface IMachine, callee nsISupports
Context: "OpenExistingSession(a->session, machineuuid)" at line 94 of file VBoxManageControlVM.cpp

In the attachments, you can see the VBox.log file for my virtual-machine.

Additionally, it doesn't matter if i use an ssh-connection from an other computer or i work locally on the vm-hosting-machine. Both don´t work.

Changed 4 years ago by miggel13

comment:4 Changed 4 years ago by klaus

miggel13, this seems to be a big misunderstanding. You're using the wrong VBoxManage commands, so the error messages are normal.

For starting a VM (whether powered off or in saved state), use VBoxManage startvm VMNAME --type vrdp. The manual doesn't mention a startvm subcommand of VBoxManage controlvm anywhere. VBoxManage controlvm is for controlling VMs which are already running. Additionally, the resume subcommand is for continuing a paused VM, not a VM in saved state.

Since I have absolutely no idea so far if user4711 was really using the same commands, I would appreciate feedback from you as well.

comment:5 Changed 4 years ago by miggel13

Hi klaus,
FIRST: thank you very much.

This was my problem. I tried the wrong command. Now it works locally and, of course over a ssh-connection.

When i type "VBoxManage controlvm", then i get the following:

VBoxManage controlvm        <uuid>|<name>
                            pause|resume|reset|poweroff|savestate|
                            acpipowerbutton|acpisleepbutton|
                            keyboardputscancode <hex> [<hex> ...]|
                            injectnmi|
                            setlinkstate<1-N> on|off |
                            nic<1-N> null|nat|bridged|intnet|hostonly
                                     [<devicename>] |
                            nictrace<1-N> on|off
                            nictracefile<1-N> <filename>
                            usbattach <uuid>|<address> |
                            usbdetach <uuid>|<address> |
                            vrdp on|off |
                            vrdpport default|<ports> |
                            setvideomodehint <xres> <yres> <bpp> [display] |
                            setcredentials <username> <password> <domain>
                                           [--allowlocallogon <yes|no>] |
                            teleport --host <name> --port <port>
                                   [--maxdowntime <msec>] [--password password]

And i thought i must use "controlvm" to control a vm (e.g. start a vm, stop a vm, save a vm, ...)

Additionally, the error message isn't very enlightening - least for me!

But now it works and i'm very happy.

Thanks a lot.

comment:6 Changed 5 months ago by frank

  • Status changed from new to closed
  • Resolution set to obsolete
  • Description modified (diff)
Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use