NuKVM/libvirt
3
0
Fork 0
mirror of https://github.com/libvirt/libvirt.git synced 2025-02-25 18:55:26 -06:00
Code Issues Packages Projects Releases Wiki Activity

Remove powerMgmt_valid field from capabilities struct

Browse Source 
If we ensure that virNodeSuspendGetTargetMask always resets
*bitmask to zero upon failure, there is no need for the
powerMgmt_valid field.

* src/util/virnodesuspend.c: Ensure *bitmask is zero upon
  failure
* src/conf/capabilities.c, src/conf/capabilities.h: Remove
  powerMgmt_valid field
* src/qemu/qemu_capabilities.c: Remove powerMgmt_valid
This commit is contained in:
Daniel P. Berrange
2011-11-29 14:50:04 +00:00
parent f5272027c3
commit f1f28611f1
5 changed files with 24 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/formatcaps.html.in
View File

@@ -74,12 +74,9 @@ BIOS you will see</p>
description). Further, the power management features
supported by the host are shown, such as Suspend-to-RAM (S3),
Suspend-to-Disk (S4) and Hybrid-Suspend (a combination of S3
and S4). In case the query for power
management features succeeded but the host does not support
and S4). In case the host does not support
any such feature, then an empty &lt;power_management/&gt;
tag will be shown. Otherwise, if the query itself failed, no
such tag will be displayed (i.e., there will not be any
power_management block or empty tag in the XML).</p>
tag will be shown. </p>
<p>The second block (in blue) indicates the paravirtualization
support of the Xen support, you will see the os_type of xen
to indicate a paravirtual kernel, then architecture