similar to: Do I need a xenU initrd image?

Hi How do I make an initrd for xen. I''m trying to boot rhel3 in fc4, and it keeps getting stuck at Freeing unused kernel memory. I''ve created the device files, but it still doesn''t boot up. I''m pretty sure that the solution lies in makeing an initrd file. Currently my xenU kernel is 2.6.11-1.1369_FC4xen0. Can someone please tell me how to do this? Many

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

Mm, I have a big Quad-Opteron.. thing.. that I''m trying to get Xen onto. I''ve used the 3.0.2 binary-install mode, updated menu.lst as per the README, but I need an initrd which contains the HP cciss RAID driver, and no Xen initrd image was installed into /boot. Now I notice xen-3.0.2-2-install/install/lib/modules/2.6.16-xen/kernel/drivers /block/cciss.ko But I

Folks, Mercurial is selectable as an installation in OpenSUSE 10.3 YAST. I have done the following: hg clone http://xenbits.xensource.com/xen-unstable.hg hg clone http://xenbits.xensource.com/linux-2.6.18-xen.hg make dist sh ./install.sh I tried running the following to create the initrd but it failed: Depending on your config, you may need to use ''mkinitrd'' to

Hi all, I''m trying to install Xen. I''m compiling from source (3.1.3 ) on a FC8 system. Compilation completed with no errors. Now I''m trying to make the grub configuration and I need to create the initrd image. The command I use is the following: /sbin/mkinitrd /boot/initrd-2.6.18-xen.img 2.6.18.8-xen It results to the following error: No module ata_generic found for

Hi, had a few problems with using xen: First: built a xen from source (tgz) and make dist ... then made initrd with mkinitrd and modules=all in the mkinitrd.conf -> initrd.img was 14mb and set it up in the grub with module /initrd.... on boot it loads the initrd like: Loading ramdisk into ram .... done but then NO MODULES in the initrd are being loaded by the kernel, though initrd

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 "

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

> I''m guessing that the initrd created for dom0 in general > won''t work for > domU domains. I''m not sure what to do about that. If this is a -xen kernel, we should create a an initrd that can be used by both dom0 and domU, i.e. it has the necessary hardware drivers, but also the front end drivers. Aren''t there various differences between different

Hi, anyone to point me URL on initrd.img creating? I have custom kernel and want to create initrd.img for install media. mkinitrd /tmp/initrd.img 2.6.18-8.1.14.el5.hrb -v -f create unusable file for install media. Thanks, David

Hi, Any one know how the Centos 5 kickstart initrd.img was built? I'll be very appreciated if any light can be shed on this topic. The basic problem to be solved here is: how to build a custom vmlinuz+initrd.img for Centos 5 kickstart with my own custom built kernel? I am not sure mkinitrd is the right tool for this purpose? If do, which are the modules I should include with

Hello I have error virt-v2v: error: unable to rebuild initrd (/boot/initramfs-4.2.3-300.fc23.x86_64.img) because mkinitrd or dracut was not found in the guest My physical machine run on fedora23 Boot on usb made from virt-p2v-livecd-1.32.0.fc23.iso <http://oirase.annexia.org/virt-p2v/virt-p2v-livecd-1.32.0.fc23.iso> Log joined to this mail Do you have this problem ?

Hi, I migrated a physical CentOS 4.8 server into a VM on a CentOS 5 KVM host. Everything works fine, I even can use the paravirt drivers for network and disk. However the required kernel modules are not put into initrd somehow. Of course I can call "mkinitrd --with virtioblk ..." manually but that's too easy to forget. I searched the web but I didn't find any similar

Greetings list! Because of the sheer number of box (re)installations we do that have a CentOS base, I've converted our provisioning process to PXE. However, I've found that an alarming number of motherboards are coming with the Realtek RTL8168 ethernet controller onboard. When the system boots, it cannot find an ethernet controller and the installer process hangs. I made a new initrd

Here is the usage for Fedora usage: mkinitrd [--version] [-v] [-f] [--preload <module>] [--omit-scsi-modules] [--omit-raid-modules] [--omit-lvm-modules] [--with=<module>] [--image-version] [--fstab=<fstab>] [--nocompress] [--builtin=<module>] [--nopivot] <initrd-image> <kernel-version> (ex: mkinitrd /boot/initrd-2.2.5-15.img

OK sorry to hammer the list but one more question - having almost got the drives mirrored and happy - since I have created a custom initrd that has the raid1 drivers in it, do I now have to tell yum to ignore kernel updates? Will the stock kernel render me unbootable? Actually I am not 100% sure the initrd I created # mkinitrd -f --preload=raid1 /mnt/tmp/initrd-`uname -r`.img `uname -r` is

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

I converted a physical maschine running CentOS 4.6 to a Xen VM on a CentOS 5 host. Almost everything was running when I decided to rsync /lib and /usr a while later in order to get updated files and get the one or two non-working programs to work. There are differences because of the xenU kernel I didn't think about. I forgot to exclude rpm database and /lib/modules. Because the synced

Hi, I hope I''m right here. If not then please point me in the right direction. My problem in short: I have problems using (pinning, mmu_update) physical pages from 0x900000 to 0xB1000 usualy. I''m writing my own little amd64 64bit toy kernel (based on Mini-OS as starting point) for xen and I run into problems with the way the start of day sets up the physical pages. My kernel

While using mkinitrd on debian sarge, it gives the following error: mkinitrd -v -f --with=aacraid --with=sd_mod --with=scsi_mod initrd-2.6.16-xen.img 2.6.16-xen /usr/sbin/mkinitrd: illegal option -- v $Id: mkinitrd,v 1.201 2004/05/16 22:00:48 herbert Exp $ Usage: /usr/sbin/mkinitrd [OPTION]... <-o outfile> [version] Options: -d confdir Specify an alternative configuration directory.