VirtualBox

Ticket #3609 (reopened defect)

Opened 5 years ago

Last modified 4 years ago

Virtual Box crashes when restoring saved session -- PAE-related?

Reported by: jlevy Owned by:
Priority: critical Component: VM control
Version: VirtualBox 2.1.4 Keywords:
Cc: Guest type: Linux
Host type: Windows

Description

When I try to restore a saved state, the program closes. I have two VMs, and this only happens for one of them. However, I deleted this VM and made a new one with the same hard drive, and it still happens. The host is windows XP Pro SP3. The guest OS is Ubuntu 8.10 server. My other VM which saves just fine is Ubuntu 8.04 desktop. Could this problem be because the guest is a server OS, and I had to enable PAE?

Attachments

VBox.log Download (45.1 KB) - added by jlevy 5 years ago.
Windows XP (virtual disk)-2009-09-18-10-20-08.log Download (44.2 KB) - added by john.doe 5 years ago.
Log with Failed Assertion

Change History

Changed 5 years ago by jlevy

comment:1 Changed 5 years ago by mikejyg

I think I have encountered the same problem. I have 1 Linux VM under Windows. When PAE is enabled, Virtualbox crashes while restoring a saved state. When PAE is not enabled, restore works fine. It appears that PAE makes the difference.

comment:2 Changed 5 years ago by jlevy

Great. Narrowing down the problem is probably a good first step. I don't see any way to alter the title or keywords to reflect the nature of the problem now that we know what it is.

comment:3 Changed 5 years ago by frank

You could try if VirtualBox 2.2 Beta 2 makes any difference.

comment:4 Changed 5 years ago by jlevy

Nope, it doesn't seem to make a difference. It saves faster, which it great, but it still crashes when I try to restore.

comment:5 Changed 5 years ago by kihjin

I am experiencing the same, or similar, issue. After saving the state of two running VMs, any attempt to restore them results in "The machine is not mutable."

Occasionally, afterwards, I notice several VBoxSVC processes just hanging around. This isn't always the case, so, be aware.

kyle@anarix:~/vm$ ./stop-all.sh 
+ for x in 2 1
+ sleep 3
+ VBoxManage -nologo controlvm UBUNTU2 savestate
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
+ for x in 2 1
+ sleep 3
+ VBoxManage -nologo controlvm UBUNTU1 savestate
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
kyle@anarix:~/vm$ VBoxHeadless -s UBUNTU1 -p 10001
VirtualBox Headless Interface 2.1.4
(C) 2008-2009 Sun Microsystems, Inc.
All rights reserved.

[!] FAILED calling vrdpServer->SetPort(vrdpPort) at line 848!
[!] Primary RC  = VBOX_E_INVALID_VM_STATE (0x80BB0002) - Current virtual machine state prevents the operation
[!] Full error info present: true , basic error info present: true 
[!] Result Code = VBOX_E_INVALID_VM_STATE (0x80BB0002) - Current virtual machine state prevents the operation
[!] Text        = The machine is not mutable (state is 2)
[!] Component   = Machine, Interface: IMachine, {ea6fb7ea-1993-4642-b113-f29eb39e0df0}
[!] Callee      = IVRDPServer, {f4584ae7-6bce-474b-83d6-17d235e6aa89}
kyle@anarix:~/vm$ VBoxHeadless -s UBUNTU2 -p 10001
VirtualBox Headless Interface 2.1.4
(C) 2008-2009 Sun Microsystems, Inc.
All rights reserved.

[!] FAILED calling vrdpServer->SetPort(vrdpPort) at line 848!
[!] Primary RC  = VBOX_E_INVALID_VM_STATE (0x80BB0002) - Current virtual machine state prevents the operation
[!] Full error info present: true , basic error info present: true 
[!] Result Code = VBOX_E_INVALID_VM_STATE (0x80BB0002) - Current virtual machine state prevents the operation
[!] Text        = The machine is not mutable (state is 2)
[!] Component   = Machine, Interface: IMachine, {ea6fb7ea-1993-4642-b113-f29eb39e0df0}
[!] Callee      = IVRDPServer, {f4584ae7-6bce-474b-83d6-17d235e6aa89}

Attempting to start them following this is successful, albeit the 'saved state' is not restored. The system reports the VMs as having been aborted.

comment:6 Changed 5 years ago by kihjin

The reason I was getting the error has to do with using the -p parameter when starting a VM that has been saved. The VRDP information is saved along with the VM and cannot be changed, hence why it complains about the machine not being mutable.

