VirtualBox

Ticket #2049 (new defect)

Opened 6 years ago

Last modified 6 years ago

VBoxHeadless with "-a" option aborts when restoring state

Reported by: steved424 Owned by:
Priority: minor Component: other
Version: VirtualBox 1.6.6 Keywords: vboxheadless restore resume
Cc: Guest type: Windows
Host type: Linux

Description

I'm running VB 1.6.6 on Ubuntu (this bug happens on both Gutsy and Hardy.)

If I use the -a option to VBoxHeadless to restore a VM with saved state, I get the following error message (and the VM is set to 'aborted' state):

VirtualBox Headless Interface 1.6.6
(C) 2008 Sun Microsystems, Inc.
All rights reserved

[!] FAILED calling vrdpServer->SetNetAddress(Bstr(vrdpAddress)) at line 855!
[!] Primary RC  = E_ACCESSDENIED (0x80070005) - Access denied
[!] Full error info present: true , basic error info present: true 
[!] Result Code = E_ACCESSDENIED (0x80070005) - Access denied
[!] Text        = The machine is not mutable (state is 2)
[!] Component   = Machine, Interface: IMachine, {f95c0793-7737-49a1-85d9-6da81097173b}
[!] Callee      = IVRDPServer, {ed9d31ae-867f-45fc-b727-6740084d1883}

The command I'm running is

VBoxHeadless -s <VMName> -a 127.0.0.1

It doesn't seem to happen when starting a VM from powered off state. In case it is relevant, I'm saving the VM states with "VBoxManage controlvm VMName savestate".

Change History

comment:1 Changed 6 years ago by michael

As far as I know, the VRDP address is set when the VM is originally started and cannot be changed until it is stopped again (just saving the state doesn't count as stopping).

comment:2 Changed 6 years ago by steved424

Ah, OK, I didn't realize the setting was persistent. (Though is there any particular reason for a front-end, per-session setting to be tied to the life of the VM, given that the session may be much shorter lived? And should it set the state to 'aborted'?)

Feel free to downgrade the severity, BTW, or mark it as a documentation issue, or whatever.

comment:3 Changed 6 years ago by michael

  • Priority changed from major to minor

There probably isn't a good reason, which is why I didn't close the ticket. This will probably get fixed at some point, but it is of course very low on the priority list.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use