qemuctl(1) [debian man page]

qemuctl(1)																qemuctl(1)

NAME

       qemuctl - Graphical control for qemu

SYNTAX

       qemuctl [-suspend-dir <dir>] [-suspend-file <filename>] [-qemu <qemu>]  [-nowakeup] qemu-options

DESCRIPTION

       qemuctl	is a gui that controls a qemu process with the built-in monitor of qemu. So you can change devices, suspend machines, save screen-
       shots, ...

       If you suspend a machine it will do the following macro:

       stop
       screendump "suspend-dir/suspend-file.ppm"
       savevm "suspend-dir/suspend-file.vm"
       commit
       quit

       You can afterwards resume the machine with:

       qemuctl -suspend-dir suspend-dir -suspend-file suspend-file your_qemu_options
       the suspend-files will then be deleted
       or
       qemuctl -loadvm suspend-dir/suspend-file.vm your_qemu_options

       Be aware that you can't use the "-monitor" option with qemuctl, because it needs the control over the monitor. The option  "-serial  stdio"
       can't be used, too.

OPTIONS

       -suspend-file <filename>
	      This  option  is	normaly  used by qemuctl to support suspend and wakeup. qemuctl can then find the vm-state-file in its folders and
	      wakeup the virtual machine. If the file is there the qemuctl waes up the virtual machine and deletes the file afterwards. On suspend
	      the  vm-state-file is then stored as the <filename> with the .vm ending and the screenshot is stored as the <filename> with the .ppm
	      ending.
	      Default filename is "suspend".

       -suspend-dir <dir>
	      This is the dir where the suspend files would be stored or expected.
	      Default is current dir.

       -nowakeup
	      Don't wake up even if the vm-file is there. Suspend still works.
	      Default is to wake up using the vm-file if it is there.

       -qemu <qemu>
	      The qemu variation to use. It can be qemu or kvm.
	      Default is qemu.

       qemu-options
	      Use qemu-options for the launch of qemu. See qemu(1) for further details.

FILES

       none

ENVIRONMENT VARIABLES

       none

EXAMPLES

       To use the suspend file 'Debian 3.1' and store/search it in the '/qemu' dir:

       qemuctl -suspend-file "Debian 3.1" -suspend-dir "/qemu" -boot c -hda hda.raw

       Alternativly you can run it with default suspend filenames:

       qemuctl -boot c -hda hda.raw

AUTHORS

       Peter Rustler

SEE ALSO

       qemu(1) qemu-launcher(1)

Peter Rustler							       0.0.1								qemuctl(1)

SYSTEMD-SUSPEND.SERVICE(8)				      systemd-suspend.service					SYSTEMD-SUSPEND.SERVICE(8)

NAME

       systemd-suspend.service, systemd-hibernate.service, systemd-hybrid-sleep.service, systemd-suspend-then-hibernate.service, systemd-sleep -
       System sleep state logic

SYNOPSIS

       systemd-suspend.service

       systemd-hibernate.service

       systemd-hybrid-sleep.service

       systemd-suspend-then-hibernate.service

       /lib/systemd/system-sleep

DESCRIPTION

       systemd-suspend.service is a system service that is pulled in by suspend.target and is responsible for the actual system suspend.
       Similarly, systemd-hibernate.service is pulled in by hibernate.target to execute the actual hibernation. Finally,
       systemd-hybrid-sleep.service is pulled in by hybrid-sleep.target to execute hybrid hibernation with system suspend and pulled in by
       suspend-then-hibernate.target to execute system suspend with a timeout that will activate hibernate later.

       Immediately before entering system suspend and/or hibernation systemd-suspend.service (and the other mentioned units, respectively) will
       run all executables in /lib/systemd/system-sleep/ and pass two arguments to them. The first argument will be "pre", the second either
       "suspend", "hibernate", "hybrid-sleep", or "suspend-then-hibernate" depending on the chosen action. Immediately after leaving system
       suspend and/or hibernation the same executables are run, but the first argument is now "post". All executables in this directory are
       executed in parallel, and execution of the action is not continued until all executables have finished.

       Note that scripts or binaries dropped in /lib/systemd/system-sleep/ are intended for local use only and should be considered hacks. If
       applications want to react to system suspend/hibernation and resume, they should rather use the Inhibitor interface[1].

       Note that systemd-suspend.service, systemd-hibernate.service, and systemd-hybrid-sleep.service systemd-suspend-then-hibernate.service
       should never be executed directly. Instead, trigger system sleep states with a command such as "systemctl suspend" or similar.

       Internally, this service will echo a string like "mem" into /sys/power/state, to trigger the actual system suspend. What exactly is written
       where can be configured in the "[Sleep]" section of /etc/systemd/sleep.conf or a sleep.conf.d file. See systemd-sleep.conf(5).

OPTIONS

       systemd-sleep understands the following commands:

       -h, --help
	   Print a short help text and exit.

       --version
	   Print a short version string and exit.

       suspend, hibernate, hybrid-sleep, suspend-then-hibernate
	   Suspend, hibernate, suspend then hibernate, or put the system to hybrid sleep.

SEE ALSO

       systemd-sleep.conf(5), systemd(1), systemctl(1), systemd.special(7), systemd-halt.service(8)

NOTES

	1. Inhibitor interface
	   https://www.freedesktop.org/wiki/Software/systemd/inhibit

systemd 237														SYSTEMD-SUSPEND.SERVICE(8)