comment:7 Changed 5 years ago by frank

  • Summary changed from Virtual Box crashes when restoring saved session to Virtual Box crashes when restoring saved session -- PAE-related?

kihjin, do you have PAE for the guest enabled as well?

comment:8 Changed 5 years ago by doodlebug

I just thought I'd add that I'm getting a similar thing using Ubuntu 9.04 as the host and Windows Server 2003 as the guest.

If I save the state from a normal session then start it everything is fine. But if I save a VBoxHeadless session, then start it I get the 'The machine is not mutable' error:

Start headless in background

colin@duckpond:~$ VBoxHeadless -startvm "REaD Web" -p 3391 &
[1] 6061
colin@duckpond:~$ VirtualBox Headless Interface 2.2.4
(C) 2008-2009 Sun Microsystems, Inc.
All rights reserved.

Listening on port 3391

Save the session

colin@duckpond:~$ VBoxManage controlvm "REaD Web" savestate
VirtualBox Command Line Management Interface Version 2.2.4
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.

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

Restart saved session as headless again

colin@duckpond:~$ VBoxHeadless -startvm "REaD Web" -p 3391
VirtualBox Headless Interface 2.2.4
(C) 2008-2009 Sun Microsystems, Inc.
All rights reserved.

ERROR: The machine is not mutable (state is 2)
Details: code VBOX_E_INVALID_VM_STATE (0x80bb0002), component Machine, interface IMachine, callee nsISupports
Context: "COMSETTER(Port)(vrdpPort)" at line 876 of file VBoxHeadless.cpp
[1]+  Done                    VBoxHeadless -startvm "REaD Web" -p 3391

So it looks like it is something to do with the VRDP.

Very annoying =I

comment:9 Changed 5 years ago by doodlebug

I've got it. It's to do with what kihjin said about the VRDP information being saved.

The mutable error actually seems to mean that you cannot change a setting because the virtual machine is not powered off. The problem seems to be that even though I'm specifying the same port for the VRDP when I resume the session, it's trying to apply that (effectively making a change to the session) and failing because the machine is not powered off.

If I resume without specifying a port then it carries on with the port I gave when I originally started the session.

That's quite annoying because now it means I have to know what state my machine was left in, and give a slightly different command. Ergh, I hope this gets fixed soon. =)

comment:10 Changed 5 years ago by doodlebug

This won't help you guys, but for anyone using a linux host who has this problem I just wrote this bash script to start and save my machines.

  • If a machine is running it will save it
  • If a machine is saved it will start it without the port number
  • If a machine is powered off (or aborted, or anything else) it will start it with the port number

Here it is:

#!/bin/bash

if [ `VBoxManage showvminfo "$1" | grep -c "State:           running"` -gt 0 ]
then
  echo Running
  VBoxManage controlvm "$1" savestate

elif [ `VBoxManage showvminfo "$1" | grep -c "State:           saved"` -gt 0 ]
then
  echo Saved
  VBoxHeadless -startvm "$1" &

else
  echo Other
  VBoxHeadless -startvm "$1" -p $2 &

fi

To use it just pass your machine name (in double quotes if it has spaces) and the port number you want it to use for VRDP.

For example:

./vbox.sh "REaD Web" 3391

comment:11 Changed 5 years ago by frank

doodlebug, your problem is completely unrelated. Your VM does not crash but it just wouldn't start. Your problem might be annoying but you can work around it by storing the port number permanently in the VM settings, for instance

VBoxManage modifyvm "REaD Web" --vrdpport 3391

From now on, you don't need to specify the VRDP port at the command line and you can safe and restore your VMs as you like.

comment:12 Changed 5 years ago by john.doe

Hi, I just posted under #4020 because previously the hang was occurring before the save of the machine state completed, however, the last two times [and never before] it has successfully saved state, but has crashed on resume, and similarly lists the state as "Aborted", and a cold boot follows.

