XCP storage driver domains

From Xen
Revision as of 12:17, 15 March 2013 by Dave.scott (talk | contribs) (Created page with "This page describes how to configure a storage driver domain on XCP 1.6. This is experimental software: please send feedback to xen-api@lists.xen.org. ==Create a suitable VM== …")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

This page describes how to configure a storage driver domain on XCP 1.6. This is experimental software: please send feedback to xen-api@lists.xen.org.

Create a suitable VM

Install a VM in the usual way. A storage driver domain can be PV or HVM. A storage driver domain must have:

  • the blkback kernel module
  • the XCP block udev scripts (available in RPM)
  • access to the storage medium (via the network or via a PCI passthrough device)

The blkback kernel module

Check you have the "xen-blkback" module (Linux) and "modprobe" it if its missing.

The XCP block udev scripts

These are needed to signal to the toolstack when a disk has been "attached".

PCI passthrough

Use "lspci" in dom0 to identify the storage controller you want to pass through. Take a note of the "BBBB:DD.F" identification string. Note that unless a multi-function device supports "Function Level Reset" on individual Functions you must pass all functions together as a group.

Use the "xe" CLI to associate this PCI device with your driver VM:

   xe vm-param-set uuid=<VM uuid> other-config:pci=0/BBBB:DD.F,1/BBBB:DD.F

If you shutdown and then restart the VM (not reboot), you should see the device appear in the driver VM with "lspci" while in dom0 the device should be associated with "pciback".

Install the storage control plane software

Add a VIF to the "internal management network"

Try the prototype file-backed "Storage Repository"

Create an SR via the driver domain