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

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


  • To: deshantm@xxxxxxxxx
  • 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
  • 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=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>


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


 


Rackspace

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