To address the similarity or difference to previous posts, I am not using the command line tool, and PAE is and has been turned off for this appliance. A log of the most recent failure (which resembles the previous one I posted in #4020) follows:

00:00:02.740 ******************** End of CPUID dump **********************
00:00:02.743 REM: VBoxREM32
00:00:02.760 TM: GIP - u32Mode=1 (SyncTSC) u32UpdateHz=100
00:00:02.788 TM: cTSCTicksPerSecond=0x8f0885b0 (2 399 700 400) fTSCVirtualized=true  fTSCUseRealTSC=false
00:00:02.788 TM: fMaybeUseOffsettedHostTSC=true  TSCTiedToExecution=false TSCNotTiedToHalt=false
00:00:02.789 CoreCode: R3=185b6000 R0=5077e000 RC=a0210000 Phys=00000000010da000 cb=0x3000
00:00:02.814 [SMP] BIOS with 1 CPUs
00:00:02.832 SUP: Loaded VBoxDDR0.r0 (/Applications/VirtualBox.app/Contents/MacOS/VBoxDDR0.r0) at 0x426eb060 - ModuleInit at 0000000000000000 and ModuleTerm at 0000000000000000
00:00:02.842 SUP: Loaded VBoxDD2R0.r0 (/Applications/VirtualBox.app/Contents/MacOS/VBoxDD2R0.r0) at 0x423c0060 - ModuleInit at 0000000000000000 and ModuleTerm at 0000000000000000
00:00:02.842 Activating Local APIC
00:00:02.842 CPUMSetGuestCpuIdFeature: Enabled APIC
00:00:02.842 CPUMSetGuestCpuIdFeature: Disabled x2APIC
00:00:02.842 PIT: mode=3 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:02.851 Shared Folders service loaded.
00:00:02.888 VDInit finished
00:00:02.891 PIIX3 ATA: LUN#0: disk, PCHS=16383/16/63, total number of sectors 41943040
00:00:02.891 PIIX3 ATA: LUN#1: no unit
00:00:02.891 PIIX3 ATA: LUN#2: CD/DVD, total number of sectors 0, passthrough disabled
00:00:02.891 PIIX3 ATA: LUN#3: no unit
00:00:02.891 PIIX3 ATA: Ctl#0: finished processing RESET
00:00:02.989 PIIX3 ATA: Ctl#1: finished processing RESET
00:00:03.277 NAT: value of BindIP has been ignored
00:00:03.278 Audio: Trying driver 'coreaudio'.
00:00:04.581 DevPcBios: ATA LUN#0 LCHS=1024/255/63
00:00:04.582 PGMR3InitFinalize: 4 MB PSE mask 0000000fffffffff
00:00:04.593 HWACCM: Host CR4=00000660
00:00:04.593 HWACCM: MSR_IA32_FEATURE_CONTROL      = 7
00:00:04.593 HWACCM: MSR_IA32_VMX_BASIC_INFO       = 5a08000000000d
00:00:04.593 HWACCM: VMCS id                       = d
00:00:04.593 HWACCM: VMCS size                     = 800
00:00:04.593 HWACCM: VMCS physical address limit   = None
00:00:04.593 HWACCM: VMCS memory type              = 6
00:00:04.593 HWACCM: Dual monitor treatment        = 1
00:00:04.593 HWACCM: MSR_IA32_VMX_PINBASED_CTLS    = 3f00000016
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_PIN_EXEC_CONTROLS_EXT_INT_EXIT
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_PIN_EXEC_CONTROLS_NMI_EXIT
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_PIN_EXEC_CONTROLS_VIRTUAL_NMI
00:00:04.593 HWACCM: MSR_IA32_VMX_PROCBASED_CTLS   = f7f9fffe0401e172
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_IRQ_WINDOW_EXIT
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_TSC_OFFSET
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_HLT_EXIT
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_INVLPG_EXIT
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_MWAIT_EXIT
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_RDPMC_EXIT
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_RDTSC_EXIT
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_CR3_LOAD_EXIT
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_CR3_STORE_EXIT
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_CR8_LOAD_EXIT
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_CR8_STORE_EXIT
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_USE_TPR_SHADOW
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_NMI_WINDOW_EXIT
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_MOV_DR_EXIT
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_UNCOND_IO_EXIT
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_USE_IO_BITMAPS
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_USE_MSR_BITMAPS
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_MONITOR_EXIT
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_PAUSE_EXIT
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_USE_SECONDARY_EXEC_CTRL
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_CR3_LOAD_EXIT *must* be set
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC_CONTROLS_CR3_STORE_EXIT *must* be set
00:00:04.593 HWACCM: MSR_IA32_VMX_PROCBASED_CTLS2  = 4100000000
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC2_VIRT_APIC
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_PROC_EXEC2_WBINVD_EXIT
00:00:04.593 HWACCM: MSR_IA32_VMX_ENTRY_CTLS       = 3fff000011ff
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_ENTRY_CONTROLS_LOAD_DEBUG
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_ENTRY_CONTROLS_IA64_MODE
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_ENTRY_CONTROLS_ENTRY_SMM
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_ENTRY_CONTROLS_DEACTIVATE_DUALMON
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_ENTRY_CONTROLS_LOAD_GUEST_PERF_MSR
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_ENTRY_CONTROLS_LOAD_DEBUG *must* be set
00:00:04.593 HWACCM: MSR_IA32_VMX_EXIT_CTLS        = 3ffff00036dff
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_EXIT_CONTROLS_SAVE_DEBUG
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_EXIT_CONTROLS_HOST_AMD64
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_EXIT_CONTROLS_ACK_EXTERNAL_IRQ
00:00:04.593 HWACCM:    VMX_VMCS_CTRL_EXIT_CONTROLS_SAVE_DEBUG *must* be set
00:00:04.593 HWACCM: MSR_IA32_VMX_MISC             = 403c0
00:00:04.593 HWACCM:    MSR_IA32_VMX_MISC_PREEMPT_TSC_BIT 0
00:00:04.593 HWACCM:    MSR_IA32_VMX_MISC_ACTIVITY_STATES 7
00:00:04.593 HWACCM:    MSR_IA32_VMX_MISC_CR3_TARGET      4
00:00:04.593 HWACCM:    MSR_IA32_VMX_MISC_MAX_MSR         200
00:00:04.593 HWACCM:    MSR_IA32_VMX_MISC_MSEG_ID         0
00:00:04.593 HWACCM: MSR_IA32_VMX_CR0_FIXED0       = 80000021
00:00:04.593 HWACCM: MSR_IA32_VMX_CR0_FIXED1       = ffffffff
00:00:04.593 HWACCM: MSR_IA32_VMX_CR4_FIXED0       = 2000
00:00:04.593 HWACCM: MSR_IA32_VMX_CR4_FIXED1       = 67ff
00:00:04.593 HWACCM: MSR_IA32_VMX_VMCS_ENUM        = 2c
00:00:04.593 HWACCM: TPR shadow physaddr           = 00000000010de000
00:00:04.593 HWACCM: VCPU0: MSR bitmap physaddr      = 00000000010ea000
00:00:04.593 HWACCM: VCPU0: VMCS physaddr            = 00000000010e2000
00:00:04.593 HWACCM: Real Mode TSS guest physaddr  = 00000000f0800000
00:00:04.593 HWACCM: Non-Paging Mode EPT CR3       = 00000000f0803000
00:00:04.594 CPUMSetGuestCpuIdFeature: Enabled sysenter/exit
00:00:04.594 HWACCM: 32-bit guests supported.
00:00:04.594 HWACCM: VMX enabled!
00:00:04.602 VM: Halt method global1 (5)
00:00:04.602 Changing the VM state from 'CREATING' to 'CREATED'.
00:00:04.603 Changing the VM state from 'CREATED' to 'LOADING'.
00:00:04.983 SSM: File header: Format V1.2, VirtualBox Version 3.0.6 r52128, 32-bit host, cbGCPhys=8, cbGCPtr=8
00:00:04.984 PCI:    PIIX3/0: register 60: 0b -> 80
00:00:04.984 PCI:    PIIX3/0: register 61: 09 -> 89
00:00:04.984 PCI:    PIIX3/0: register 62: 0b -> 8b
00:00:04.984 PCI:    PIIX3/0: register 63: 09 -> 80
00:00:04.984 PCI:    PIIX3/0: register ad: 00 -> ef
00:00:04.984 PCI:    PIIX3/0: register de: 00 -> be
00:00:04.985 PCI: piix3ide/0: register 40: 00 -> 07
00:00:04.985 PCI: piix3ide/0: register 41: 80 -> e3
00:00:04.985 PCI: piix3ide/0: register 42: 00 -> 03
00:00:04.985 PCI: piix3ide/0: register 43: 80 -> e3
00:00:04.985 PCI: piix3ide/0: register 48: 00 -> 05
00:00:04.985 PCI: piix3ide/0: register 4a: 00 -> 02
00:00:04.985 PCI: piix3ide/0: register 4b: 00 -> 02
00:00:04.985 PCI:      vga/0: 16-bit field COMMAND: 2 -> 7
00:00:04.986 PCI:    pcnet/0:  8-bit field LATENCY_TIMER: 0 -> 60 - !READ ONLY!
00:00:04.986 PCI:    pcnet/0:  8-bit field INTERRUPT_LINE: b -> 13
00:00:04.986 PCI:   VMMDev/0:  8-bit field INTERRUPT_LINE: 9 -> 14
00:00:04.986 PCI:   VMMDev/0: 16-bit field COMMAND: 3 -> 7
00:00:04.986 PCI: usb-ohci/0:  8-bit field INTERRUPT_LINE: 9 -> 16
00:00:04.986 PCI: usb-ohci/0: 16-bit field COMMAND: 2 -> 7
00:00:04.986 PCI:     acpi/0: 16-bit field COMMAND: 1 -> 7
00:00:04.986 PCI: usb-ehci/0:  8-bit field INTERRUPT_LINE: b -> 13
00:00:04.986 PCI: usb-ehci/0: 16-bit field COMMAND: 2 -> 7
00:00:06.278 TM: cTSCTicksPerSecond=0x96a91d5c (2 527 665 500) fTSCVirtualized=true  fTSCUseRealTSC=false (state load)
00:00:06.283 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0) (restore)
00:00:06.283 RTC: period=0x200 (512) 64 Hz (restore)
00:00:06.283 SharedFolders host service: connected, u32ClientID = 1
00:00:06.284 SharedFolders host service: loading state, u32ClientID = 1
00:00:06.284 SharedFolders host service: success
00:00:06.284 Guest Additions information report: additionsVersion = 0x00010004, osType = 0x00033000
00:00:06.807 
00:00:06.807 !!Assertion Failed!!
00:00:06.807 Expression: !VM_FF_ISSET(pVM, VM_FF_PDM_DMA)
00:00:06.807 Location  : /Users/vbox/tinderbox/3.0-mac-rel/src/VBox/VMM/PDM.cpp(814) int pdmR3Load(VM*, SSMHANDLE*, uint32_t)

