Searched refs:hypervisor (Results 1 – 25 of 80) sorted by relevance
1234
3 Before=mapper-wait@-xyz-openbmc_project-state-hypervisor.service6 ExecStart=/usr/bin/phosphor-hypervisor-state-manager
52 ${resp}= Redfish.Patch /redfish/v1/Systems/hypervisor/EthernetInterfaces/${interface}97 ... /redfish/v1/Systems/hypervisor/EthernetInterfaces/${interface}120 ... /redfish/v1/Systems/hypervisor/EthernetInterfaces/${interface}126 ... /redfish/v1/Systems/hypervisor/EthernetInterfaces/${interface}141 ... /redfish/v1/Systems/hypervisor/EthernetInterfaces/${interface}174 ${resp}= Redfish.Get /redfish/v1/Systems/hypervisor/EthernetInterfaces196 ${resp}= Redfish.Get /redfish/v1/Systems/hypervisor/EthernetInterfaces205 ... /redfish/v1/Systems/hypervisor/EthernetInterfaces/eth${i}241 ... /redfish/v1/Systems/hypervisor/EthernetInterfaces/${interface}247 ... /redfish/v1/Systems/hypervisor/EthernetInterfaces/${interface}[all …]
9 On POWER based servers, a hypervisor firmware manages and allocates resources to10 the logical partitions running on the server. If this hypervisor encounters an19 from the hypervisor memory.41 - **Hypervisor**: A hypervisor (or virtual machine monitor, VMM) is a computer46 faults in hypervisor.51 - **Terminate Immediate (TI)**: A condition when the hypervisor encountered a81 memory preserved reboot. Once the system finished booting, the hypervisor96 - The hypervisor should send a special attention to BMC to notify about a severe99 - BMC should receive special TI attention from hypervisor110 - Once the dump is generated, the hypervisor should notify BMC.[all …]
26 hypervisor = 'H', enumerator32 hypervisor = 0x82, enumerator
2 sPAPR hypervisor calls6 a set of hypervisor calls (a.k.a. hcalls) defined in the Linux on Power9 which is what PowerVM, the IBM proprietary hypervisor, adheres to.13 In addition to those calls, we have added our own private hypervisor31 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
6 guest kernel to send command to the host hypervisor.20 This register allows the kernel to send the commands to the hypervisor.
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 device20 commands from VM to hypervisor and to transfer messages produced by21 hypervisor to VM. Data itself is transferred via virtual scatter-gather DMA.
97 A hypervisor reads the CS segment base and IP value. The CS segment99 the hypervisor must left shift the value of the CS segment base by 16109 This describes the guest RAM area where the hypervisor should inject the118 This describes the guest RAM area where the hypervisor should install a
8 directly to virtual processors without hypervisor assistance.15 the hypervisor provides identical interfaces and similar22 the hypervisor provides new interfaces to manage the XIVE control65 VMs running under a L1 hypervisor (KVM on pSeries). In that case, the66 hypervisor will not advertise the KVM capability and QEMU will use the190 contains a list of priorities that the hypervisor has reserved for227 In the case of a ``pseries`` machine, QEMU acts as the hypervisor and only
1 console-id = hypervisor
3 console-id = hypervisor
16 PACKAGECONFIG[ibm-hypervisor-cert] = "-Dca-cert-extension=enabled,-Dca-cert-extension=disabled"28 …${@bb.utils.contains('PACKAGECONFIG', 'ibm-hypervisor-cert', 'bmc-vmi-ca-manager.service', '', d)}…
1 subdir('hypervisor-network-mgr-src')
1 PACKAGECONFIG:append:ibm-enterprise = " ibm-hypervisor-cert"
11 'hypervisor-busname',18 'hypervisor-objpath',20 value: '/xyz/openbmc_project/state/hypervisor',21 description: 'The hypervisor state manager Dbus root.',
11 capable of acting as a hypervisor OS, providing, on that role, nested32 PowerVM hypervisor with VIOS managing LPARs.116 running the IBM PowerVM hypervisor with LPARs.119 hypervisor and non-Linux guests in mind, you should use the virtio counterparts180 on hypervisor mode on a Power processor (this function was restricted to181 PowerVM, the IBM proprietary hypervisor).202 KVM-HV uses the hypervisor mode of more recent Power processors, that allow209 hypervisor mode of the Power CPU, it wasn't possible to run KVM-HV on a guest.275 pool of secure memory which cannot be accessed by the hypervisor.279 memory, where it cannot be eavesdropped by a compromised hypervisor.
1 inc_dir = include_directories('../../../src/ibm/hypervisor-network-mgr-src/')
5 guest's memory and other state, meaning that a compromised hypervisor8 protection from a compromised hypervisor. This is obviously
8 aimed at a particular use case of loading hypervisor guests. This is27 In the above example the Xen hypervisor is loaded by the -kernel
21 # IBM systems track the state of the hypervisor so bring24 RRECOMMENDS:${PN}-host:append = " ${PN}-hypervisor"
16 compatible hypervisor and use Hyper-V specific features.32 When any set of the Hyper-V enlightenments is enabled, QEMU changes hypervisor42 hypervisor. It is known that some Windows versions will do this even when they43 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 conjunction163 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
25 hypervisor to perform functions on behalf of a guest, there is architectural28 the hypervisor to satisfy the requested function.48 The guest policy is passed as plaintext. A hypervisor may choose to read it,113 guest register state is encrypted and cannot be updated by the VMM/hypervisor,120 - Requires in-kernel irqchip - the burden is placed on the hypervisor to235 Since the memory contents of a SEV guest are encrypted, hypervisor access to237 then a hypervisor can use the DEBUG_DECRYPT and DEBUG_ENCRYPT commands to access
69 nlohmann::json::object_t hypervisor; in handleSystemCollectionMembers() local70 hypervisor["@odata.id"] = "/redfish/v1/Systems/hypervisor"; in handleSystemCollectionMembers()71 membersArray.emplace_back(std::move(hypervisor)); in handleSystemCollectionMembers()
21 description: 'ibm-oem: Enable the hypervisor network manager',
5 (PVMs) are encrypted or inaccessible to the hypervisor, effectively19 Running PVMs requires using the KVM hypervisor.