mirror of
https://github.com/xen-project/xen.git
synced 2026-10-28 18:21:39 +01:00
Keir Fraser
e4e14402c1
To be able to use "bootloader" on drbd devices the following changes need to be made: *) 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 resources 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. 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. Signed-off-by: Michael Renner <michael.renner@geizhals.at>
The file test.py here is from the Zope project, and is Copyright (c) 2001, 2002 Zope Corporation and Contributors. This file is released under the Zope Public License, version 2.0, a copy of which is in the file ZPL-2.0.