I believe the failed assertion regarding VM_FF_PDM_DMA has something to do with the problem. Does anyone know what that is?

comment:13 Changed 5 years ago by john.doe

Looks like the flag for Pending DMA operations in the Pluggable Device Manager was set when it shouldn't be. Either it was never properly init'ed, or something called the DMA servicer early. The code on sourcearchive doesn't let me search, so I'm not sure what calls PDMR3DmaRun, but it's possible whatever called it did so early or twice. I don't think init is a problem if pdmR3LoadPrep is being called, which I think it is because if not I would expect the PIC assertions to fail first, but since the LogFlow in that method isn't shown I guess I have no way of being certain. Interestingly, a comment in that method says a pending DMA transfer is "unlikely", yet it seems to be consistently the cause of this problem, unless I am totally misreading the code (possible). Hopefully someone who's actually worked on the project can posit a more precise cause (and, even better, fix it!) Thanks.

Changed 5 years ago by john.doe

Log with Failed Assertion

comment:14 Changed 5 years ago by john.doe

I just want to emphasize this is still happening in VitrualBox 3.0.6! In my case, the host is MacOS 10.5.8 with a WinXP SP3 guest.

comment:15 Changed 5 years ago by frank

  • Status changed from new to closed
  • Resolution set to duplicate

