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-devel] Patch for using drbd block devices and pygrub.

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Patch for using drbd block devices and pygrub.
From: Ben Timby <btimby@xxxxxxxxx>
Date: Wed, 25 Mar 2009 01:38:44 -0400
Delivery-date: Tue, 24 Mar 2009 22:39:09 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=Mm/qCS4oS9vkMk6muoOVhuXWcHB5lqGPWX8lQXtgsS4=; b=VGgX1frmCtKV33p/2frUxuI+Lm9ImwmETll30knlnx+LWrj7HLKhj7VrbotTsdf+vX SaospIa70sbYAET4AdOpDPEO5chp6fn20m/drTV/PJyk/MEYCGooBDGiwbLreVs4dzoB 8wK+FNuS2WbD9MqHGYv+bPuU2uGF1Ziju2Pfc=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=gFYhN3zriORlpgkwSjwcghZgk8/FZBw8CQyZC/mYxkGxmC+GOf7ZhpTXoZ00waknpL JQD4YJrq+2NtMxOslqCRzMSLGh8TUm0+sSVe6ydHqQPloUWOhLBaQsHKwYYd2fd1E5CQ SWxMuciqPOlzPiVM88/u6GUg1abLztVLD5HaY=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I ran into this problem when I installed CentOS using the HowTo:


After installation, you are urged to use bootloader="/usr/bin/pygrub"

However, trying to start the domU results in the error "Error: Disk
isn't accessible". A google search turns up speculation that this is
somehow pygrub's fault, however, if one runs pygrub /dev/drbd0, it
works as expected.

The problem is in the xm utility, it attempts to resolve the disk name
(drbd0) into a device name (/dev/drbd0) by using the disk type (drbd).
However, it does not recognize the type drbd, so it fails to do so.
Attached is a patch that simply treats a drbd disk like phy and
returns "/dev/%s" % "drbd0".

I realize that a resource (drbd0) may actually use a different device
node that /dev/drbd0, however, resolving this would require parsing
the drbd.conf file and also using the current host name to locate the
correct "on" section. I figure this patch is good enough to work for
most folks.

Attachment: drbd_blkif.patch
Description: Text Data

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Patch for using drbd block devices and pygrub., Ben Timby <=