VirtualBox

Ticket #16745 (new defect) — at Version 4

Opened 4 years ago

Last modified 4 years ago

Segmentation fault while starting a VM headless from snapshot

Reported by: bb90 Owned by:
Component: VM control Version: VirtualBox 5.1.22
Keywords: segfault snapshot headless Cc:
Guest type: Linux Host type: Linux

Description (last modified by frank) (diff)

Given a newly created Ubuntu VM installed with Cloud-Init And a snapshot from the VM When I restore the snapshot (VBoxManage snapshot server restorecurrent --> no problem) And start the VM (VBoxManage startvm server --type headless)

Then I get 'VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component SessionMachine, interface ISession' And there is segfault log in syslog (attached).

Ubuntu 16.04.2 LTS (Xenial Xerus)
Linux HOST 4.8.0-49-generic #52~16.04.1-Ubuntu SMP Thu Apr 20 10:55:59 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

There is also some path mismatch. Snapshot file is here: /home/USER/VirtualBox VMs/GROUP/server/Snapshots/{b60bca32-76e8-4815-88cd-e55516a6186a}.vdi VBox wants: /home/USER/VirtualBox VMs/GROUP/server/Snapshots/2017-05-09T09-32-52-131952000Z.sav/Snapshots/2017-05-09T09-32-52-131952000Z.sav

Please fix this issue. For now, I have to revert the VirtualBox version to older, working one.

Change History

Changed 4 years ago by bb90

Changed 4 years ago by bb90

comment:1 Changed 4 years ago by bb90

Also:

VBoxManage unregistervm --delete server
0%...10%...20%...30%...40%...50%...60%...
Progress state: VBOX_E_IPRT_ERROR
VBoxManage: error: Machine delete failed
VBoxManage: error: Could not delete file '/home/USER/VirtualBox VMs/GROUP/server/Snapshots/2017-05-09T09-32-52-131952000Z.sav/Snapshots/2017-05-09T09-32-52-131952000Z.sav'(VERR_FILE_NOT_FOUND)
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component MachineWrap, interface IMachine
VBoxManage: error: Context: "RTEXITCODE handleUnregisterVM(HandlerArg*)" at line 163 of file VBoxManageMisc.cpp
Last edited 4 years ago by frank (previous) (diff)

comment:2 Changed 4 years ago by bb90

Work around: if the newly created VM is not moved to a VM group. Than the problem does not occur. Maybe the .sav file is not moved with the VM.

comment:3 Changed 4 years ago by frank

Would be interesting to know which older, working version of VirtualBox you are referring to.

comment:4 Changed 4 years ago by frank

  • Description modified (diff)

Furthermore I would like to have a step-by-step reproduction scenario for the problem triggered with VBox 5.1.22.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use