Duplicate of #5042 and fixed in the next maintenance release.

comment:16 Changed 5 years ago by sagemintblue

Is there another ticket which covers doodlebug's issue? I'm seeing exactly what s/he describes with VirtualBox 3.0.8 (Save vm state successfully; On attempted start w/ VBoxHeadless using a port specification this error is encountered; Second attempt with same command line succeeds).

comment:17 Changed 4 years ago by csizo

I can also verify the same behavior for 3.0.8

The host is Ubuntu server kernel: 2.6.24-26-server

Virtual Box used via VBoxHeadless
Command to start virtual machine:
VBoxHeadless --startvm [VmName] --vrdp on --vrdpport 5002 > /var/virtualbox/scriptlog 2>/var/virtualbox/scripterrorlog
fails
but
VBoxHeadless --startvm [VmName]_x64 --vrdp config > /var/virtualbox/scriptlog 2>/var/virtualbox/scripterrorlog
works fine

Guest is a Windows 2008 R2
Details (showvminfo)
Number of CPUs: 1
Synthetic Cpu: off
CPUID overrides: None
...
ACPI: on
IOAPIC: on
PAE: on
Time offset: 0 ms
Hardw. virt.ext: on
Hardw. virt.ext exclusive: on
Nested Paging: on
VT-x VPID: off
...
VRDP: enabled (Address 0.0.0.0, Ports 5002, MultiConn: off, ReuseSingleConn: off, Authentication type: null)
VRDP port: 5002


Symptoms
Save virtual machine successful
starting is not possible only if the VBoxHeadless command does not have the explicit vrdpport setting

comment:18 Changed 4 years ago by fychan

  • Status changed from closed to reopened
  • Resolution duplicate deleted

Verified on 3.2.4

It's definitely to do with restoring the machine from a saved state and declaring a port for the VRDP. The savestate works fine, the restart command fails if you tell it a port to load on.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use