[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Patch for using drbd block devices and pygrub.


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Ben Timby <btimby@xxxxxxxxx>
  • Date: Wed, 25 Mar 2009 01:38:44 -0400
  • Delivery-date: Tue, 24 Mar 2009 22:39:09 -0700
  • 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=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

I ran into this problem when I installed CentOS using the HowTo:

http://wiki.centos.org/HowTos/Xen/InstallingCentOSDomU

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
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.