On Sun, May 23, 2010 at 10:22:47PM -0400, Ben C wrote:
> Ok, after several weeks of struggling with Xen 3.3.2 / NetBSD dom0 ..
> trying to run linux domu's paravirtualized .. I finally got CentOS to
> install using the images available on the FTP.
>
> Unfortunately.. after installation, I can't seem to get it to boot.
>
> after running xm -c create Ben1CentOSpv I get:
>
> ...[snipped]
> Loading sd_mod.ko module
> Loading libata.ko module
> Loading ata_piix.ko module
> Loading dm-mem-cache.ko module
> Loading dm-mod.ko module
> device-mapper: uevent: version 1.0.3
> device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised:
> dm-devel@xxxxxxxxxx
> Loading dm-log.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
> Waiting for driver initialization.
> Scanning and configuring dmraid supported devices
> 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!
>
> -------
>
> I don't know what's going wrong here. I FINALLY just got them
> installing after what seems an eternity. Now this! arg.. I have a
> feeling this is something simple, though.
>
You're missing root= parameter for the Linux kernel.
CentOS initrd image requires that to mount the root.
> Here is my config:
>
>
> #-kernels from kernels-xen package
> # this is what i'm using to get the above error
> kernel = '/home/ben/kernels/centos/vmlinuz-2.6.18-164.15.1.el5xen';
> ramdisk = '/home/ben/kernels/centos/initrd-2.6.18-164.15.1.el5xen.img';
>
> #-generic kernel
> #kernel = '/home/ben/kernels/centos/vmlinuz-2.6.18-164.el5'
> #ramdisk = '/home/ben/kernels/centos/initrd-2.6.18-164.el5.img'
>
> #- installation kernels from ftp
> #kernel = '/home/ben/kernels/centosx/vmlinuz'
> #ramdisk = '/home/ben/kernels/centosx/initrd.img'
>
> name = "centospv"
> memory = "512"
> # I tried this and xvda1 ... no go either
> #root="/dev/xvda"
> disk = [ 'file:/home/ben/fileback/server1.img,xvda1,w', ]
> #vif = [ 'bridge=xenbr0', ]
> #vif = [ 'type=ioemu, bridge=bridge0, ip=PUB.LIC.IP.ADDR' ]
> vif = [ 'mac=aa:00:00:50:02:fa, bridge=bridge0' ]
> vcpus=1
> on_reboot = 'destroy'
> on_crash = 'destroy'
>
See, no root= parameter specified.
I'd recommend you to use "pygrub" to load the kernel/initrd/settings from the
guest,
instead of specifying kernel+initrd+root+extra in the cfgfile.
-- Pasi
> -------
>
> With the generic kernel, I get this error:
>
> Error: (2, 'Invalid kernel', 'xc_dom_parse_elf_kernel: ELF image has no
> shstrtab\n')
>
You're not using xen domU enables kernel here.
> Which amazes me because I see reference after reference that these
> generic kernels are now "xen ready". Maybe that's for newer versions of
> Xen? Regardless, I just need these suckers working! Any help would be
> appreciated.
>
RHEL5/CentOS5 use Linux 2.6.18 kernel, with "xenlinux" patches applied.
Newer upstream kernel.org Linux kernels after 2.6.24 do support Xen domU
out-of-the-box, but like you can see, CentOS5 still uses older kernel,
which requires special Xenlinux patches.
-- Pasi
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home