/openbmc/phosphor-state-manager/ |
H A D | hypervisor_state_manager.hpp | 31 class Hypervisor : public HypervisorInherit class 34 Hypervisor() = delete; 35 Hypervisor(const Hypervisor&) = delete; 36 Hypervisor& operator=(const Hypervisor&) = delete; 37 Hypervisor(Hypervisor&&) = delete; 38 Hypervisor& operator=(Hypervisor&&) = delete; 39 ~Hypervisor() override = default; 41 /** @brief Constructs Hypervisor State Manager 46 Hypervisor(sdbusplus::bus_t& bus, const char* objPath) : in Hypervisor() function in phosphor::state::manager::Hypervisor 67 /** @brief Check if BootProgress change affects hypervisor state [all …]
|
H A D | hypervisor_state_manager.cpp | 28 server::Host::Transition Hypervisor::requestedHostTransition(Transition value) in requestedHostTransition() 30 info("Hypervisor state transition request of {TRAN_REQUEST}", in requestedHostTransition() 36 error("Hypervisor state only supports a transition to On"); in requestedHostTransition() 42 // which is responsible for propagating the On request to the hypervisor in requestedHostTransition() 47 server::Host::HostState Hypervisor::currentHostState(HostState value) in currentHostState() 52 info("Change to Hypervisor State: {HYP_STATE}", "HYP_STATE", value); in currentHostState() 57 server::Host::HostState Hypervisor::currentHostState() const in currentHostState() 62 void Hypervisor::updateCurrentHostState(std::string& bootProgress) in updateCurrentHostState() 88 // set hypervisor state to off in updateCurrentHostState() 93 void Hypervisor::bootProgressChangeEvent(sdbusplus::message_t& msg) in bootProgressChangeEvent()
|
H A D | meson.options | 11 'hypervisor-busname', 13 value: 'xyz.openbmc_project.State.Hypervisor', 14 description: 'The Hypervisor DBus busname to own.', 18 'hypervisor-objpath', 20 value: '/xyz/openbmc_project/state/hypervisor', 21 description: 'The hypervisor state manager Dbus root.',
|
H A D | hypervisor_state_manager_main.cpp | 15 // For now, we only have one instance of the hypervisor in main() 22 phosphor::state::manager::Hypervisor manager(bus, objPathInst.c_str()); in main()
|
/openbmc/docs/designs/ |
H A D | power-systems-memory-preserving-reboot.md | 9 On POWER based servers, a hypervisor firmware manages and allocates resources to 10 the logical partitions running on the server. If this hypervisor encounters an 19 from the hypervisor memory. 41 - **Hypervisor**: A hypervisor (or virtual machine monitor, VMM) is a computer 43 [read more](https://en.wikipedia.org/wiki/Hypervisor) 46 faults in hypervisor. 51 - **Terminate Immediate (TI)**: A condition when the hypervisor encountered a 81 memory preserved reboot. Once the system finished booting, the hypervisor 96 - The hypervisor should send a special attention to BMC to notify about a severe 99 - BMC should receive special TI attention from hypervisor [all …]
|
/openbmc/bmcweb/redfish-core/lib/ |
H A D | hypervisor_system.hpp | 44 * @brief Retrieves hypervisor state properties over dbus 46 * The hypervisor state object is optional so this function will only set the 56 BMCWEB_LOG_DEBUG("Get hypervisor state information."); in getHypervisorState() 58 "xyz.openbmc_project.State.Hypervisor", in getHypervisorState() 71 BMCWEB_LOG_DEBUG("Hypervisor state: {}", hostState); in getHypervisorState() 129 * @brief Populate Actions if any are valid for hypervisor object 131 * The hypervisor state object is optional so this function will only set the 141 BMCWEB_LOG_DEBUG("Get hypervisor actions."); in getHypervisorActions() 167 // More then one hypervisor object is not supported and is an in getHypervisorActions() 177 "/redfish/v1/Systems/hypervisor/Actions/ComputerSystem.Reset"; in getHypervisorActions() [all …]
|
/openbmc/phosphor-state-manager/service_files/ |
H A D | xyz.openbmc_project.State.Hypervisor.service | 2 Description=Phosphor Hypervisor State Manager 3 Before=mapper-wait@-xyz-openbmc_project-state-hypervisor.service 6 ExecStart=/usr/bin/phosphor-hypervisor-state-manager 9 BusName=xyz.openbmc_project.State.Hypervisor
|
/openbmc/phosphor-networkd/src/ibm/hypervisor-network-mgr-src/ |
H A D | hyp_network_manager_main.cpp | 7 "/xyz/openbmc_project/network/hypervisor"; 9 "xyz.openbmc_project.Network.Hypervisor"; 29 // Create hypervisor network manager dbus object in main() 32 // Create the hypervisor eth interface objects in main() 35 // Create the hypervisor system config object in main()
|
H A D | meson.build | 1 hyp_default_busname = 'xyz.openbmc_project.Network.Hypervisor' 4 input: 'xyz.openbmc_project.Network.Hypervisor.service.in', 5 output: 'xyz.openbmc_project.Network.Hypervisor.service',
|
H A D | xyz.openbmc_project.Network.Hypervisor.service.in | 2 Description=Hypervisor Network Manager 9 BusName=xyz.openbmc_project.Network.Hypervisor
|
/openbmc/openbmc/meta-ibm/recipes-phosphor/settings/phosphor-settings-manager/ |
H A D | HypervisorInterface-default-p10bmc.override.yml | 1 /xyz/openbmc_project/network/hypervisor: 7 /xyz/openbmc_project/network/hypervisor/eth0: 20 /xyz/openbmc_project/network/hypervisor/eth0/ipv4/addr0: 40 /xyz/openbmc_project/network/hypervisor/eth1: 53 /xyz/openbmc_project/network/hypervisor/eth1/ipv4/addr0:
|
/openbmc/qemu/docs/specs/ |
H A D | ppc-spapr-hcalls.rst | 2 sPAPR hypervisor calls 6 a set of hypervisor calls (a.k.a. hcalls) defined in the Linux on Power 9 which is what PowerVM, the IBM proprietary hypervisor, adheres to. 13 In addition to those calls, we have added our own private hypervisor 31 calls our private H_RTAS hypervisor call to pass the RTAS calls to QEMU. 53 PAPR and LoPAR provides a set of hypervisor calls to perform cacheable or
|
H A D | vmw_pvscsi-spec.rst | 14 The interface is based on a memory area shared between hypervisor and VM. 18 The registers area is used to raise hypervisor interrupts and issue device 20 commands from VM to hypervisor and to transfer messages produced by 21 hypervisor to VM. Data itself is transferred via virtual scatter-gather DMA.
|
H A D | virt-ctlr.rst | 6 guest kernel to send command to the host hypervisor. 20 This register allows the kernel to send the commands to the hypervisor.
|
/openbmc/pldm/oem/ibm/configurations/events/ |
H A D | oem_ibm_event_state_sensor.json | 10 "object_path": "/xyz/openbmc_project/network/hypervisor/eth0/ipv4/addr0", 24 "object_path": "/xyz/openbmc_project/network/hypervisor/eth1/ipv4/addr0", 38 "object_path": "/xyz/openbmc_project/network/hypervisor/eth0/ipv6/addr0", 52 "object_path": "/xyz/openbmc_project/network/hypervisor/eth1/ipv6/addr0",
|
/openbmc/openbmc-test-automation/lib/external_intf/ |
H A D | vmi_utils.robot | 52 ${resp}= Redfish.Patch /redfish/v1/Systems/hypervisor/EthernetInterfaces/${interface} 95 ... /redfish/v1/Systems/hypervisor/EthernetInterfaces/${interface} 118 ... /redfish/v1/Systems/hypervisor/EthernetInterfaces/${interface} 124 ... /redfish/v1/Systems/hypervisor/EthernetInterfaces/${interface} 139 ... /redfish/v1/Systems/hypervisor/EthernetInterfaces/${interface} 172 ${resp}= Redfish.Get /redfish/v1/Systems/hypervisor/EthernetInterfaces 194 ${resp}= Redfish.Get /redfish/v1/Systems/hypervisor/EthernetInterfaces 203 ... /redfish/v1/Systems/hypervisor/EthernetInterfaces/eth${i} 239 ... /redfish/v1/Systems/hypervisor/EthernetInterfaces/${interface} 245 ... /redfish/v1/Systems/hypervisor/EthernetInterfaces/${interface} [all …]
|
/openbmc/qemu/linux-user/ppc/ |
H A D | cpu_loop.c | 254 /* PowerPC 64 with hypervisor mode support */ in cpu_loop() 255 case POWERPC_EXCP_HDECR: /* Hypervisor decrementer exception */ in cpu_loop() 256 cpu_abort(cs, "Hypervisor decrementer interrupt " in cpu_loop() 264 /* PowerPC 64 with hypervisor mode support */ in cpu_loop() 265 case POWERPC_EXCP_HDSI: /* Hypervisor data storage exception */ in cpu_loop() 266 cpu_abort(cs, "Hypervisor data storage exception " in cpu_loop() 269 case POWERPC_EXCP_HISI: /* Hypervisor instruction storage excp */ in cpu_loop() 270 cpu_abort(cs, "Hypervisor instruction storage exception " in cpu_loop() 273 case POWERPC_EXCP_HDSEG: /* Hypervisor data segment exception */ in cpu_loop() 274 cpu_abort(cs, "Hypervisor data segment exception " in cpu_loop() [all …]
|
/openbmc/qemu/include/system/ |
H A D | hvf_int.h | 2 * QEMU Hypervisor.framework (HVF) support 20 #include <Hypervisor/Hypervisor.h> 23 #include <Hypervisor/hv.h>
|
/openbmc/qemu/tests/uefi-test-tools/UefiTestToolsPkg/Include/Guid/ |
H A D | BiosTablesTest.h | 3 point(s) in a MB-aligned structure to the hypervisor. 5 The hypervisor locates the MB-aligned structure based on the signature GUID 7 address(es) are retrieved, the hypervisor may perform various ACPI and SMBIOS 48 // value that the hypervisor should look for at each MB boundary, looping
|
/openbmc/qemu/tests/functional/ |
H A D | test_aarch64_xen.py | 3 # Functional test that boots a Xen hypervisor with a domU kernel and 21 Boots a Xen hypervisor with a Linux DomU kernel. 59 'files=xen-hypervisor-4.11-arm64_4.11.4%2B37-g3263f257ca-1_arm64.deb'), 70 'files=xen-hypervisor-4.14-arm64_4.14.0%2B80-gd101b417b7-1_arm64.deb'),
|
/openbmc/qemu/target/i386/hvf/ |
H A D | README.md | 1 # OS X Hypervisor.framework support in QEMU 3 …./hvf-all.c) are adapted from Veertu Inc's vdhh (Veertu Desktop Hosted Hypervisor) (last known loc…
|
/openbmc/bmcweb/redfish-core/include/generated/enums/ |
H A D | operating_system.hpp | 20 Hypervisor, enumerator 63 {OperatingSystemTypes::Hypervisor, "Hypervisor"},
|
/openbmc/qemu/docs/ |
H A D | glossary.rst | 96 Hypervisor chapter 99 The formal definition of an hypervisor is a program or API than can be used to 103 In the context of QEMU, an hypervisor is an API, provided by the Host OS, 236 or it may work with a hypervisor such as KVM, Xen or Hypervisor.Framework to 272 system calls, but targeting an hypervisor, which happens to be QEMU in our 274 minimizing the amount of interactions between a guest VM and its hypervisor.
|
/openbmc/qemu/docs/system/i386/ |
H A D | hyperv.rst | 16 compatible hypervisor and use Hyper-V specific features. 32 When any set of the Hyper-V enlightenments is enabled, QEMU changes hypervisor 42 hypervisor. It is known that some Windows versions will do this even when they 43 see 'hypervisor' CPU flag. 53 hypervisor. A special value 0xffffffff indicates "never notify". 113 implements TLB shoot-down through hypervisor enabling the optimization. 120 through APIC requires more than one access (and thus exit to the hypervisor). 148 the hypervisor) until it is ready to switch to the new one. This, in conjunction 163 hypervisors making L2 exits to the hypervisor faster. The feature is Intel-only. 251 guest without the need to exit to L1 (Hyper-V) hypervisor. While the feature is
|
/openbmc/qemu/docs/about/ |
H A D | index.rst | 11 hypervisor such as KVM, Xen or Hypervisor.Framework to allow the
|