utilize hypervisor property for effecter
The BootMode property is tied to the pvm_stop_at_standby BIOS attribute.
The user utilizes BootMode (via a Redfish or IPMI interface) to tell the
firmware the expectation of the boot. It is not meant as an action for
the host (i.e. move from one state to another).
This commit moves PLDM over to monitoring the hypervisor object and the
RequestedHostTransition property on that object to know when to set this
effecter.
A series of commits under this topic are transitioning the external
interfaces over to this concept:
https://gerrit.openbmc-project.xyz/q/topic:%22hyp-state%22+(status:open%20OR%20status:merged)
Tested:
- Built image with all related changes and verified hypervisor state
correctly tracked with BootProgress and that requesting an On
transition successfully made it to the hypervisor.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I26b6056f31cb3063c017af89451ec09b65ef719b
diff --git a/configurations/host/dbus_to_host_effecter.json b/configurations/host/dbus_to_host_effecter.json
index ff7141f..3b4b424 100644
--- a/configurations/host/dbus_to_host_effecter.json
+++ b/configurations/host/dbus_to_host_effecter.json
@@ -11,12 +11,12 @@
"effecters": [
{
"dbus_info": {
- "object_path": "/xyz/openbmc_project/control/host0/boot",
- "interface": "xyz.openbmc_project.Control.Boot.Mode",
- "property_name": "BootMode",
+ "object_path": "/xyz/openbmc_project/state/hypervisor0",
+ "interface": "xyz.openbmc_project.State.Host",
+ "property_name": "RequestedHostTransition",
"property_type": "string",
"property_values": [
- "xyz.openbmc_project.Control.Boot.Mode.Modes.Regular"
+ "xyz.openbmc_project.State.Host.Transition.On"
]
},
"state" : {