Displaying 20 results from an estimated 30000 matches similar to: "mtpbase"
2005 Sep 07
1
mkinitrd
I''ve compiled xen without any problems. but now i have to create an initrd file. When i use the command mkinitrd (without any options) the i''ve got some errors:
# mkinitrd
Root device: /dev/sda3 (mounted on / as reiserfs)
Module list: ata_piix mptbase mptscsih qla2300 reiserfs
Kernel image: /boot/vmlinuz-2.6.11.12-xen0
Initrd image: /boot/initrd-2.6.11.12-xen0
Shared
2005 Oct 10
1
mkinitrd-4.2.1.3-1 unsuitable for 2.6.13+ kernels?
Hi all,
I have a Opteron-machine with the MPT SCSI-controller (Symbios 53c1030).
At least in i386-mode, mkinitrd does not seem to build a usable initrd
for 2.6.13.x (.3 tested) with this kernel. With 2.6.12.6 it works fine.
I have not tested this in x86_64 -mode yet.
The symptom is that mptbase and mptscsih load, but mptscsih does not
discover any controllers nor drives, and things like
2011 Oct 24
1
dell: mtpbase: ioc fault state?
Hi List,
Any ideas what is wrong with controller? It is running latest 5.x
series of centos and driver spills out following warnings at random
times:
mptbase: ioc0: WARNING - IOC is in FAULT state (1600h)!!!
mptbase: ioc0: WARNING - Issuing HardReset from mpt_fault_reset_work!!
mptbase: ioc0: Initiating recovery
mptbase: ioc0: WARNING - IOC is in FAULT state!!!
mptbase: ioc0: WARNING -
2006 Jan 25
0
[Xen kernel panic error] on kernel 2.6.12.6
# Error facing :------
kernel panic - : not syncying , VFS : Unable to mount root fs on
un-known block (3,5)
------------------------------------------------------------------------------------------------------
# Machine and kernel architecture:-----------
Default Working installed kernel - vmlinux-2.6.5-7.97
Xen dom0 kernel - vmlinuz-2.6.12.6-xen0
2005 Dec 13
3
is my initramdisk right? also getting ''Error opening /dev/console'' error
Hello,
I am getting kernel panic while trying to xm create a domU.
Xen version 3.0
Linux kernel 2.6.12.6
Grub entry for dom0:
title Xen 3.0 / XenLinux 2.6
kernel /boot/xen- 3.0.gz console=vga
module /boot/vmlinuz-2.6-xen0 root=LABEL=/ ro console=tty0
module /boot/initrd-2.6.12.6-xen0.img
For domU, my xm file contains:
kernel = "/boot/vmlinuz-2.6.12.6-xenU "
2005 Oct 01
2
Problem getting x86_64 dom0 to boot on a FC4 machine
I''m struggling to get Xen to boot on a FC4 Opteron box. I''ve included the
tail of the boot log below [1]. I suspect that the problems relates to the
software RAID 1 root and boot partitions, and how it relates to the initrd
image. The RAID volumes fail to mount.
I compiled the Xen snapshot from the 23rd September, and the only change
I''ve made is to enable the
2006 Jun 07
0
(no subject)
All,
I am running xen3.0.2 on CentOS4.2, and get this error when trying to
boot Xen kernel(domain0)
......
Creating root device
Mounting root filesystem
mount: error 6 mounting ext3
mount: error 2 mounting none
Switching to new root
switchroot: mount failed: 22
umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempting to kill init!
>Then system reboot.In grub.conf,I have changed
2005 Jan 27
2
booting erro on FC3
I''m a newbie. :)
I followed the steps written by Jerone Young:
http://sourceforge.net/mailarchive/message.php?msg_id=10562241
but i found an error at the 17th step:
17. mkinitrd /boot/initrd-2.6.10-xen0.img 2.6.10-xen0
it said:"No module ata_piix found for kernel 2.6.10-xen0, aborting."
so I commented the line of "module /boot/initrd-2.6.10-xen0.img" in the
2008 May 28
0
[PATCH] ia64/xen: a recipe for using xen/ia64 with pv_ops.
Recipe for useing xen/ia64 with pv_ops domU.
Signed-off-by: Akio Takebe <takebe_akio at jp.fujitsu.com>
Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp>
Cc: Randy Dunlap <randy.dunlap at oracle.com>
---
Documentation/ia64/xen.txt | 183 ++++++++++++++++++++++++++++++++++++++++++++
1 files changed, 183 insertions(+), 0 deletions(-)
create mode 100644
2008 May 28
0
[PATCH] ia64/xen: a recipe for using xen/ia64 with pv_ops.
Recipe for useing xen/ia64 with pv_ops domU.
Signed-off-by: Akio Takebe <takebe_akio at jp.fujitsu.com>
Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp>
Cc: Randy Dunlap <randy.dunlap at oracle.com>
---
Documentation/ia64/xen.txt | 183 ++++++++++++++++++++++++++++++++++++++++++++
1 files changed, 183 insertions(+), 0 deletions(-)
create mode 100644
2006 May 23
2
new initrd
Hi
Can anyone show me how to make a new initrd for a newly rolled kernel? I
have to install a 'custom' 2.6.14 kernel and i have build the kernel and
now just trying to build the initrd
cd /boot
mkinitrd initrd-2.6.14.img 2.6.14
No module mptbase found for kernel 2.6.14, aborting.
What am i doing wrong?
thanks
2004 Oct 09
0
iscsi boot xen0 initrd
In case it helps anyone, here''s a script I use to boot xen0 over iscsi
with an initrd using linux-iscsi and iscsi-init (both on sourceforge).
Some (or most) of it might be debian (sarge) specific though. The script
goes in /etc/mkinitrd/scripts and puts the bits and pieces in place. It
has to prepend stuff to /script in the resultant initrd so it does a few
funny things. Add your Ethernet
2005 Sep 22
1
LPFC support in Xen ?
Hi,
Afraid I dont have a very new system to try out Xen.. It''s an ia32 PIII
machine with 1GB memory (that''s gud i believe).
When I try to build the initrd image for my xen kernel, i get error
messages complaining about missing modules, so am trying to compile them on
my own.
Could find support for the remaining three, but am left with lpfcdd.ko.
Couldnt find an appropriate
2005 Jun 09
8
Xen and ReiserFS
I am unable to boot Dom0 on a machine with Reiser file systems. Reiser
support is built into the xen0 kernel. I have similar setup with ext3
file systems working just fine, so I don''t think it is a setup problem.
I have tried booting with and without and initrd file, booting with the
original Linux distro initrd file, etc, but nothing seems to work. I
recall seeing a thread about ReiserFS
2006 Mar 28
0
Segmentation Fault & Root /dev/ does not exist
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello List,
So I managed to get Xen 3.0.1 compiled and installed, but the machine
failed to boot from the Xen kernel. The server's physically located at
a Co-lo, so I'm having to rely on somebody on the other end to tell me
what it's doing and saying.
When I try to boot the -xen0 kernel, the screen fills up with
Segmentation Faults and
2006 Mar 30
2
linux-2.6-xen kernels and initrds
I have a question regarding the building of the unified xen kernel
(linux-2.6-xen) and the use of initrd. In the past I built both xen0
and xenU kernels; the xen0 default configurations had SCSI and Fusion
MPT support compiled into the kernel. Now, they are built as modules.
The problem is that I am unable to boot the xen kernel built that way,
even though I am building an initrd. I have
2006 Jun 13
17
switchroot mount failed
All,
I am running xen3.0.2 and xen unstable on RHEL 4, and get this error when
trying to boot Xen kernel(domain0)
......
Creating root device
Mounting root filesystem
mount: error 6 mounting ext3
mount: error 2 mounting none
Switching to new root
switchroot: mount failed: 22
umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempting to kill init!
Then system reboot.In grub.conf,I have
2006 Jun 13
17
switchroot mount failed
All,
I am running xen3.0.2 and xen unstable on RHEL 4, and get this error when
trying to boot Xen kernel(domain0)
......
Creating root device
Mounting root filesystem
mount: error 6 mounting ext3
mount: error 2 mounting none
Switching to new root
switchroot: mount failed: 22
umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempting to kill init!
Then system reboot.In grub.conf,I have
2005 Sep 12
3
Won''t boot to Xen, GRUB Problem
I am installing Xen on a remote server. I left the other kernels on the
grub.conf and made xen the default to boot from. The box didn''t boot into
Xen on reboot but I''m not sure why. Here is my Xen config file:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
#
2006 Mar 30
0
kernel-image naming with Xen
Hey there,
Earlier today I went to rebuild a Xen0 kernel and my modules_image
failed with an error based on the fact that my Xen0 image did not have
the standard kernel-image-XXX/linux-image-XXX name format. The error
output is at the bottom of this email. Previously it had worked fine,
only recently the maintainer (Kel) of the module source added some
restrictions to modules.control.in to look