Xen users - May 2008 - domU as the backend for another domU on xen 3.2

Hello everyone,

I am trying to setup a bridged connections between domUs using one of  
the domUs as a backend. For this purpose I followed this email, which  
was very illustrative:

http://lists.xensource.com/archives/html/xen-users/2005-07/msg00558.html

The previous solution works for me, but I would to do something more  
elegant. Specially being able to discern to which bridge a vif would  
like to connect. Anyone know of any solution or any way to make this  
work instead of putting all the vifs in a single bridge?

Thanks,
Pepe


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

Hi Pepe,

On Thu, May 8, 2008 at 12:30 PM, Pepe Barbe <elventear@gmail.com>
wrote:
> Hello everyone,
>
>  I am trying to setup a bridged connections between domUs using one of the
> domUs as a backend. For this purpose I followed this email, which was very
> illustrative:
>
>  http://lists.xensource.com/archives/html/xen-users/2005-07/msg00558.html
>
>  The previous solution works for me, but I would to do something more
> elegant. Specially being able to discern to which bridge a vif would like
to
> connect. Anyone know of any solution or any way to make this work instead
of
> putting all the vifs in a single bridge?
>
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?


Cheers,
Todd

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

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@lists.xensource.com
http://lists.xensource.com/xen-users

Hi Pepe,

On Thu, May 8, 2008, Pepe Barbe wrote:
>  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.
Could you post your refined scripts and setup to the list at some point?
I am sure that others could benefit from it.

Thanks,
Todd

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

On May 8, 2008, at 6:46 PM, Todd Deshane wrote:
> Could you post your refined scripts and setup to the list at some  
> point?
> I am sure that others could benefit from it.
I finally managed to make it work and the solution was simpler was  
trivial. I am using Ubuntu 8.04 and the domUs were created using xen- 
tools. The domUs were missing the udev scripts that automagically do  
this work for you. Installing xen-utils and all it''s dependencies  
solved the problem for me.

Pepe

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