Unable to savestate following a previous savestate

This is for discussing general topics about how to use VirtualBox.

Unable to savestate following a previous savestate

Postby kihjin » 3. Apr 2009, 19:53

I have two systems running VBoxHeadless in two screen sessions.

screen -S vm1 -d -m VBoxHeadless -s vm1 (UUID: aad05dae-75b1-4501-972d-a9a49fb5678d)
screen -S vm2 -d -m VBoxHeadless -s vm2 (UUID: 3cc90f04-22ca-477e-a75d-40af94a9c09a)

After starting the sessions, they show as "running" under showvminfo. I can also execute list runningvms and display the two UUIDs.

I open up two RDP connections to these vms.

Then I try the following:

Code: Select all   Expand viewCollapse view
:~$ VBoxManage -nologo list runningvms
aad05dae-75b1-4501-972d-a9a49fb5678d
3cc90f04-22ca-477e-a75d-40af94a9c09a


OK, there they are running.

Code: Select all   Expand viewCollapse view
:~$ VBoxManage controlvm aad05dae-75b1-4501-972d-a9a49fb5678d savestate
VirtualBox Command Line Management Interface Version 2.1.4
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.

0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%


At this point one of the VM RDP sessions disconnects. All good so far.

Code: Select all   Expand viewCollapse view
:~$ VBoxManage controlvm 3cc90f04-22ca-477e-a75d-40af94a9c09a savestate
VirtualBox Command Line Management Interface Version 2.1.4
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.

[!] FAILED calling a->virtualBox->OpenExistingSession (a->session, uuid) at line
 2784!
[!] Primary RC  = VBOX_E_INVALID_SESSION_STATE (0x80BB000B) - Current session state prohibits operation
[!] Full error info present: true , basic error info present: true
[!] Result Code = VBOX_E_INVALID_SESSION_STATE (0x80BB000B) - Current session state prohibits operation
[!] Text        = The machine 'vm2' does not have an open session
[!] Component   = Machine, Interface: IMachine, {ea6fb7ea-1993-4642-b113-f29eb39e0df0}
[!] Callee      = IVirtualBox, {339abca2-f47a-4302-87f5-7bc324e6bbde}


What just happened here? It says it isn't open, but, my RDP session is definitely active.

Code: Select all   Expand viewCollapse view
:~$ ps x
  PID TTY      STAT   TIME COMMAND
 1477 ?        Sl     0:00 /usr/lib/virtualbox/VBoxSVC --automate
 1504 ?        Ss     0:00 SCREEN -S vm2 -d -m /home/vm/start-vm.sh vm2
 1505 pts/3    Ss+    0:00 /bin/bash /home/vm/start-vm.sh vm2
 1506 pts/3    Sl+    0:30 /usr/lib/virtualbox/VBoxHeadless -s vm2


At this point none of the controlvm commands work for vm2. They report the machine as being powered off. showvminfo shows the system as 'powered off' yet it isn't.

If I 'savestate' in the reverse order, it works fine. It looks like they need to be 'saved' in the opposite order to what they were started. I tried starting them in the opposite order, and I experienced the same effect.

Is this a feature?
kihjin
 
Posts: 71
Joined: 18. Nov 2008, 21:30
Primary OS: Ubuntu other
VBox Version: OSE self-compiled
Guest OSses: Ubuntu, Windows XP

Re: Unable to savestate following a previous savestate

Postby TerryE » 4. Apr 2009, 05:18

Hi, this looks like a bug. Can you please use the public Bugtracker to raise a ticket on this issue. You will first need to register for a wiki user account (this is different to a forum account sorry) and then you can logon to the wiki and raise the ticket. Make sure to give your version and platfomm details and attach VBox.log files for both vm1 and vm2.
Read the Forum Posting Guide
Google your Q site:VirtualBox.org or search for the answer before posting.
TerryE
Site Moderator
 
Posts: 3572
Joined: 28. May 2008, 08:40
Primary OS: Ubuntu other
VBox Version: PUEL
Guest OSses: Ubuntu 10.04 & 11.10, both Svr&Wstn, Debian, CentOS

Re: Unable to savestate following a previous savestate

Postby kihjin » 5. Apr 2009, 03:42

Thanks Terry. That is what I was afraid of. I was able to replicate this behavior on another machine with four base Ubuntu Server VMs. I will submit a bug report soon.
kihjin
 
Posts: 71
Joined: 18. Nov 2008, 21:30
Primary OS: Ubuntu other
VBox Version: OSE self-compiled
Guest OSses: Ubuntu, Windows XP

Re: Unable to savestate following a previous savestate

Postby kihjin » 5. Apr 2009, 04:13

Ticket has been submitted with details.

http://www.virtualbox.org/ticket/3637
kihjin
 
Posts: 71
Joined: 18. Nov 2008, 21:30
Primary OS: Ubuntu other
VBox Version: OSE self-compiled
Guest OSses: Ubuntu, Windows XP

Re: Unable to savestate following a previous savestate

Postby morettoni » 23. Jun 2009, 10:56

kihjin wrote:I have two systems running VBoxHeadless in two screen sessions.

screen -S vm1 -d -m VBoxHeadless -s vm1 (UUID: aad05dae-75b1-4501-972d-a9a49fb5678d)
screen -S vm2 -d -m VBoxHeadless -s vm2 (UUID: 3cc90f04-22ca-477e-a75d-40af94a9c09a)

After starting the sessions, they show as "running" under showvminfo. I can also execute list runningvms and display the two UUIDs.

[...cut...]

Is this a feature?


I have a similar problem when I shutdown one VM in a multiple VMs env., is related?
Luca Morettoni <luca@morettoni.net> | OpenSolaris SCA #OS0344
Web/BLOG: http://www.morettoni.net/ | http://twitter.com/morettoni
jugUmbria founder - https://jugUmbria.dev.java.net/
ITL-OSUG leader - http://www.opensolaris.org/os/project/itl-osug/
morettoni
 
Posts: 6
Joined: 8. Oct 2008, 08:54
Location: Perugia - Italy

Re: Unable to savestate following a previous savestate

Postby TerryE » 23. Jun 2009, 16:34

Luca, what is your error message?

Are you just doing a VBoxManage controlvm XXX savestate/poweroff?
Read the Forum Posting Guide
Google your Q site:VirtualBox.org or search for the answer before posting.
TerryE
Site Moderator
 
Posts: 3572
Joined: 28. May 2008, 08:40
Primary OS: Ubuntu other
VBox Version: PUEL
Guest OSses: Ubuntu 10.04 & 11.10, both Svr&Wstn, Debian, CentOS


Return to Using VirtualBox

Who is online

Users browsing this forum: No registered users and 27 guests