This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] EVMS in dom-U

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] EVMS in dom-U
From: Jim Henderson <his_jimboness@xxxxxxxx>
Date: Thu, 01 Dec 2005 10:56:08 -0700
Delivery-date: Thu, 01 Dec 2005 17:56:11 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.2 (X11/20050418)

I am using XEN 2.0.7, kernel, EVMS 2.5.2.

I am trying to use EVMS in my domU but it is not detecting a "virtual"
disk.  I get the following error when issuing evms_activate -d debug:
Dec 01 17:20:34 samba _8_ LocalDskMgr: get_geometry: Error getting
geometry for disk sda: 38: Function not implemented.
So sda is "seen", but evms doesn't like it because-- it would appear--
it can't get the drive's geometry.

This is the domU configuration:
hostname = 'samba'
domainname = 'blah.com'
config_eth0 = 'dhcp'

# domU configuration
name = hostname + '.' + domainname
kernel = '/boot/kernel.xen-dom0'
ramdisk = '/boot/initrd'
memory = 128
cpu = -1

nics = 1
vif = [ 'mac=00:48:45:44:01:01, bridge=xen-br0' ]

disk = [ 'phy:loop0,hda,r', 'phy:sda4,sda,w' ]
root = '/dev/ram0 ro init=/linuxrc cdroot hostname=' + hostname + \
        ' domainname=' + domainname + ' config_eth0=' + config_eth0

Note that the sda device is what I'm unable to detect.  (Note that the
'hostname', 'domainname', 'config_eth0' root parameters are my own
customizations and unrelated to this discussion.)

I should note that:

1. I don't have these problems in domU when detecting an iSCSI volume in
EVMS; everything works perfectly under these conditions.

2. The O/S itself in dom-U has no problems; I can fdisk /dev/sda, make
partitions, make file systems, mount it, etc.  It's just EVMS that's
having trouble with the drive geometry.

3. In dom-0 I have no problems with EVMS; it detects sda4.  The problem
only occurs when I try EVMS within the dom-U.  I've tried exporting sda4
into the dom-U as sda1 (instead of sda) as well, with the same results.

So the question is: Is there something unique about xen disks in domU
that might cause EVMS to fail reading the disk geometry?  What else
might be the cause?

Thank you,

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>