Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#56891 - Suspend/Wake Errors

Attached to Project: Arch Linux
Opened by scott (daily_pilgrim) - Friday, 29 December 2017, 04:04 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 29 December 2017, 22:19 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

VBox Arch Linux Guest Crash Report

System Info:
4.14.8-1-ARCH
xfce4 version 4.12
Virtualbox 5.2.4r119758

Summary:

Issuing the '$systemctl suspend' command turns screen black. System fails to wake from keyboard and mouse input. The ACPI Shutdown command is executed via virtualbox menu bar>Machine>ACPI Shutdown. The Arch CLI boots and returns the output in the file attached.

Addendum:

I realize that this crash could very well be a bug for 'upstream', in which case I apologize for having wasted anyone's time. I'm very new at this and constantly neck-deep in open tabs to learn about linux at the systems level. I've scanned archlinux bug report guidelines and some forums and searched for similar crashes; simply put, it's still unclear to me as to who I should report to and what I should include in my report as far as my system's error output regarding this incident. It appears there's some relevance to what happened in journalctl, but I thought I'd start with this small bit and go from there. Thanks for any response at all to my inquiry, and I apologize in advance if I've wasted anyone's time.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Friday, 29 December 2017, 22:19 GMT
Reason for closing:  Not a bug
Comment by scott (daily_pilgrim) - Friday, 29 December 2017, 21:13 GMT
Here is an answer supplied by askubuntu in response to a similiar question that settled it for me and was going to close my bug report. I thought I'd add it here just for documentation purposes.

"For Virtual Box it is not recommended to use the power saving features of the guest OS as this will all be handled by the host. Therefore first thing when having installed my guest OS I disable this (including disabling the screen saver).

The appropriate way to save a virtual machines state (and resume later) is to choose Save the machine state when closing the machine from virtual box manager (here depicted for Windows XP).

This will free all ressources from the virtual machine. Next time we start the machine we will resume exactly at the same state where we saved it (like in suspend/hibernate from a real machine).

From command line this can also be done by

VBoxManage controlvm <name_of_machine> savestate"

Loading...