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

Re: [Xen-users] HVM domU on storage driver domain

  • To: xen-users@xxxxxxxxxxxxx
  • From: Kuba <kuba.0000@xxxxx>
  • Date: Tue, 17 Jan 2017 12:57:30 +0100
  • Delivery-date: Tue, 17 Jan 2017 11:58:46 +0000
  • List-id: Xen user discussion <xen-users.lists.xen.org>

W dniu 2017-01-16 o 17:06, G.R. pisze:
Hi all,
I'm trying out the storage driver domain feature


A while ago, with a great deal of help from Roger Pau Monné, I managed to use FreeBSD domU as storage driver domain to provide storage for other domUs.

The main difference is that it didn't require any network-based protocol (iSCSI etc.) between the domains.

Typically your domU's frontend driver is connected to a block device inside dom0 via dom0's backend driver. But Xen has the ability to connect your domU's frontend driver directly to the backend driver of another domU. In short, you can create a storage driver domain, create a block device inside it (e.g. a zvol) and than create another domU using this block device directly, just as if it was provided by dom0.

Here you can find the steps that should get you started. It was a while ago and required to apply a patch to Xen; I don't know what's its status right now, but since FreeNAS is based on FreeBSD, it might be worth to take a look:


Some time later I managed to set up a "true" storage driver domain using PCI passthrough to assign SATA controller directly to the driver domain and used that domain to provide storage for Windows-based guests. It worked flawlessly. I believe this idea might be interesting to you too.


Xen-users mailing list



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