similar to: Problem getting x86_64 dom0 to boot on a FC4 machine

Basically the issue comes down to my Volume Groups not being found by this initrd, causing good ole kernel panic. initrd-2.6.12.6-xen3_12.1_rhel4.1.img [root@xen01 lvm]# uname -a Linux xen01.inside.***.com 2.6.9-22.0.2.ELsmp #1 SMP Thu Jan 5 17:13:01 EST 2006 i686 i686 i386 GNU/Linux [root@xen01 lvm]# cat /etc/redhat-release Red Hat Enterprise Linux ES release 4 (Nahant Update 2) Everything

Howdy folks, I''m trying to boot Xen 3.0 on a Centos 4(.2) system with root on a software raid1 volume. When booting the Xen kernel, ''raidautorun'' in the /init nash script fails to assemble either the root md or the raid5 md containing my LVM volumes. If I move root to /dev/hda1, the system boots fine. raidautorun still fails to assemble the md devices, but mdadm

When booting a CentOS4 domU, I''m getting some errors in the /etc/sysinit file. I''ve read that some edits are required in this file, but cannot find any specific references. Has anyone seen this before? Is there a workaround? EXT2-fs warning (device sda1): ext2_fill_super: mounting ext3 filesystem as ext2 VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel

Hi again I have a minimal Fedora Core 3 image running fine as domain 0 (thanks and sorry for the previous FAQ query) using both the standard install ramdisk image, and the FC3 ramdisk image downloaded from xen sourceforge. However, I can''t get it running in a non-zero domain. In brief, I have a full FC3 installed on /dev/hda1, which I typically use as my domain 0 OS. Then I have a

Hello, I have Xen running on an Ubuntu 8.04 LTS machine. This machine has been in production for a few months now. Up until recently, all the DomU machines have also been Ubuntu 8.04 machines. Recently, I tried creating a Debian Lenny machine. I use xen tools to create the DomU machines. Upon completion of creating the DomU with xen tools, I start the DomU using the [sanitized] command

Hi, in short: - EPIA MII6000E motherboard with CF-Card - Booting from network works with Linux Kernel 2.4.25 - Change to 2.6.15.4 doesn't work -- kernel panics: VFS: Cannot open root device "hde1" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncinc: VFS: Unable to mount root fs on unknown-block(0,0) in Detail: -

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greets all sorry for the posting but this one has me confused. I compiled Zaptel and am experiencing something strange. I followed the instructions on README.udevs to the tee, set permissions, etc. and I'm confused as to what gives. Zaptel compiled without a problem but no device was made.... [beta@staging ]# uname -a Linux xxx.xxx

Has anyone had issues starting xen0 on a md? I have installed it a few times now w/ and w/o raid. Anytime I have a raid1 mirror, Xen panics on boot when trying to mount /. It gets past waiting for /dev/md0 to appear. John _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Has anyone had issues starting xen0 on a md? I have installed it a few times now w/ and w/o raid. Anytime I have a raid1 mirror, Xen panics on boot when trying to mount /. It gets past waiting for /dev/md0 to appear. John _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hello again, I'm always not able to boot-up my CF-FileSystem. (It works with a 2.4.x Kernel!) See: http://syslinux.zytor.com/archives/2006-June/006942.html I dont't understand, why the kernel can't mount the root-fs on exit of "linuxrc". Before finising "linuxrc" I can work on it, start a "bash"-shell, do all sorts of linux-cmds on the root-fs...

Hi All, I am trying to evaluate whether centos-4.8 system container work on Fedora-19 machine or not. Host machine : Fedora 19 Guest (LXC container) : CentOS4 .8 For creation of of container i followed following steps, 1. Installed libvirt packages on fedora19 2. For installation of rootfs using yum, I have created the LOCAL YUM REPO using CentOS-4.8 ISO files

I'm trying to set-up a ContOS 7 DomU server. I have used the PXE set-up images like I normally would for earlier versions of CentOS. Here is my config file:- name      = "centos7" memory    = 2048 disk      = ['phy:/dev/xen6/centos7,xvda,w' ] vif = [ 'mac=xx:xx:xx:xx:xx:xx' ] kernel    = "/root/xen/centos7-64/vmlinuz" ramdisk   =

Hi, another issue I''m seeing with 3.0-rc2 and Xen is that there is an unexpectedly high amount of kernel reserved memory. I suspect that Linux allocates page table entries and corresponding data structures for the whole 6GB areas of the provided ''physical RAM map'' even though it has rather big unusable holes in it. [ 0.000000] BIOS-provided physical RAM map: [

Thought I would write some notes about how I got an APC BackUPS XS 1500 working with newhidups under Gentoo 2006.0. The specific issue here is the permissions on the device files used that libusb uses to access the USB hardware. I followed Peter Selinger's instructions at http://www.mscs.dal.ca/~selinger/ups/backups.html on getting newhidups going with an APC device. The sticking point for

Hi , I am ruuning Senmail with MailScanner on CentOS 4.4. It has updated to kernel 2.6.9-42.0.8.EL from its past kernel 2.6.9-42.0.3.EL. Now the Server can not boot up and gives the below error. mkrootdev: label / not found Mounting root filesystem mount: error 2 mouting ext3 switchroot: mount failed: 22 Kernel panic - not syncing: Attempted to kill init! But I can boot up from its

I really wants to know. When I start "xm create fc3 -c" but always maintenance mode. Is someone kind enough to point whats wrong with me? Configfiles are like this. kernel ="/boot/vmlinuz-2.6.11-1.1177_FC4xenU" memory =128 name = "fc3" nics = 1 disk = [''file:/root/fedora.img,hda2,w''] ip="210.166.211.245"

I have a CentOS 5 machine in which I'm trying to remove lvm. I dd'ed the file system to another partition, then dd'ed it back overwriting the lvm partition. I then modified menu.lst and fstab and replaced the paths to point to the correct device. When the system boots it's still looking for lvm. I can restore the system back to where it was with lvm, but I'm not sure what

I posted this to the Fedora-test list but I''ll try here. If I need to ditch fedora rpms and move to building directly from src before posting here, please let me know and I''ll do so (apologies in advance if this is the case). I have the following Fedora RPMS installed: kernel-xen0-2.6.10-1.1155_FC4 kernel-xenU-2.6.10-1.1155_FC4 xen-2-20050222 I can

Dear All Problem with ext3 fs on 3ware 9500S controller: Dec 7 05:59:50 stams kernel: EXT3-fs error (device sda1): ext3_add_entry: bad entry in directory #145998372: rec_len is smaller than minim al - offset=0, inode=0, rec_len=0, name_len=0 Dec 7 05:59:50 stams kernel: Aborting journal on device sda1. Dec 7 05:59:50 stams kernel: ext3_abort called. Dec 7 05:59:50 stams kernel: EXT3-fs

Hello, I just upgraded from Xen-3.3.1 to Xen-4.0.0. System is Gentoo, Hardware is DualCore AMD Athlon, 8GB RAM. The kernel was upgraded from OpenSUSE 2.6.27.29-0.1.1 to Gentoo-2.6.32-xen- r1. The first boot failed with an OOM error during kernel/initrd load, so I adjusted the dom0_mem option and had to increase it''s avalue from 256M to at least 400M until the dom0 could boot. At all