Incorrect answers to xen KVM virtualization IPMI

Problem description:

Use the Dell r720 server to install the xen and KVM services. After creating and starting guest, and entering the system, the system runs normally. However, a failed prompt is displayed during startup, as shown below:

Prompt during xen domu startup

# Dmesg | grep PCI
PCI: Warning: cannot find a gap in the 32bit address range
PCI: unassigned devices with 32bit resource registers may break!
Allocating PCI resources starting at 400100000 (gap: 400100000: 400000)
PCI-DMA: using software bounce buffering for Io (swiotlb)
PCI: Fatal: No config space access function found
PCI: system does not support PCI
PCI: system does not support PCI
PCI: Max bus depth: 0 pci_try_num: 1
Pci_hotplug: PCI Hot Plug PCI core version: 0.5
Pciehp: PCI Express Hot Plug controller driver version: 0.4
Acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5

# Dmesg | grep IPMI

IPMI message handler version 39.2

IPMI system interface driver.

Ipmi_si: Adding default-specified KCS state machine

Ipmi_si: Trying default-specified KCS state machine at I/O address 0xca, slave address 0x0, IRQ 0

Ipmi_si: interface detection failed

Ipmi_si: Adding default-specified SMIC state machine

Ipmi_si: Trying default-specified SMIC state machine at I/O address 0xca9, slave address 0x0, IRQ 0

Ipmi_si: interface detection failed

Ipmi_si: Adding default-specified BT state machine

Ipmi_si: Trying default-specified BT state machine at I/O address 0xe4, slave address 0x0, IRQ 0

Ipmi_si: interface detection failed

Ipmi_si: unable to find any system interface (s)

650) This. width = 650; "src ="/e/u261/themes/default/images/spacer.gif "style =" Background: URL ("/e/u261/lang/ZH-CN/images/localimage.png") No-repeat center; Border: 1px solid # DDD; "alt =" spacer.gif "/> 650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M00/49/D1/wKiom1QbmsrTdZ5xAAKm2km44Eo176.jpg "Title =" qq 40919105349.jpg "alt =" wkiom1qbmsrtdz5xaakm2km44eo176.jpg "/>

Prompt during KVM guest startup

IPMI message handler version 39.2

IPMI system interface driver.

Ipmi_si: Adding default-specified KCS state machine

Ipmi_si: Trying default-specified KCS state machine at I/O address 0xca, slave address 0x0, IRQ 0

Ipmi_si: interface detection failed

Ipmi_si: Adding default-specified SMIC state machine

Ipmi_si: Trying default-specified SMIC state machine at I/O address 0xca9, slave address 0x0, IRQ 0

Ipmi_si: interface detection failed

Ipmi_si: Adding default-specified BT state machine

Ipmi_si: Trying default-specified BT state machine at I/O address 0xe4, slave address 0x0, IRQ 0

Ipmi_si: interface detection failed

Ipmi_si: unable to find any system interface (s)

650) This. width = 650; "src ="/e/u261/themes/default/images/spacer.gif "style =" Background: URL ("/e/u261/lang/ZH-CN/images/localimage.png") No-repeat center; Border: 1px solid # DDD; "alt =" spacer.gif "/> 650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M02/49/D3/wKioL1Qbm0Djn0aDAAOaNFdTFcw162.jpg "Title =" qq20140919105500.png "alt =" wkiol1qbm0djn0adaaoanfdtfcw162.jpg "/>

It has been half a month since I checked the information for this question. I joined the virtualization group for various Google searches and asked if I could not find the answer. Because it does not affect the use, I have struggled to give up searching for the question for many times, however, this rock cannot be placed in my heart.

······

The official Red Hat documents were highlighted at last.

Https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html-single/6.5_Technical_Notes/

• kernelComponent

• Typically, on platforms with no intelligent platform management interface (IPMI) hardware the user can see the following message the on the boot console and inDmesgLog:

  Could not set up I/O space

  This message can be safely ignored, unless the system really does have IPMI hardware. in that case, the message indicates that the IPMI hardware cocould not be initialized. in order to support advanced configuration and Power Interface (ACPI) opregion access to IPMI functionality early in the boot, The ipmi driver has been statically linked with the kernel image. this means that the IPMI driver is "loaded" whether or not there is any hardware. the ipmi driver will try to initialize the IPMI hardware, but if there is no IPMI hardware present on the booting platform, the driver will print error messages on the console and inDmesgLog. Some of these error messages do not identify themselves as having been issued by the IPMI driver, so they can appear to be serous, when they are harmless.

This article from the "Jin Ge tie Ma difei Yan blog", please be sure to keep this source http://bbotte.blog.51cto.com/6205307/1555049

Incorrect answers to xen KVM virtualization IPMI