[CentOS-virt] Centos 6.5 Xen Stock cannot run dom-u PCI: Fatal: - ipmi_si

Konrad Rzeszutek Wilk konrad.wilk at oracle.com
Mon Jun 16 17:15:33 UTC 2014


On Mon, Jun 16, 2014 at 08:42:49AM -0700, Periko Support wrote:
> I had a supermicro server SuperServer 1027R-WRF4+ and a old Dell PowerEdge 2950.
> 
> In both machines I setup centos 6.5, which is running
> 3.10.34-11.el6.centos.alt.x86_64.
> 
> I follow Xen4Cen wiki to setup Xen, I had other servers running Centos
> 5.x without issues.
> 
> Now, once I build my vm's dom-u centos 6.5/centos 5.9 both x64, I
> receive different erros, let me show u the message I receive in my
> console for centos 6.5 dum-u.
> 
> xl  console oerp-server
> PCI: Fatal: No config space access function found
> ipmi_si: Could not set up I/O space
> ipmi_si: Could not set up I/O space
> ipmi_si: Could not set up I/O space
> 
> Something related to ipmi in my server which is enable by default? can
> be, now what happen is I try to boot xentos 5.9 x64 dom-u:

So if I understand you correct - in 5.9 you did not see this, but
in 6.5 you do?

And the error is that some driver that looks to be built in
is telling you that it can't set up I/O space? Well, that is OK - if
it can't it cannot.

> 
> Brought up 1 CPUs
> checking if image is initramfs... it is
> Grant table initialized
> NET: Registered protocol family 16
> Brought up 1 CPUs
> PCI: setting up Xen PCI frontend stub
> ACPI: Interpreter disabled.
> Linux Plug and Play Support v0.97 (c) Adam Belay
> pnp: PnP ACPI: disabled
> xen_mem: Initialising balloon driver.
> usbcore: registered new driver usbfs
> usbcore: registered new driver hub
> PCI: System does not support PCI
> PCI: System does not support PCI
> NetLabel: Initializing
> NetLabel:  domain hash size = 128
> NetLabel:  protocols = UNLABELED CIPSOv4
> NetLabel:  unlabeled traffic allowed by default
> NET: Registered protocol family 2
> IP route cache hash table entries: 65536 (order: 7, 524288 bytes)
> TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
> TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
> TCP: Hash tables configured (established 262144 bind 65536)
> TCP reno registered
> audit: initializing netlink socket (disabled)
> type=2000 audit(1402907331.494:1): initialized
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
> Initializing Cryptographic API
> alg: No test for crc32c (crc32c-generic)
> ksign: Installing public key data
> Loading keyring
> - Added public key 691B840A64868995
> - User ID: CentOS (Kernel Module GPG key)
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> pci_hotplug: PCI Hot Plug PCI Core version: 0.5
> rtc: IRQ 8 is not free.
> Non-volatile memory driver v1.2
> Linux agpgart interface v0.101 (c) Dave Jones
> brd: module loaded
> Xen virtual console successfully installed as xvc0
> Event-channel device installed.
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
> ide-floppy driver 0.99.newide
> usbcore: registered new driver hiddev
> usbcore: registered new driver usbhid
> drivers/usb/input/hid-core.c: v2.6:USB HID core driver
> PNP: No PS/2 controller found. Probing ports directly.
> i8042.c: No controller found.
> mice: PS/2 mouse device common for all mice
> md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
> md: bitmap version 4.39
> TCP bic registered
> Initializing IPsec netlink socket
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> XENBUS: Device with no driver: device/vbd/51712
> XENBUS: Device with no driver: device/vif/0
> XENBUS: Device with no driver: device/console/0
> Initalizing network drop monitor service
> Write protecting the kernel read-only data: 506k
> Red Hat nash version 5.1.19.6 starting
> Mounting proc filesystem
> Mounting sysfs filesystem
> Creating /dev
> Creating initial device nodes
> Setting up hotplug.
> Creating block device nodes.
> Loading ehci-hcd.ko module
> Loading ohci-hcd.ko module
> Loading uhci-hcd.ko module
> USB Universal Host Controller Interface driver v3.0
> Loading jbd.ko module
> Loading ext3.ko module
> Loading xenblk.ko module
> XENBUS: Waiting for devices to initialise:
> 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s...
> XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3,
> remote state 1)
> Loading dm-mod.ko module
> device-mapper: uevent: version 1.0.3
> device-mapper: ioctl: 4.11.6-ioctl (2011-02-18) initialised: dm-devel at redhat.com
> Loading dm-log.ko module
> Loading dm-mirror.ko module
> Loading dm-zero.ko module
> Loading dm-snapshot.ko module
> Loading dm-mem-cache.ko module
> Loading dm-region_hash.ko module
> Loading dm-message.ko module
> Loading dm-raid45.ko module
> device-mapper: dm-raid45: initialized v0.2594l
> Scanning and configuring dmraid supported devices
> Scanning logical volumes
>   Reading all physical volumes.  This may take a while...
>   No volume groups found
> Activating logical volumes
>   Volume group "VolGroup00" not found
> Creating root device.
> Mounting root filesystem.
> mount: could not find filesystem '/dev/root'
> Setting up other filesystems.
> Setting up new root fs
> setuproot: moving /dev failed: No such file or directory
> no fstab.sys, mounting internal defaults
> setuproot: error mounting /proc: No such file or directory
> setuproot: error mounting /sys: No such file or directory
> Switching to new root and running init.
> unmounting old /dev
> unmounting old /proc
> unmounting old /sys
> switchroot: mount failed: No such file or directory
> Kernel panic - not syncing: Attempted to kill init!
> 
> Looks is not finding the dom-u disk.
> 
> In both cases I'm using almost the same settings:
> 
> name = "centos5"
> uuid = "5020979f-8dae-105d-df56-9fb28d377aa2"
> bootloader = "/usr/bin/pygrub"
> memory = 2048
> on_poweroff = "destroy"
> on_reboot = "restart"
> on_crash = "restart"
> disk = [ "tap:aio:/ext4/centos5/disk.img,xvda,w" ]
> vif = [ "mac=X:X:X:X:X:X,bridge=xenbr0,script=vif-bridge" ]
> 
> The main line of centos stock without Xen continue using kernel 2.6.x,
> but Xen is using the new line 3.x.
> 
> Anyone else with this issue?
> 
> Thanks for your time.
> _______________________________________________
> CentOS-virt mailing list
> CentOS-virt at centos.org
> http://lists.centos.org/mailman/listinfo/centos-virt


More information about the CentOS-virt mailing list