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

Mon Jun 16 18:10:10 UTC 2014
Periko Support <pheriko.support at gmail.com>

On Mon, Jun 16, 2014 at 10:55 AM, Konrad Rzeszutek Wilk
<konrad.wilk at oracle.com> wrote:
> On Mon, Jun 16, 2014 at 10:51:54AM -0700, Periko Support wrote:
>> On Mon, Jun 16, 2014 at 10:46 AM, Periko Support
>> <pheriko.support at gmail.com> wrote:
>> > On Mon, Jun 16, 2014 at 10:37 AM, Konrad Rzeszutek Wilk
>> > <konrad.wilk at oracle.com> wrote:
>> >> On Mon, Jun 16, 2014 at 10:21:45AM -0700, Periko Support wrote:
>> >>> ---------------------------------------
>> >>> So if I understand you correct - in 5.9 you did not see this, but
>> >>> in 6.5 you do?
>> >>> --------------------------------------
>> >>>
>> >>> Yes, just with centos 6.5 dom-u.
>> >>>
>> >>> But none of both vm's run.
>> >>
>> >> Please do not top post.
>> >> .. snip..
>> >> .. snip..
>> >>> >> 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!
>> >>
>> >>
>> >>
>> >> Ah, that is because you do not have xen-blkfront  loaded in your initrd.
>> >> Somehow it thinks it is called 'xenblk'. If you recreate your initrd
>> >> (either dracut or mkinitrd) make sure you specify that you want to
>> >> have the 'xen-blkfront' driver as part of it. The usual parameter
>> >> is '--add' or such.
>> >>
>> >> How did you generate your initrd?
>> >> _______________________________________________
>> >> CentOS-virt mailing list
>> >> CentOS-virt at centos.org
>> >> http://lists.centos.org/mailman/listinfo/centos-virt
>> >
>> > No, I'm using the instructions from xen4centos project. Nothing manually.
>> >
>> > U mention 2 things:
>> >
>> > For centos6 is normal the error, I have to connect to my console using
>> > other methods and see if centos6 dom-u is running, I will let u know.
>> > 2nd u mention that we need a module xen-blkfront for centos5 dom-u,
>> > hope the developers read this and fix this asap.
>> >
>> > Thanks.
>>
>> If u need info from me, let me know, because this happen in both
>> servers with different year of manufacturing.
>> and different centos version 5.9/6.0.
>
> Huh?
>
> You do not need any developers. You just need to regenerate your
> initrd to have extra drivers. That is it.
>
>
>>
>> Thanks for your time!!!
>> _______________________________________________
>> CentOS-virt mailing list
>> CentOS-virt at centos.org
>> http://lists.centos.org/mailman/listinfo/centos-virt
> _______________________________________________
> CentOS-virt mailing list
> CentOS-virt at centos.org
> http://lists.centos.org/mailman/listinfo/centos-virt

Understand that, but if exist something to be done to have the fix for
the whole community will be better, don't u think?