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

Re: [Xen-users] domU as the backend for another domU on xen 3.2

To: deshantm@xxxxxxxxx
Subject: Re: [Xen-users] domU as the backend for another domU on xen 3.2
From: Pepe Barbe <elventear@xxxxxxxxx>
Date: Thu, 8 May 2008 14:21:30 -0500
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 08 May 2008 12:22:05 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer; bh=YIW50ppVfgeDpaJllplMgTIDb36R92AXynocEc5OEKs=; b=bAIuNI3GhAnhVSHTSkHrFTsTBZFBP3szh0qfJOwBRR22ghP0OEtReYLSHsbAt+6lJaDu2In6IlnI5Hvh/3O4BL+Wp2S3MeMiXoO93f/c/1LaF83BPxHpPk0iSx/7CQFRI4qeifgaFkEfVk8L/uCqdlCnB6JmrgRzYuOLwjlXV+Q=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer; b=niwy/bCDhTyPF8ws1tOjzogM0WgG5C2k3v9x35bzREMET793yZj59oxlbpdaOqxiZ1TVtfnwraih/s+HoAok7SfQm5f9tn2ouaffiaPk6hIBBExwrBEIDQJznKx/UTgyWN5M9aTM1yNHEOkgbB6t7coeKaJl3O7Z9C4Al+Bgivg=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1e16a9ed0805081100l65d5a0d0y89ff7fce5ddbe693@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <B9889E28-D3B0-41C2-84C1-EF7C7153E05E@xxxxxxxxx> <1e16a9ed0805081100l65d5a0d0y89ff7fce5ddbe693@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

On May 8, 2008, at 1:00 PM, Todd Deshane wrote:

I haven't been thru the thread in detail, but the part about having different bridges for different vifs can be handled in the domU configuration file.
For example

vif=['bridge=otherbridge']

Is that the information you are looking for or is it a deeper design question?

I found a solution that somewhat satisfies me, I have to write the scripts know.

If the config line says vif=['bridge=otherbridge,backend=domain'], then I can query XenStore and find out where does the vif that has been added to domain be bridged. I think this will allow a little bit more flexibility than the script that is the email that I had referenced previously.

Pepe

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