WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 1506] New: Support "bootloader" mode for "drbd:" devices

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1506] New: Support "bootloader" mode for "drbd:" devices
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Wed, 2 Sep 2009 08:54:10 -0700
Delivery-date: Wed, 02 Sep 2009 08:55:06 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1506

           Summary: Support "bootloader" mode for "drbd:" devices
           Product: Xen
           Version: 3.0.4
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Tools
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: michael.renner@xxxxxxxxx


Hi,

there's a bit of glue missing in xend to support the "bootloader" stanza in
Guests which use a "drbd:" device as their bootdevice.

This patch extends and supersedes Bug #1438.


To be able to use "bootloader" on drbd devices the following changes need to be
done:


*) Translation of devicename

_parse_uname which is used by blkdev_uname_to_file which is again used by
_configureBootloader in XendDomainInfo needs to be able to resolve drbd
resouces to the corresponding blockdevice to feed to the configured bootloader. 


*) Activation of drbd device

If the drbd device isn't in Primary mode when the bootloader tries to fetch the
kernel and initrd, the start of the DomU will fail. To prevent this the given
drbd device will be made Primary before the bootloader gets executed. 


The patches need some revising since I'm neither very fluent in Python nor
familiar with the error handling infrastructure in Xen.



A note on the naming of drbd resouces:

drbd uses mostly resource names in it's userland tools. Because of that drbd
VBDs, if configured with the "drbd:" type, should always use the drbd resource
name, as suggested by the drbd documentation at
http://www.drbd.org/users-guide-emb/s-xen-configure-domu.html . My patches
assume that the VBDs are named accordingly.


-- 
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

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