Opened 6 years ago
Last modified 6 years ago
#18407 new defect
vboxmanage controlvm <> savesate crashes if 3D acceleration is enabled
Reported by: | domino-pl | Owned by: | |
---|---|---|---|
Component: | 3D support | Version: | VirtualBox 6.0.4 |
Keywords: | vboxmanage, 3d, savestate | Cc: | |
Guest type: | all | Host type: | all |
Description
I wanted to create headless vms server. I found an strange error. When in specific conditions you exec:
vboxmanage controlvm <vmname> savestate
you go something like:
$ vboxmanage controlvm <cmname> savestate 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%... Progress state: NS_ERROR_ABORT VBoxManage: error: Failed to save machine state VBoxManage: error: The object is not ready VBoxManage: error: Details: code E_ACCESSDENIED (0x80070005), component SessionMachine, interface IMachine VBoxManage: error: Context: "RTEXITCODE handleControlVM(HandlerArg*)" at line 622 of file VBoxManageControlVM.cpp
and vm is aborted.
It looks similar to https://www.virtualbox.org/ticket/16437 but I collected more information. Error occurs only when 3D acceleration is enabled. Moreover it usually disappears when VirtualBox GUI windows is opened on any(or many) tty. Sometimes opened window dosn’t help. Problem sometimes disappears till next reboot.
Most of my tries started with vboxmanage startvm <vmname> --type headless via ssh but problem occurs also with normal vboxmanage startvm <vmname> in X environment.
It doesn’t matter what type of guest os family and type is set (you don’t have to install it).
I did tests which this hosts' os: Win 10 on physical machine – error sometimes occur Debian 9 on physical machine – error often occur Centos 7.6 on physical machine – error almost ever occur Debian, Ubuntu, Centos as VirtualBox Guest - error almost ever occur
Attachments (1)
Change History (3)
by , 6 years ago
Attachment: | guestLogFromDebian.log added |
---|
comment:2 by , 6 years ago
Hello. I suffer from the same exactly problem. Just in my case the 3D is off and VBox is version 5.2.2. I didn't wanted to update it, as everything worked for 2 years. But starting from 2 months ago I have this issue periodically.
Are there any news how to solve/avoid/work around this?
Many thanks.
Error also happens with poweroff command.
How could I edit piervous post???
I did tests which this hosts' os:
Win 10 on physical machine – error sometimes occur
Debian 9 on physical machine – error often occur
Centos 7.6 on physical machine – error almost ever occur
Debian, Ubuntu, Centos as VirtualBox Guest - error almost ever occur