community/xen without support for LVM

nicebloom · 2009-06-15 09:29:27

Hello Fellows,

Have tried XEN on Archlinux but run into troubles rigth after install.

Have set up my system with LVM for easy resizing and things like this, but when I try to boout my XEN-Kernel he drops me o a shell.

The Message is:

ALERT! /dev/sda2 does not exist. Droping to a shell!

I've tried to recompile the package with ABS but haven't get a working module for LVM (Module is dm_mod).
Anyone have solution for this?

...:::R3G4RD5:::...

nIcE

poopship21 · 2009-06-17 03:22:07

yeah i got something like that as well. installing the xen-3.4.0-1 package from community i was able to generate initcpio but got the following errors:

>>> Updating module dependencies. Please wait ...
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image "default"
==> Running command: /sbin/mkinitcpio -k 2.6.18.8-xen0 -c /etc/mkinitcpio.conf -g /boot/xen0.img
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [autodetect]
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [lvm2]
ERROR: module 'dm[-_]mod' not found
:: Parsing hook [filesystems]
:: Generating module dependencies
:: Generating image '/boot/xen0.img'...SUCCESS
==> SUCCESS
==> Building image "fallback"
==> Running command: /sbin/mkinitcpio -k 2.6.18.8-xen0 -c /etc/mkinitcpio.d/xen-fallback.conf -g /boot/xen0-fallback.img
:: Begin build
ERROR: module 'BusLogic' not found
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [ide]
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [usbinput]
:: Parsing hook [raid]
:: Parsing hook [filesystems]
:: Generating module dependencies
:: Generating image '/boot/xen0-fallback.img'...SUCCESS
==> SUCCESS
==> Building image "default"
==> Running command: /sbin/mkinitcpio -k 2.6.18.8-xenU -c /etc/mkinitcpio.conf -g /boot/xenU.img
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [autodetect]
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [lvm2]
ERROR: module 'dm[-_]mod' not found
:: Parsing hook [filesystems]
:: Generating module dependencies
:: Generating image '/boot/xenU.img'...SUCCESS
==> SUCCESS
==> Building image "fallback"
==> Running command: /sbin/mkinitcpio -k 2.6.18.8-xenU -c /etc/mkinitcpio.d/xen-fallback.conf -g /boot/xenU-fallback.img
:: Begin build
ERROR: module 'BusLogic' not found
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [ide]
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [usbinput]
:: Parsing hook [raid]
:: Parsing hook [filesystems]
:: Generating module dependencies
:: Generating image '/boot/xenU-fallback.img'...SUCCESS
==> SUCCESS

of course my root is on an lvm2 logical volume so im not going to even try to boot into this new kernel until that error goes away

i thought the whole point of "hooks" in mkinitcpio was to identify those modules...

nicebloom · 2009-06-17 12:11:44

Right the same as I have seen, when doing this.

The Archlinux Stock Kernel doesn't come with the modules or the abbility to use raid or lvm subsystem.:(
Haven't managed it yet to edit PKGBUILD to build the right kernel (with make menu to select the dm_mod).:/
If anyone has success with this please post your solution!:cool:

...:::R3G4RD5:::...

nIcE

fukawi2 · 2009-06-17 12:51:18

nicebloom wrote:

The Archlinux Stock Kernel doesn't come with the modules or the abbility to use raid or lvm subsystem.:(

Yes it does.

Try using the 'mdadm' hook in /etc/mkinitcpio.conf then rerun mkinitcpio

nicebloom · 2009-06-17 14:33:57

fukawi2 wrote:

nicebloom wrote:
The Archlinux Stock Kernel doesn't come with the modules or the abbility to use raid or lvm subsystem.:(
Yes it does.
Try using the 'mdadm' hook in /etc/mkinitcpio.conf then rerun mkinitcpio

But mdadm is not dm_mod, or?
and the mdadm hook isnt the lvm2 hook, or?

And if i want tu use LVM my mkinitcpio.conf looks like this:

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES="piix ide_disk reiserfs"
MODULES="scsi_mod ahci"

# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish.  This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
BINARIES=""

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway.  This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
#    FILES="/etc/modprobe.conf"
FILES=""

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
#    This setup specifies all modules in the MODULES setting above.
#    No raid, lvm2, or encrypted root is needed.
#    HOOKS="base"
#
#    This setup will autodetect all modules for your system and should
#    work as a sane default
#    HOOKS="base udev autodetect pata scsi sata filesystems"
#
#    This is identical to the above, except the old ide subsystem is
#    used for IDE devices instead of the new pata subsystem.
#    HOOKS="base udev autodetect ide scsi sata filesystems"
#
#    This setup will generate a 'full' image which supports most systems.
#    No autodetection is done.
#    HOOKS="base udev pata scsi sata usb filesystems"
#
#    This setup assembles an pata raid array with an encrypted root FS.
#    Note: See 'mkinitcpio -H raid' for more information on raid devices.
#    HOOKS="base udev pata raid encrypt filesystems"
#
#    This setup loads an lvm2 volume group on a usb device.
#    HOOKS="base udev usb lvm2 filesystems"
HOOKS="base udev autodetect pata scsi sata usb fw net usbinput keymap lvm2 filesystems"

...:::R3G4RD5:::...

nIcE

Last edited by nicebloom (2009-06-17 14:36:42)

poopship21 · 2009-06-17 17:23:38

the lvm2 hook is sufficient to build the initcpio from an arch kernel because it adds the dm_mod module (necessary for lvm). you can extract the kernel .img (not as root) and take a look inside to confirm this. the problem we were running into with lvm during mkinitcpio on the xen dom0 kernel is that the kernel which comes with this package does not include dm_mod (therefore the lvm2 hook in mkinitcpio.conf fails). i believe it would be sufficient to copy this module into the xen kernel archive but i havent tried. also does anyone know what BusLogic (see mkinitcpio output above) is and what module it corresponds to?

fukawi2 · 2009-06-17 22:28:43

nicebloom wrote:

fukawi2 wrote:
nicebloom wrote:
The Archlinux Stock Kernel doesn't come with the modules or the abbility to use raid or lvm subsystem.:(
Yes it does.
Try using the 'mdadm' hook in /etc/mkinitcpio.conf then rerun mkinitcpio
But mdadm is not dm_mod, or?
and the mdadm hook isnt the lvm2 hook, or?

Apologies, late night posting ftl. I was just looking at the RAID part of your query. mdadm is for Software RAID. You are right that 'lvm2' is for LVM.

nicebloom · 2009-06-18 08:39:35

poopship21 wrote:

I believe it would be sufficient to copy this module into the xen kernel archive but i havent tried.

This isn't as easy as you say. Because the module must fit into your kernel, so it must compiled against it. So copying wouldn't do the trick.
Your kernel must first support this module to load and you need the right module for your kernel.

You must recompile the Archlinux Stock Xen kernel to approach this.:|
But haven't get it working yet...

...:::R3G4RD5:::...

nIcE

WaxyMouthfeel · 2009-07-09 14:02:38

I noticed from the config file that the Xen kernel doesn't need the LVM2 module as its built into the kernel. On the other hand, it's missing XFS support completely, which is why it wouldn't work for me. I used the config file that comes with the binary package, and grabbed the source from http://xenbits.xen.org/linux-2.6.18-xen.hg and I just got it to boot properly.

Arch Linux

#1 2009-06-15 09:29:27

community/xen without support for LVM

#2 2009-06-17 03:22:07

Re: community/xen without support for LVM

#3 2009-06-17 12:11:44

Re: community/xen without support for LVM

#4 2009-06-17 12:51:18

Re: community/xen without support for LVM

#5 2009-06-17 14:33:57

Re: community/xen without support for LVM

#6 2009-06-17 17:23:38

Re: community/xen without support for LVM

#7 2009-06-17 22:28:43

Re: community/xen without support for LVM

#8 2009-06-18 08:39:35

Re: community/xen without support for LVM

#9 2009-07-09 14:02:38

Re: community/xen without support for LVM

Board footer