HP Integrity Superdome SX2000 HP Insight Manager WBEM Provider Events Referenc - Page 92

Event ID Event Severity 11604 Error 11605 Error 11607 Error 11696 Error 11700 Error 11702 Error 11703 Error 11705 Error 11706 Error 11707 Error 11708 Error 11709 Error Event Description Memory locking failed. The data is the size of the memory block which could not be locked. Probable Cause: This can be caused by insufficient physical memory. Recommended Action: Reduce memory usage by other programs, add physical memory, or configure the guest to use less memory. WBEM EventID: 4958. WBEM ProviderName: FPL_IndicationProvider. The minimum number of processors required is more than the number available. The data is the number of available processors. Probable Cause: The number of physical processors is too few to run the guest as configured. Recommended Action: Add processors or reconfigure the guest to use fewer processors. WBEM EventID: 4959. WBEM ProviderName: FPL_IndicationProvider. The guest operating system performed an operation which could not be handled by the virtual machine. The virtual machine could not continue running the guest so it stopped. Probable Cause: The guest detected an error and could not continue. Recommended Action: See the HPVM guest operation log for additional information. WBEM EventID: 5133. WBEM ProviderName: FPL_IndicationProvider. Kernel driver failed to lock memory. Probable Cause: Kernel driver was unable to lock memory pages Recommended Action: Possibly insufficient physical memory. Add memory or reduce size of guest. WBEM EventID: 5134. WBEM ProviderName: FPL_IndicationProvider. The code which initializes the MMIO/IOP map found that the table already contained information. Probable Cause: An incorrect calling sequence has occurred or an image is corrupt. Recommended Action: If this continues to occur, reinstall the software. If this does not fix the problem contact your HP support representative. WBEM EventID: 5135. WBEM ProviderName: FPL_IndicationProvider. An attempt was made to add a PCI bus with a number greater than the maximum allowed. Probable Cause: Improper configuration Recommended Action: Check the configuration and set all bus numbers to supported values. WBEM EventID: 5136. WBEM ProviderName: FPL_IndicationProvider. The configured CPU generation is not supported. Probable Cause: The configuration contains an unsupported CPU generation Recommended Action: Modify the configuration to use a supported CPU generation. WBEM EventID: 5137. WBEM ProviderName: FPL_IndicationProvider. An ISA UART was created without a data structure. A PCI UART structure exists. Probable Cause: The ISA UART code was called when a PCI UART structure and no ISA UART structure were created. Recommended Action: Verify that the configuration contains the correct UART type. WBEM EventID: 5138. WBEM ProviderName: FPL_IndicationProvider. A TCGETS or TCSETS IOCTL failed. The errno status will be in a subsequent event. Probable Cause: The device is not configured or is not the proper type. Recommended Action: Check the configuration. WBEM EventID: 5139. WBEM ProviderName: FPL_IndicationProvider. A stat call on the PMAN failed. The next event contains the failure errno. Probable Cause: The device does not exist or is not available Recommended Action: Check the configuration and verify the device. WBEM EventID: 5140. WBEM ProviderName: FPL_IndicationProvider. The virtual machine driver could not be opened. Probable Cause: The virtual machine software is not properly installed or is not running Recommended Action: Restart the virtual machine. If this fails verify that it is properly installed. WBEM EventID: 5141. WBEM ProviderName: FPL_IndicationProvider. The virtual machine driver could not create a virtual machine. Probable Cause: The PMAN kernel has insufficient memory available to create a guest Recommended Action: Add memory or reduce memory use. WBEM EventID: 5142. WBEM ProviderName: FPL_IndicationProvider. 92 WBEM Provider Event Tables