Bug 129436

Summary:	xen domU kernel does not contain device-mapper driver
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Stephan Böni <sb>
Component:	Xen	Assignee:	Kurt Garloff <garloff>
Status:	VERIFIED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P4 - Low
Version:	Final
Target Milestone:	---
Hardware:	x86-64
OS:	SuSE Linux 10.0
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Stephan Böni 2005-10-19 16:55:37 UTC

Trying to access a LVM gives the following error:

# vgdisplay
  --- Volume group ---
  VG Name               xenvg
  System ID
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  47
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                45
  /proc/misc: No entry for device-mapper found
  Is device-mapper driver missing from kernel?
  Failure to communicate with kernel device-mapper driver.
  Open LV               0
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               299.97 GB
  PE Size               32.00 MB
  Total PE              9599
  Alloc PE / Size       8928 / 279.00 GB
  Free  PE / Size       671 / 20.97 GB
  VG UUID               S3ER0v-xNyR-oTdc-xKkn-pZed-l6uT-Eyg8Il

Please add the device-mapper driver to the domU kernel. Thanks.

Comment 1 Kurt Garloff 2005-11-14 22:12:38 UTC

I'm confused: SUSE only has one kernel, both for dom0 and domU. And it does
contain the device-mapper kernel modules. Did you maybe fail to put the
dm module into the domU filesystem or its initrd? Or just fail to load it?
How did you build the root FS for domU anyway?

Comment 2 Stephan Böni 2005-11-28 09:54:39 UTC

The root filesystem for domU is a primary partion with reiserfs. I've filled it up with 'yast dirinstall'.

Comment 3 Kurt Garloff 2005-12-20 20:43:34 UTC

Sorry, but the kernel module for device-mapper does exist, can be loaded and
works.
If mkinitrd can determine that dm-mod is needed, it will be added to the
initrd and loaded on boot. Otherwise, you may add it to MODULES_LOADED_ON_BOOT in /etc/sysconfig/kernel.

This should fix it for you.

Comment 4 Lynn Bendixsen 2006-01-23 17:51:18 UTC

Fixed in latest release of SL10.1 and SLES 10.