[Xen-bugs] [Bug 1438] New: Cannot use pygrub with drbd blcok device as xvda.

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1438

           Summary: Cannot use pygrub with drbd blcok device as xvda.
           Product: Xen
           Version: 3.0.4
          Platform: All
               URL: http://ben.timby.com/?p=80
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Tools
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: btimby@xxxxxxxxx


I ran into this problem when I installed CentOS into a Xen domU 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 than /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.


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs