Re: [MirageOS-devel] Xen VIF configuration for tap devices

[Masoud Koleini <masoud.koleini@xxxxxxxxxxxxxxxx>]

Solved.

Although Netif.connect accepts alphanumeric device ids in unix 
configuration, Xen version only accepts integer ids. Otherwise, it 
always assigns the first defined vif to the device. So, "tap1" has to be 
"1", and so on.
Thanks everyone.

On 30/10/14 13:42, Richard Mortier wrote:
> all;
>
> to take a slightly different tack on this -- is there anyone out there 
> successfully running mirage unikernels on xen that make use of >1 network 
> interface?  how did you configure this?
>
> haris-- what did you do for the mirage openflow paper?
>
> more generally-- is http://wiki.xenproject.org/wiki/Xen_Networking the 
> canonical location for info on how to configure and manage networking on xen 
> vms?
>
> and presumably all this results in entries in xenstore-- are 
> http://wiki.xen.org/wiki/XenStore and 
> http://wiki.xen.org/wiki/XenStore_Reference the canonical documentation for 
> xenstore and it's use by network devices?
>
> is there any documentation available on how to debug openvswitch networking on 
> xen via xenstore (or through some other means)?
>
> On 26 Oct 2014, at 20:06, Masoud Koleini <Masoud.Koleini@xxxxxxxxxxxxxxxx> 
> wrote:
>
> > I have defined 3 vifs with 3 different mac addresses for the 3 tap
> > devices that I am using, and switch shows the same mac address (mac
> > address of the first defined vif) assigned to both tap2 and tap3.
> >
> > Another issue that I faced is, although I can ping switch vm, nothing
> > appears on vifs and xenbr0 when switch starts a TCP connection to a
> > remote controller (using TCPV4 create_connection function). This
> > function works well for unix config.
> >
> > On 26/10/14 11:43, Anil Madhavapeddy wrote:
> > > On 25 Oct 2014, at 11:36, Masoud Koleini <masoud.koleini@xxxxxxxxxxxxxxxx> 
> > > wrote:
> > > > Hi all,
> > > >
> > > > I have a switch with three tap devices tap0 (for the controller connection), 
> > > > tap1, and tap 2 running on Xen.
> > > >
> > > > What would be the right VIF configuration for Xen?
> > > It would be pretty much the same configuration as your tap setup.  The Xen 
> > > networking model is to expose a VIF ('virtual interface') in the guest and 
> > > dom0.  Everything else from there is host setup and can be customised -- most 
> > > commonly by adding a bridge to the outside world and adding the VIFs from the 
> > > guests to that bridge so they can communication externally.
> > >
> > > The xl setup fragment looks like:
> > >
> > >      vif = [ 'bridge=xenbr0' ]
> > > or
> > >      vif = [ 'mac=c0:ff:ee:c0:ff:ee,bridge=br0' ]
> > >
> > > -anil
> > This message and any attachment are intended solely for the addressee and may 
> > contain confidential information. If you have received this message in error, 
> > please send it back to me, and immediately delete it.   Please do not use, copy 
> > or disclose the information contained in this message or in any attachment.  
> > Any views or opinions expressed by the author of this email do not necessarily 
> > reflect the views of the University of Nottingham.
> >
> > This message has been checked for viruses but the contents of an attachment
> > may still contain software viruses which could damage your computer system, you 
> > are advised to perform your own checks. Email communications with the 
> > University of Nottingham may be monitored as permitted by UK legislation.
> >
> >
> >
> >
> >
> > _______________________________________________
> > MirageOS-devel mailing list
> > MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
> > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
This message and any attachment are intended solely for the addressee and may 
contain confidential information. If you have received this message in error, 
please send it back to me, and immediately delete it.   Please do not use, copy 
or disclose the information contained in this message or in any attachment.  
Any views or opinions expressed by the author of this email do not necessarily 
reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system, you 
are advised to perform your own checks. Email communications with the 
University of Nottingham may be monitored as permitted by UK legislation.





_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel