Document that runtime changes may be lost after S4 suspend

This commit is contained in:
Jiri Denemark 2013-05-31 18:00:48 +02:00
parent 2136327e23
commit fae2505eee
2 changed files with 14 additions and 0 deletions

View File

@ -2472,6 +2472,13 @@ error:
* Dependent on hypervisor used, this may require a * Dependent on hypervisor used, this may require a
* guest agent to be available, e.g. QEMU. * guest agent to be available, e.g. QEMU.
* *
* Beware that at least for QEMU, the domain's process will be terminated
* when VIR_NODE_SUSPEND_TARGET_DISK is used and a new process will be
* launched when libvirt is asked to wake up the domain. As a result of
* this, any runtime changes, such as device hotplug or memory settings,
* are lost unless such changes were made with VIR_DOMAIN_AFFECT_CONFIG
* flag.
*
* Returns: 0 on success, * Returns: 0 on success,
* -1 on failure. * -1 on failure.
*/ */

View File

@ -1680,6 +1680,13 @@ hypervisor driver and 0 should be used.).
Note that this command requires a guest agent configured and running in the Note that this command requires a guest agent configured and running in the
domain's guest OS. domain's guest OS.
Beware that at least for QEMU, the domain's process will be terminated when
target disk is used and a new process will be launched when libvirt is asked
to wake up the domain. As a result of this, any runtime changes, such as
device hotplug or memory settings, are lost unless such changes were made
with I<--config> flag.
=item B<dompmwakeup> I<domain> =item B<dompmwakeup> I<domain>
Wakeup a domain from pmsuspended state (either suspended by dompmsuspend or Wakeup a domain from pmsuspended state (either suspended by dompmsuspend or