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

Re: [Xen-devel] Running netback/blkback in non-dom0 domains

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Running netback/blkback in non-dom0 domains
From: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Date: Fri, 18 Jul 2008 00:30:48 +0100
Cc: Anton Burtsev <aburtsev@xxxxxxxxxxxxx>
Delivery-date: Thu, 17 Jul 2008 16:31:12 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20080717220232.GE1918@xxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20080717220232.GE1918@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.9
On Thursday 17 July 2008, Anton Burtsev wrote:
> Hi,
>
> Is there a way to configure/hack Xen to run backend devices in
> a non-dom0 domain (in domU). Like, for example connect two domU
> domains with a block device.

Yes, I think this should Just Work with the right configuration parameters...

Set:
blkif = 'yes'
or
netif = 'yes'

As appropriate in your domain config file for the "backend" domU.  Then in the 
frontend domU's config file you can specify something like:

disks = [ 'phy:hda1,hda1,w,BACK' ]

substituting the domid of the backend domain for BACK (its name might work, 
possibly, I'm not sure).  Specifying file: or tap: disks in the backend domU 
to work in this way might be a bit of a fiddle (if it's possible) but phy: 
should work just fine.

or you can do:

vif 
= 
"type=TYPE,mac=MAC,bridge=BRIDGE,ip=IPADDR,script=SCRIPT,backend=DOM,vifname=NAME"

again, specifying the domid (or possibly the name) of the backend domain.

If you start the backend and then the frontend from these config files they 
should be able to connect do virtual device IO.

Cheers,
Mark


-- 
Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/)

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